From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Switching from uClibc to glibc as the default in Buildroot?
Date: Wed, 19 Feb 2014 00:26:43 +0100 [thread overview]
Message-ID: <20140219002643.50795999@skate> (raw)
In-Reply-To: <20140218231759.GS184@brightrain.aerifal.cx>
Dear Rich Felker,
On Tue, 18 Feb 2014 18:17:59 -0500, Rich Felker wrote:
> As maintainer of musl libc (http://www.musl-libc.org), I'd like to
> suggest it as an alternative to switching to glibc. Obviously sticking
> with uClibc as the default would probably be the least invasive for
> your user base, but if that turns out not to be feasible, I think musl
> might be a better fit for most Buildroot users. Both musl's small size
> and strong robustness aims are attractive from an embedded
> perspective. We are about to make a 1.0 release and have active
> development plans following 1.0 as well.
>
> musl's arch coverage is still considerably less than uClibc's or
> glibc's, but the amount of work needed to add a port is also much
> lower (less than 20 small mandatory port-specific files aside from
> bits headers to match kernel/ABI-specific types) and we have an active
> development community willing to help getting additional ports
> integrated upstream. Right now we have i386, x86_64, arm(32),
> mips(32), microblaze, and powerpc(32); I expect to also merge the
> in-progress superh port before the next release.
Thanks a lot Rich for this proposal.
In fact, I am myself interested in musl: I have already added the
possibility of using external musl toolchains with Buildroot, and I
have started to work on integrating musl support in the internal
toolchain backend of Buildroot. So you can clearly expect musl to be
fully supported by Buildroot in the coming months.
Since we don't yet have this support in Buildroot, I believe it is too
early to consider making musl the default C library. But I definitely
want to see musl supported in Buildroot, in order to help make its
usage more widespread.
Do you intend to have support for non-MMU architectures in musl?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-18 23:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 22:14 [Buildroot] Switching from uClibc to glibc as the default in Buildroot? Thomas Petazzoni
[not found] ` <20140218231759.GS184@brightrain.aerifal.cx>
2014-02-18 23:26 ` Thomas Petazzoni [this message]
[not found] ` <20140219024634.GT184@brightrain.aerifal.cx>
2014-02-19 8:13 ` Thomas Petazzoni
[not found] ` <CAMKF1soCcLba_EacJLe7f9fM9=gFsTJYj0kaz6YzoXzEY1rx2A@mail.gmail.com>
2014-02-19 8:18 ` Thomas Petazzoni
2014-02-19 8:29 ` Peter Korsgaard
[not found] ` <fd7802bd-3f37-4d70-ad22-2e46fc452b4b@email.android.com>
[not found] ` <66DCE5C2-E7A6-4634-8C79-441DA9FC46FB@gmail.com>
2014-02-19 8:21 ` Thomas Petazzoni
2014-02-19 8:32 ` Peter Korsgaard
2014-02-19 13:21 ` Mike Zick
2014-03-07 8:07 ` Thomas De Schampheleire
2014-03-12 20:24 ` Bernhard Reutner-Fischer
2014-03-13 10:45 ` Vineet Gupta
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=20140219002643.50795999@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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