From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] glibc: add version 2.24
Date: Tue, 9 Aug 2016 10:49:51 +0200 [thread overview]
Message-ID: <20160809104951.1ad736d4@free-electrons.com> (raw)
In-Reply-To: <20160808164209.GA5876@free.fr>
Hello,
On Mon, 8 Aug 2016 18:42:09 +0200, Yann E. MORIN wrote:
> > It is not written completely clearly: they first say that on
> > x86/x86-64, 2.6.32 is sufficient, but they conclude that 3.2 is the
> > minimum version on all architectures. It would be good to clarify this
> > aspect.
>
> What this means, at least what I understand it means, is that:
>
> - glibc 2.24 will not *run* on kernels more ancient than 3.2, except on
> x86/x86_64, when it will not run on kernels older than 2.6.32.
>
> This is a runtime dependency.
>
> - glibc needs kernel headers 3.2 (or later) for all architectures,
> even for x86/x86_64.
>
> This is a built-time dependency.
OK. From Buildroot's perspective, all what matters is the build-time
dependency. If the 3.2 kernel headers are needed to build glibc 2.24,
then glibc 2.24 should depend on headers >= 3.2.
> > 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.
>
> On all but x86_x86_64, yes.
I don't get this. From my point of view, the x86/x86_64 "exception" is
of no use to us: all we are interested in is the build-time dependency.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-09 8:49 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
2016-08-08 16:42 ` Yann E. MORIN
2016-08-09 8:49 ` Thomas Petazzoni [this message]
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=20160809104951.1ad736d4@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