[yocto] Kernel too old?

[Gary Thomas]

On 2016-11-16 13:08, Gary Thomas wrote:
> On 2016-11-16 12:55, Jussi Kukkonen wrote:
>> On 16 November 2016 at 13:29, Gary Thomas <gary at mlbassoc.com <mailto:gary at mlbassoc.com>> wrote:
>>
>>     I'm trying to run some user code on a [closed] box that it's
>>     difficult (maybe impossible) to update the kernel.  To date,
>>     I've been able to create my own user environment using Yocto
>>     and then just 'chroot XXX'.  That came to an end today with
>>     the latest (version 2.2) like this:
>>
>>       DiskStation> chroot /volume1/MY.test/
>>       FATAL: kernel too old
>>       DiskStation> cat /proc/version
>>       Linux version 2.6.32.12 (root at build5) (gcc version 4.3.2 (GCC) ) #3202 SMP Fri Mar 1 01:04:06 CST 2013
>>
>>     Where '/volume1/MY.test' is my Yocto-built root file system.
>>
>>     Is there any way around this if I can't update the running kernel?
>>
>>
>> Modern glibc needs linux 3.2, see http://repo.or.cz/glibc.git/commit/5b4ecd3f95695ef593e4474b4ab5a117291ba5fc
>> (apparently on x86* you could still get away with setting OLDEST_KERNEL to 2.6.32).
>
> Given that my code was running fine as recently as mid-summer with
> a version of glibc that was called 2.24-r0, do you think I can get
> away with this?  Can I just set that variable in local.conf?
>
> (I know it's only speculation...)
>
> Thanks
>

Sadly, I tried this, overriding this value in the glibc recipe
... same results :-(

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------