From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] glibc: add 2.19 as a supported version
Date: Mon, 10 Feb 2014 21:29:59 +0100 [thread overview]
Message-ID: <52F936C7.4040300@mind.be> (raw)
In-Reply-To: <1392054226-20285-1-git-send-email-thomas.petazzoni@free-electrons.com>
On 02/10/14 18:43, Thomas Petazzoni wrote:
> glibc 2.19 has been released recently
> (https://sourceware.org/ml/libc-alpha/2014-02/msg00224.html). This
> commit allows to build a toolchain with this new version. In order to
> allow this, we add a version selection that did not exist for
> glibc. We default to 2.18, which was the only supported version until
> now, and add an option for 2.19.
How useful is it to offer a choice for the libc version?
For uClibc it makes a tiny bit of sense because you may have custom
patches or a custom config, which you don't want to port when going to a
new buildroot version. But I don't think that's a very good reason to
begin with.
For glibc, however, I really don't see a reason to keep multiple versions.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-02-10 20:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 17:43 [Buildroot] [PATCH] glibc: add 2.19 as a supported version Thomas Petazzoni
2014-02-10 20:29 ` Arnout Vandecappelle [this message]
2014-02-10 22:41 ` Thomas Petazzoni
2014-02-11 8:05 ` Arnout Vandecappelle
2014-02-11 8:19 ` Peter Korsgaard
2014-02-11 8:32 ` [Buildroot] Supporting multiple versions of toolchain components? Thomas Petazzoni
2014-02-11 17:16 ` Arnout Vandecappelle
2014-02-12 8:03 ` Thomas Petazzoni
2014-02-12 8:43 ` Peter Korsgaard
2014-02-12 17:37 ` Arnout Vandecappelle
2014-02-12 21:38 ` Thomas Petazzoni
2014-02-13 22:01 ` [Buildroot] [PATCH] glibc: add 2.19 as a supported version 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=52F936C7.4040300@mind.be \
--to=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.