From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] glibc and --enable-kernel
Date: Tue, 02 Feb 2016 14:27:03 +0100 [thread overview]
Message-ID: <87egcv5jko.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <56AAA5BE.2050306@mind.be> (Arnout Vandecappelle's message of "Fri, 29 Jan 2016 00:35:26 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
>> The only reason that may encourage you to use
>> BR2_TOOLCHAIN_HEADERS_AT_LEAST instead of BR2_DEFAULT_KERNEL_HEADERS is
>> an upcoming patch from Yann E. Morin (already submitted but not merged
>> yet), which allows to tell Buildroot to use the kernel version
>> specified in the "Kernel" menu as the version for the kernel headers.
>> In this case, I believe BR2_DEFAULT_KERNEL_HEADERS will not be correct,
>> while BR2_TOOLCHAIN_HEADERS_AT_LEAST will be.
> A minor issue with _AT_LEAST, however, is that it will probably go through
> deprecation eventually. Right now we have "2.6" as the lowest _AT_LEAST - how
> will glibc deal with that? I can imagine at some point we'll deprecate 3,1, 3.2,
> and 3.3, so if you're using 3.3 headers the _AT_LEAST will become 3.0. Right
> now, we already have that for 2.6.3x, which will fall back to 2.6.0 (I guess -
> should be checked if glibc doesn't barf on 2.6 without .0).
If it does, then I suggest we filter out --enable-kernel for the oldest
variant, so we're back to how it works now as a lowest common denominator.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2016-02-02 13:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 4:21 [Buildroot] glibc and --enable-kernel Sam Bobroff
2016-01-27 8:21 ` Thomas Petazzoni
2016-01-28 2:55 ` Sam Bobroff
2016-01-28 8:36 ` Thomas Petazzoni
2016-01-28 23:35 ` Arnout Vandecappelle
2016-02-02 13:27 ` Peter Korsgaard [this message]
2016-02-02 16:56 ` Mike Frysinger
2016-02-04 4:10 ` Sam Bobroff
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=87egcv5jko.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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