From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] glibc: bump default to version 2.22
Date: Fri, 19 Feb 2016 17:44:55 +0100 [thread overview]
Message-ID: <20160219174455.0ebf17b9@free-electrons.com> (raw)
In-Reply-To: <56C73852.8000400@zacarias.com.ar>
Hello,
On Fri, 19 Feb 2016 12:44:18 -0300, Gustavo Zacarias wrote:
> 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.
Agreed. If glibc no longer supports sparc < v9 and doesn't support SPE
FPUs, then it's an upstream issue, and we shouldn't keep old stuff
around because of this. People interested by those features should get
involve with upstream.
So: +1 to remove eglibc, and get rid of glibc 2.21, to keep only 2.22
and 2.23.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-19 16: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
2016-02-19 16:44 ` Thomas Petazzoni [this message]
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=20160219174455.0ebf17b9@free-electrons.com \
--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