From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Romain Naour <romain.naour@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [for-next] configs: select uclibc when needed
Date: Tue, 23 Aug 2022 22:01:53 +0200 [thread overview]
Message-ID: <20220823220153.3e5c1fb4@windsurf> (raw)
In-Reply-To: <2a8f7591-1ee7-f0e0-1fb6-43635272c258@gmail.com>
On Sun, 21 Aug 2022 23:56:19 +0200
Romain Naour <romain.naour@gmail.com> wrote:
> I'm agree on the principle to switch them to glibc but boards defconfig where
> only runtime tested with uclibc.
True, but I don't have much doubt that glibc will work fine if uclibc
was working fine. We're anyway already updating the versions of
gcc/binutils/uclibc for all defconfigs without necessarily checking
again on hardware.
> Also we may need to increase the file system
> image (BR2_TARGET_ROOTFS_EXT2_SIZE) when needed.That's why I choose to keep
> uclibc in this patch.
The size issue is not an issue: we will get a hard build failure if we
reach the maximum size, so it's easy to detect and fix.
So I think I would still prefer the defconfigs to not enforce a C
library, and use the default of Buildroot, which is now glibc.
Thanks!
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
next prev parent reply other threads:[~2022-08-23 20:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 15:31 [Buildroot] [for-next] package/gcc: bump to version 12.2.0 Romain Naour
2022-08-21 15:31 ` [Buildroot] [for-next] configs: select uclibc when needed Romain Naour
2022-08-21 21:03 ` Thomas Petazzoni via buildroot
2022-08-21 21:56 ` Romain Naour
2022-08-23 20:01 ` Thomas Petazzoni via buildroot [this message]
2022-08-23 20:18 ` [Buildroot] [for-next] package/gcc: bump to version 12.2.0 Thomas Petazzoni via buildroot
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=20220823220153.3e5c1fb4@windsurf \
--to=buildroot@buildroot.org \
--cc=romain.naour@gmail.com \
--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