From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] glibc: add version 2.24
Date: Fri, 5 Aug 2016 23:30:33 +0200 [thread overview]
Message-ID: <20160805233033.41c43841@free-electrons.com> (raw)
In-Reply-To: <20160805212501.GB3009@haswell>
Hello,
On Fri, 5 Aug 2016 14:25:01 -0700, Khem Raj wrote:
> Its just not kernel headers, infact its the kernel proper version as well
> which should be >= 3.2.0
Well, if your kernel headers are version X, surely you're running a
kernel >= X.
> you should also use --enable-kernel switch to detect the case where
> someone might be using older kernel with glibc 2.24 and running into
> issues at runtime.
As said above, we make the assumption that if kernel headers version X
were used, the user is running a kernel of version >= X.
> IMO BR should deprecate older versions more agressively, and keep them
> only on need basis. May be its against the objectives of the project
> but you will be spread thin supporting so many combinations and
> how to test them all.
We already deprecate older versions quite aggressively. We're currently
using glibc 2.23 (the latest until today), the latest uclibc-ng, the
latest musl. We haven't switched to gcc 5 as the default yet (we're on
gcc 4.9), but I'm planning on moving to gcc 5 as the default for the
next Buildroot release, i.e 2016.11.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-05 21:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 8:59 [Buildroot] [PATCH] glibc: add version 2.24 Vicente Olivert Riera
2016-08-05 14:33 ` Khem Raj
2016-08-05 16:54 ` Thomas Petazzoni
2016-08-08 8:46 ` Vicente Olivert Riera
2016-08-05 16:53 ` Thomas Petazzoni
2016-08-05 20:58 ` Khem Raj
2016-08-05 21:17 ` Thomas Petazzoni
2016-08-05 21:25 ` Khem Raj
2016-08-05 21:30 ` Thomas Petazzoni [this message]
2016-08-08 16:42 ` Yann E. MORIN
2016-08-09 8:49 ` Thomas Petazzoni
2016-08-09 19:33 ` Yann E. MORIN
2016-08-09 19:42 ` Khem Raj
2016-08-09 19:56 ` Yann E. MORIN
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=20160805233033.41c43841@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 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.