[yocto] [Yocto] [PULL] devel/toolchain Recipes upgrades

[Kamble, Nitin A]

-----Original Message-----
From: yocto-bounces at yoctoproject.org [mailto:yocto-bounces at yoctoproject.org] On Behalf Of Mark Hatle
Sent: Tuesday, November 09, 2010 7:18 AM
To: yocto at yoctoproject.org
Subject: Re: [yocto] [Yocto] [PULL] devel/toolchain Recipes upgrades

On 11/9/10 12:12 AM, Bruce Ashfield wrote:
> On 10-11-08 7:41 PM, Kamble, Nitin A wrote:
>> -----Original Message-----
>> From: Bruce Ashfield [mailto:bruce.ashfield at 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.

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.




Thanks Bruce & Mark for the responses. I think in the past we upgraded the 
linux-libc-headers while hoping the kernel will match it soon. But if we are going 
to stick to the current kernel for a while, then we can delay linux-libc-headers upgrade.

Also one way to handle this would be keep two versions of linux-libc-headers, one 
matching with kernel, and another with latest release. So whenever kernel is ready to 
be upgraded, linux-libc-headers would be ready.

Thanks & Regards,
Nitin