From: Peter Korsgaard <peter@korsgaard.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Buildroot List <buildroot@buildroot.org>,
Romain Naour <romain.naour@gmail.com>,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
Subject: Re: [Buildroot] [PATCH next] toolchain/toolchain-buildroot: default to glibc as the C library
Date: Tue, 16 Aug 2022 23:37:53 +0200 [thread overview]
Message-ID: <87bksjc1ji.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220816210334.GP2854108@scaer> (Yann E. MORIN's message of "Tue, 16 Aug 2022 23:03:34 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> Thomas, All,
> On 2022-08-15 22:29 +0200, Thomas Petazzoni via buildroot spake thusly:
>> This is perhaps the most controversial change for Buildroot that can
>> be written in a two-liner.
>>
>> Historically, we have used uClibc as our default C library, as
>> Buildroot was created initially as a test-bed for uClibc, and also
>> because uClibc made a lot of sense for embedded Linux systems, due to
>> its smaller size and fine-grained configurability.
>>
>> Since then, the landscape of embedded Linux systems has changed. Even
>> though Buildroot happily supports really low-end devices, the vast
>> majority of Buildroot users are quite certainly running the resulting
>> system on a reasonably powerful platform, with significant amount of
>> RAM and storage. In this context, the benefits of uClibc are no longer
>> that much relevant, and glibc causes less "troubles". Therefore, this
>> patch proposes to use glibc as our default C library when using the
>> internal toolchain backend instead of uClibc.
>>
>> Of course, we will keep the support for uClibc, which remains an
>> important C library choice, for space-constrained systems, or simply
>> for architectures that are not supported by glibc.
>>
>> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> Acked-by: Yann E. MORIN <yann.morin.1998@free.fr>
> Yes, I will be a bit sad that we demote uClibc-ng, but let's face it:
> the word moves on, let's move along.
Agreed.
Acked-by: Peter Korsgaard <peter@korsgaard.com>
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-08-16 21:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 20:29 [Buildroot] [PATCH next] toolchain/toolchain-buildroot: default to glibc as the C library Thomas Petazzoni via buildroot
2022-08-16 20:50 ` Arnout Vandecappelle
2022-08-16 21:03 ` Yann E. MORIN
2022-08-16 21:37 ` Peter Korsgaard [this message]
2022-08-17 19:35 ` Romain Naour
2022-08-18 20:15 ` Arnout Vandecappelle
2022-08-17 18:46 ` 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=87bksjc1ji.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=romain.naour@gmail.com \
--cc=thomas.de_schampheleire@nokia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox