From: Richard Purdie <rpurdie@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: yocto@yoctoproject.org
Subject: Re: [PULL] devel/toolchain Recipes upgrades
Date: Wed, 10 Nov 2010 07:31:58 +0800 [thread overview]
Message-ID: <1289345518.1272.55.camel@rex> (raw)
In-Reply-To: <4CD9663A.50200@windriver.com>
On Tue, 2010-11-09 at 09:18 -0600, Mark Hatle wrote:
> On 11/9/10 12:12 AM, Bruce Ashfield wrote:
> > On 10-11-08 7:41 PM, Kamble, Nitin A wrote:
> >> From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com]
> >>
> >> Out of curiosity. What's the logic/requirement behind this
> >> change ? Since we don't have a 'supported' 2.6.36 kernel, using
> >> these would be a mismatch with what is actually booting on
> >> the targets.
> >>
> >> There's probably something I just don't understand here, so
> >> apologies in advance for the (potentially) dumb question.
> >>
> >> AFAIU the linux-libc-headers are independent from the running kernel. These are headers for libc.
> >
> > But they aren't. The libc headers should be coupled to the
> > kernel version. New ABIs are established and glibc can detect
> > and deal with this, but you should never have a newer set of
> > headers than the running kernel.
> >
> > To say the least, I'd like more explanation of this change.
>
> I agree with Bruce here. If anything the linux-libc-headers should be the same
> or OLDER then the running kernel for this exact reason. It's quite dangerous
> for newer kernel headers, as they may trigger behavioral differences within the
> glibc configuration.
When you compile [e]glibc you specify the oldest kernel you wish to
support. As far as I know it is safe to use a recent set of kernel
headers to build [e]glibc and then use older kernels with it. I have
never seems a problem caused directly by kernel versions unless it was
related to ABI changes or massive kernel version differences (2.4
kernels on a 2.6 optimised glibc, compiled with 2.6 as the oldest kernel
it would support).
I'm therefore ok in general with keeping linux-libc-headers tracking the
most recent kernels and letting the toolchain optionally support
features from the most recent kernel.
If I'm missing something or anyone has experience of this causing
problems I'd be interested to learn about it though.
Cheers,
Richard
next prev parent reply other threads:[~2010-11-10 0:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 20:32 [PULL] devel/toolchain Recipes upgrades Kamble, Nitin A
2010-11-08 20:39 ` Bruce Ashfield
2010-11-09 0:41 ` Kamble, Nitin A
2010-11-09 6:12 ` Bruce Ashfield
2010-11-09 15:18 ` Mark Hatle
2010-11-09 23:31 ` Richard Purdie [this message]
2010-11-10 1:14 ` Bruce Ashfield
2010-11-15 18:17 ` Kamble, Nitin A
2010-11-09 0:06 ` Saul Wold
2010-11-09 1:01 ` Kamble, Nitin A
2010-11-12 17:05 ` Kamble, Nitin A
2010-11-14 19:03 ` Kamble, Nitin A
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=1289345518.1272.55.camel@rex \
--to=rpurdie@linux.intel.com \
--cc=mark.hatle@windriver.com \
--cc=yocto@yoctoproject.org \
/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.