All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Romain Naour <romain.naour@gmail.com>,
	Fabrice Fontaine <fontaine.fabrice@gmail.com>,
	"Yann E. MORIN" <yann.morin.1998@free.fr>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/zlib-ng: disable riscv with uclibc
Date: Sun, 24 Mar 2024 17:46:48 +0100	[thread overview]
Message-ID: <20240324174648.02bdf400@windsurf> (raw)
In-Reply-To: <7b0c2b66-38d2-4853-8438-2671006a91a1@mind.be>

On Sun, 24 Mar 2024 17:33:04 +0100
Arnout Vandecappelle <arnout@mind.be> wrote:

>   I believe we generally don't fix issues in packages if the issue is actually 
> in the libc itself. This does mean we will have build failures for older 
> prebuilt external toolchains, but those we should fix using the exclusions in 
> genrandconfig.
> 
>   I'm putting the other maintainers in Cc to check if they agree with my assessment.

I agree with your assessment. If Bootlin toolchains need to be rebuilt,
let me know, and I will be happy to rebuild them.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-03-24 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20 22:13 [Buildroot] [PATCH 1/1] package/zlib-ng: disable riscv with uclibc Fabrice Fontaine
2024-03-24 16:33 ` Arnout Vandecappelle via buildroot
2024-03-24 16:46   ` Thomas Petazzoni via buildroot [this message]
2024-03-25 21:11   ` Yann E. MORIN

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=20240324174648.02bdf400@windsurf \
    --to=buildroot@buildroot.org \
    --cc=arnout@mind.be \
    --cc=fontaine.fabrice@gmail.com \
    --cc=romain.naour@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.