From: Khem Raj <raj.khem@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] glibc: add version 2.24
Date: Fri, 5 Aug 2016 14:25:01 -0700 [thread overview]
Message-ID: <20160805212501.GB3009@haswell> (raw)
In-Reply-To: <20160805231747.768e6c08@free-electrons.com>
On 16-08-05 23:17:47, Thomas Petazzoni wrote:
> Hello,
>
> On Fri, 5 Aug 2016 13:58:12 -0700, Khem Raj wrote:
>
> > > Regardless of this detail, this means we will have to encode this
> > > dependency somehow. Indeed, we still have people using kernels older
> > > than 3.2 I believe on various platforms.
> >
> > thats right. perhaps --enable-kernel=3.2.0 conditional on version being
> > 2.24 in glibc mk file would put in a runtime check where apps would fail
> > to run on older kernels. If you want to detect it at build time then you
> > need to insert a mechanism to parse the kernel version of the build and
> > then compare that against kernel version used with --enable-kernel,
>
> I'm not really talking of build time detection, but rather referring to
> the fact that we have Config.in options in Buildroot that tell us the
> version of the kernel headers. So maybe glibc 2.24 should depend on
> kernel headers >= 3.2.0. For now, we'll keep glibc 2.23, but then some
> time later in the future, when 2.24 becomes the oldest supported glibc
> version, glibc as a whole will be usable only for >= 3.2.0. Hopefully
> by that time, all the people will have moved to newer kernels :)
Its just not kernel headers, infact its the kernel proper version as well
which should be >= 3.2.0
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.
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.
next prev parent reply other threads:[~2016-08-05 21:25 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 [this message]
2016-08-05 21:30 ` Thomas Petazzoni
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=20160805212501.GB3009@haswell \
--to=raj.khem@gmail.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