On Fri, 2011-07-08 at 11:03 +0100, Paul Eggleton wrote: > On Friday 08 July 2011 10:53:49 Phil Blundell wrote: > > They can always provide their own OLDEST_KERNEL setting, though. To > > some extent I think it's a bit academic what the default in oe-core is. > > Yes, but let's have a sensible default value, in particular that will allow > the majority not to experience subtle problems that they will have to spend > time tracking down. Many people coming to OE fresh will not know this setting > even exists - I only discovered it the other day by accident.
If OLDEST_KERNEL is set to a value that's too new then the failure you get is anything but subtle: glibc will just print "kernel too old" and exit. I guess we could enhance that message to refer directly to OLDEST_KERNEL to make it a bit more obvious what you need to do. Also, we could teach kernel.bbclass to issue a diagnostic if you try to build a kernel that's older than OLDEST_KERNEL. p. _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
