From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: Re: [PATCH] sbuild-chroot: Drop no longer needed and now broken riscv64 special case
Date: Mon, 10 Mar 2025 08:35:11 +0000 [thread overview]
Message-ID: <d56133dbf2c25adb8ae46a4f45bd79a13fa20468.camel@siemens.com> (raw)
In-Reply-To: <a7ad8d8d-3a02-46fc-a32c-7c183081493e@siemens.com>
On Mon, 2025-03-10 at 07:31 +0100, 'Jan Kiszka' via isar-users wrote:
> On 24.02.25 22:02, 'Jan Kiszka' via isar-users wrote:
> > From: Jan Kiszka <jan.kiszka@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.kiszka@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"
>
> Can we please finally merge this fix? I'd like to avoid have to
> release
> a downstream layer with an isar patch.
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
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/d56133dbf2c25adb8ae46a4f45bd79a13fa20468.camel%40siemens.com.
next prev parent reply other threads:[~2025-03-10 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 21:02 'Jan Kiszka' via isar-users
2025-03-10 6:31 ` 'Jan Kiszka' via isar-users
2025-03-10 8:35 ` 'MOESSBAUER, Felix' via isar-users [this message]
2025-03-12 13:09 ` Uladzimir Bely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d56133dbf2c25adb8ae46a4f45bd79a13fa20468.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox