[oe] [oe-commits] Roman I Khimov : (e) glibc-package: fix kernel version passed to qemu

[Roman I Khimov]

On Monday 18 May 2009 22:54:53 Phil Blundell wrote:
> On Mon, 2009-05-18 at 22:42 +0400, Roman I Khimov wrote:
> > Now, I think that this should be fixed on target level. OLDEST_KERNEL
> > should be something sane. Global 2.4.0 from bitbake.conf is good enough
> > for most targets, but if we know that none of ARM EABI works with kernel
> > versions prior to 2.6.14, we should set OLDEST_KERNEL to 2.6.14 for that
> > targets. Or higher, of course, if target needs/wants that. If that's OK
> > with all, I'm doing a patch.
>
> ...
>
> I think it would be better to leave the semantics of OLDEST_KERNEL alone
> and just teach qemu to use either the same __LINUX_KERNEL_VERSION as
> glibc's configure script has settled on, or (perhaps better) just the
> newest version that it supports for the given target.

Well, from my point of view, any static version is bad, because it's magic 
thrown in. When I've stumbled upon this, I've scratched my head a bit on why 
the hell is it 2.6.16, not 2.6.10, not 2.6.20, not anything else but 2.6.16. 
Sure enough, it's just something that worked some time ago for someone and was 
hardcoded then.

Then, I think that OLDEST_KERNEL should be something sane, since this is what 
we try to configure glibc with. It properly warns that there is something 
wrong on our side if we try to configure glibc for 2.4.0 kernel with ARM EABI 
target, so why not fix it? And then, if there are updates to glibc or anything 
else, it's target-specific and the target should adjust its OLDEST_KERNEL 
appropriately.

Of course, we can take version from __LINUX_KERNEL_VERSION, but that's more 
work and it doesn't fix misconfiguration we have when glibc has to decide that 
it knows better its minimal requirements for target.