Re: [PATCH] Refuse to run bitbake on a kernel that is too old.

[Mark Hatle <mark.hatle@windriver.com>]

On 10/21/14, 6:03 PM, Enrico Scholz wrote:
> <jeffrey.honig-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org> writes:
>
>> Bitbake.conf now specifies OLDEST_KERNEL to insure that the SDK is
>> not run on a kernel that is not supported by a component of the SDK
>> (i.e. glibc).
>
> OLDEST_KERNEL is used in glibc recipe only; it would be much better
> to build SDK's glibc with an --enable-kernel matching the target
> distribution.  E.g. by setting a special 'OLDEST_KERNEL_nativesdk'
> variable.

glibc included with master has a minimum kernel version due to various ABIs that 
it uses.  My understanding is that the OLDEST_KERNEL does indeed match for the 
nativesdk.

>> +    # Check that our kernel will work for crosssdk
>
> This check should be made overridable for environments which do not
> build SDKs.

Using the buildtools-tarball will result in these issues.. (that is a lot more 
common, at least for us due to the wide variety of distributions that don't have 
minimum tool versions...)

>> +    if os.uname()[0] == "Linux" and LooseVersion(os.uname()[2]) < LooseVersion(d.getVar('OLDEST_KERNEL')):
>
> This check does not work when you build e.g. in an LXC container.  You
> could define something like
>
> | SDK_UNAME ??= "${@' '.join(os.uname())}"
>
> and do the checks on this.
>
>
> Enrico
>