Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Christian Stewart <christian@aperture.us>,
	Buildroot List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] package/crun: allow building with uClibc
Date: Sat, 12 Aug 2023 00:26:34 +0200	[thread overview]
Message-ID: <20230812002634.45f2eff2@windsurf> (raw)
In-Reply-To: <de5cac45-aa70-b155-d7b6-f29006d4214b@mind.be>

On Fri, 11 Aug 2023 22:06:40 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:

>   I believe this is going to create problems again, because we have a few 
> toolchain configurations that are used in the autobuilders and that have really 
> old uClibc versions.
> 
>   As I said in a previous mail, we may want to drop these and move to bootlin 
> toolchains instead. But then, for some of them there is no bootlin toolchain 
> equivalent...
> 
>   Also, those autobuilder toolchains make sure we still have some testing of old 
> GCC versions, which we probably do want to keep.
> 
>   So, we should either:
> 
> - update all the autobuilder toolchains with newer uClibc;
> - switch those toolchains to bootlin toolchains;
> - switch those toolchains to internal toolchains;
> - add autobuilder exceptions;
> - add some Kconfig construct to identify fexecve availability.

The autobuilders are now doing fully random testing I believe, so they
are no longer testing some of those "special toolchains" we used to
have. They are either using well-known external toolchains, or building
internal toolchains.

In any case, I don't think we should worry too much about uClibc
features, and assume that people should have a recent uClibc, with the
uClibc configuration as it is in Buildroot.

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:[~2023-08-11 22:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-29 21:21 [Buildroot] [PATCH] package/crun: allow building with uClibc Thomas Petazzoni via buildroot
2023-07-31  2:44 ` Christian Stewart via buildroot
2023-08-06 14:28 ` Thomas Petazzoni via buildroot
2023-08-11 20:06 ` Arnout Vandecappelle via buildroot
2023-08-11 22:26   ` Thomas Petazzoni via buildroot [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=20230812002634.45f2eff2@windsurf \
    --to=buildroot@buildroot.org \
    --cc=arnout@mind.be \
    --cc=christian@aperture.us \
    --cc=thomas.petazzoni@bootlin.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