public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] sbuild-chroot: Drop no longer needed and now broken riscv64 special case
Date: Wed, 12 Mar 2025 16:09:56 +0300	[thread overview]
Message-ID: <a4846998ce68611c107bcf6f9da0678fb1b30211.camel@ilbers.de> (raw)
In-Reply-To: <e0283029-6862-4282-a235-0dab237a143e@siemens.com>

On Mon, 2025-02-24 at 22:02 +0100, '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"
> -- 
> 2.43.0
> 

Applied to next, thanks.

-- 
Best regards,
Uladzimir.

-- 
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/a4846998ce68611c107bcf6f9da0678fb1b30211.camel%40ilbers.de.

      parent reply	other threads:[~2025-03-12 13:10 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
2025-03-12 13:09 ` Uladzimir Bely [this message]

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=a4846998ce68611c107bcf6f9da0678fb1b30211.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=isar-users@googlegroups.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