From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Kamble, Nitin A" <nitin.a.kamble@intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: [PULL] devel/toolchain Recipes upgrades
Date: Tue, 09 Nov 2010 01:12:04 -0500 [thread overview]
Message-ID: <4CD8E634.1090403@windriver.com> (raw)
In-Reply-To: <8EA2C2C4116BF44AB370468FBF85A77701BCA3809D@orsmsx504.amr.corp.intel.com>
On 10-11-08 7:41 PM, Kamble, Nitin A wrote:
> -----Original Message-----
> 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.
>
> Cheers,
>
> Bruce
>
>
> Bruce,
> 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.
Bruce
>
> Thanks,
> Nitin
next prev parent reply other threads:[~2010-11-09 6:12 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 [this message]
2010-11-09 15:18 ` Mark Hatle
2010-11-09 23:31 ` Richard Purdie
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=4CD8E634.1090403@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=nitin.a.kamble@intel.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.