There are two reasons for that:
1. In the README, GCC baseline is chosen to be 12.2, whereas Debian 11
uses GCC 10.2.1.
2. Xen requires mandatory some Z extensions, but GCC 10.2.1 does not
support Z extensions in -march, causing the compilation to fail.
Signed-off-by: Oleksii Kurochko <oleksii.kuroc...@gmail.com>
---
Changes in V8:
- Nothing changed except that now it has dependency from the
previous commit which adds information about GCC to README
and thereby clarify the commit message of the current commit.
---
Changes in V7:
- new patch
---
automation/gitlab-ci/build.yaml | 14 --------------
automation/scripts/containerize | 1 -
2 files changed, 15 deletions(-)
diff --git a/automation/gitlab-ci/build.yaml b/automation/gitlab-ci/build.yaml
index 6a2e491534..b952a59c06 100644
--- a/automation/gitlab-ci/build.yaml
+++ b/automation/gitlab-ci/build.yaml
@@ -723,20 +723,6 @@ debian-12-ppc64le-gcc:
HYPERVISOR_ONLY: y
# RISC-V 64 cross-build
-debian-11-riscv64-gcc:
- extends: .gcc-riscv64-cross-build
- variables:
- CONTAINER: debian:11-riscv64
- KBUILD_DEFCONFIG: tiny64_defconfig
- HYPERVISOR_ONLY: y
-
-debian-11-riscv64-gcc-debug:
- extends: .gcc-riscv64-cross-build-debug
- variables:
- CONTAINER: debian:11-riscv64
- KBUILD_DEFCONFIG: tiny64_defconfig
- HYPERVISOR_ONLY: y
-
debian-12-riscv64-gcc:
extends: .gcc-riscv64-cross-build
variables:
diff --git a/automation/scripts/containerize b/automation/scripts/containerize
index bc43136078..0953e0728c 100755
--- a/automation/scripts/containerize
+++ b/automation/scripts/containerize
@@ -31,7 +31,6 @@ case "_${CONTAINER}" in
_fedora) CONTAINER="${BASE}/fedora:41-x86_64";;
_bullseye-ppc64le) CONTAINER="${BASE}/debian:11-ppc64le" ;;
_bookworm-ppc64le) CONTAINER="${BASE}/debian:12-ppc64le" ;;
- _bullseye-riscv64) CONTAINER="${BASE}/debian:11-riscv64" ;;
_bookworm-riscv64) CONTAINER="${BASE}/debian:12-riscv64" ;;
_bookworm-x86_64-gcc-ibt) CONTAINER="${BASE}/debian:12-x86_64-gcc-ibt" ;;
_bookworm|_bookworm-x86_64|_) CONTAINER="${BASE}/debian:12-x86_64" ;;
--
2.48.1
