[PATCH] sbuild-chroot: Drop no longer needed and now broken riscv64 special case

13 views
Skip to first unread message

Jan Kiszka

unread,
Feb 24, 2025, 4:02:33 PM2/24/25
to isar-users
From: Jan Kiszka <jan.k...@siemens.com>

This was forgotten while cleaning up for trixie in 735dc16c1e. However,
it continued to work - until these days. Fix the riscv64 build by simply
dropping the obsolete package list.

Signed-off-by: Jan Kiszka <jan.k...@siemens.com>
---

Found via isar-cip-core where riscv64 is no longer allowed to break the
build.

meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb | 6 ------
1 file changed, 6 deletions(-)

diff --git a/meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb b/meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb
index 255d6937..3f0888d8 100644
--- a/meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb
+++ b/meta/recipes-devtools/sbuild-chroot/sbuild-chroot-host.bb
@@ -18,9 +18,3 @@ SBUILD_CHROOT_PREINSTALL ?= " \
crossbuild-essential-${DISTRO_ARCH} \
apt-utils \
"
-
-SBUILD_CHROOT_PREINSTALL:riscv64 ?= " \
- ${SBUILD_CHROOT_PREINSTALL_COMMON} \
- gcc-riscv64-linux-gnu \
- g++-riscv64-linux-gnu \
- dpkg-cross"
--
2.43.0

Jan Kiszka

unread,
Mar 10, 2025, 2:32:04 AM3/10/25
to isar-users
Can we please finally merge this fix? I'd like to avoid have to release
a downstream layer with an isar patch.

Jan

--
Siemens AG, Foundational Technologies
Linux Expert Center

MOESSBAUER, Felix

unread,
Mar 10, 2025, 4:35:19 AM3/10/25
to isar-...@googlegroups.com, Kiszka, Jan
If you want to release a downstream layer, you also need to consider
the "fix(rootfs): cleanup leftover 0000bootstrap.list" patch.
It would be good if that could get merged as well.

Currently ISAR is in a - let's say - not optimal state.

Felix

>
> Jan
>
> --
> Siemens AG, Foundational Technologies
> Linux Expert Center

--
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany

Uladzimir Bely

unread,
Mar 12, 2025, 9:10:03 AM3/12/25
to Jan Kiszka, isar-users
Applied to next, thanks.

--
Best regards,
Uladzimir.
Reply all
Reply to author
Forward
0 new messages