<p dir="ltr"></p>
<p dir="ltr">On Oct 13, 2016 5:23 AM, "Paul Eggleton" <<a href="mailto:paul.eggleton@linux.intel.com">paul.eggleton@linux.intel.com</a>> wrote:<br>
><br>
> On Thu, 13 Oct 2016 09:38:08 Paul Eggleton wrote:<br>
> > On Wed, 12 Oct 2016 15:26:15 Martin Jansa wrote:<br>
> > > is this separate variable working correctly?<br>
> > ><br>
> > > It was introduced in:<br>
> > > commit 522ba4c51fff53566678b2689d0d63c393e417b3<br>
> > > Author: Richard Purdie <<a href="mailto:richard.purdie@linuxfoundation.org">richard.purdie@linuxfoundation.org</a>><br>
> > > Date: Fri Sep 11 13:25:46 2015 +0100<br>
> > ><br>
> > > populate_sdk_base: Fix aarch64 OLDEST_KERNEL sdk issues<br>
> > ><br>
> > > aarch64 sets OLDEST_KERNEL to 3.14. This stops the aarch64 SDK<br>
> > ><br>
> > > installing on anything with an older kernel which is clearly incorrect.<br>
> > ><br>
> > > I attempted to extract the correct non-overridden version from the<br>
> > > data<br>
> > ><br>
> > > store but it proved problematic and I was running into data store issues.<br>
> > > Those are a separate problem but there isn't time to fix this right now.<br>
> > ><br>
> > > Instead just code the SDK kernel version separately to work around<br>
> > > this<br>
> > ><br>
> > > for now (and fix the autobuilder tests and SDK usage).<br>
> > ><br>
> > > But when I'm using:<br>
> > > OLDEST_KERNEL = "3.2" (default)<br>
> > > SDK_OLDEST_KERNEL = "2.6.32"<br>
> > > because we would like to use SDK on host with older kernel, then<br>
> > > SDK_OLDEST_KERNEL helped to bypass the uname check in environment-setup<br>
> > > script, but then gcc cannot be used, because it fails immediately with:<br>
> > ><br>
> > > FATAL: kernel too old<br>
> > ><br>
> > > So I'm not sure what this variable are trying to achieve, maybe<br>
> > > autobuilder<br>
> > > tests were only testing setup script and not the actual $CC?<br>
> > ><br>
> > > The other option is that it works only when sdk toolchain is built with<br>
> > > default OLDEST_KERNEL (which is lower than OLDEST_KERNEL_aarch64) and only<br>
> > > target bits use OLDEST_KERNEL_aarch64, but those aren't executed on host<br>
> > > using SDK.<br>
> ><br>
> > I'm not sure how this ever could have worked, since it doesn't enter into<br>
> > the nativesdk-glibc configuration. It seems to me that the glibc recipe<br>
> > needs to be using SDK_OLDEST_KERNEL in place of OLDEST_KERNEL for<br>
> > class-nativesdk.<br>
><br>
> Thinking about it - even if that were fixed, would setting it to 2.6.32<br>
> actually work on master? We are now using glibc 2.24 and that requires a<br>
> minimum kernel version of 3.2.0.</p>
<p dir="ltr">For x86/x86_64 2.6.32 would still work which is the most common arch for sdk host.<br>
><br>
> Cheers,<br>
> Paul<br>
><br>
> --<br>
><br>
> Paul Eggleton<br>
> Intel Open Source Technology Centre<br></p>