From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Switching from uClibc to glibc as the default in Buildroot?
Date: Wed, 19 Feb 2014 09:29:16 +0100 [thread overview]
Message-ID: <8738jf33qb.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20140219091822.08d1a87e@skate> (Thomas Petazzoni's message of "Wed, 19 Feb 2014 09:18:22 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Dear Khem Raj,
> On Tue, 18 Feb 2014 16:23:11 -0800, Khem Raj wrote:
>> > To give you an idea, Buildroot currently has more than 50 patches on
>> > top of uClibc 0.9.33.2:
>> >
>> > http://git.buildroot.net/buildroot/tree/package/uclibc/0.9.33.2/
>>
>> Indeed, I see what you are saying here. In order to begin the process,
>> can you send a list of patches
>> that buildroot is carrying for inclusion into master.
> Peter will confirm, but I believe that *all* our patches are backports
> from the 0.9.33 branch at http://git.uclibc.org/uClibc/log/?h=0.9.33.
> So there is no special fix in Buildroot that isn't already in mainline
> uClibc.
That's the plan atleast. We normally don't carry any feature patches
(besides backports), but I would need to check to 100% sure.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-02-19 8:29 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
[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 [this message]
[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=8738jf33qb.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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