From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] glibc: bump default to version 2.22
Date: Fri, 19 Feb 2016 12:44:18 -0300 [thread overview]
Message-ID: <56C73852.8000400@zacarias.com.ar> (raw)
In-Reply-To: <87y4aghfxm.fsf@dell.be.48ers.dk>
On 19/02/16 12:34, Peter Korsgaard wrote:
>>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
>
> > Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
>
> Committed to next, thanks.
Hi.
Big general question for everyone, we now have 3 versions of glibc (not
counting eglibc).
The only reason for keeping 2.21 is sparc (< v9) support, which i think
doesn't make sense.
The case for eglibc is somewhat similar, it's support for SPE FPU (e500*).
Both are covered by uclibc so i think we could retire them.
Regards.
next prev parent reply other threads:[~2016-02-19 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 13:32 [Buildroot] [PATCH 1/2] glibc: add version 2.23 Gustavo Zacarias
2016-02-19 13:32 ` [Buildroot] [PATCH 2/2] glibc: bump default to version 2.22 Gustavo Zacarias
2016-02-19 15:34 ` Peter Korsgaard
2016-02-19 15:44 ` Gustavo Zacarias [this message]
2016-02-19 16:44 ` Thomas Petazzoni
2016-02-19 15:34 ` [Buildroot] [PATCH 1/2] glibc: add version 2.23 Peter Korsgaard
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=56C73852.8000400@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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