On Friday 08 July 2011 11:12:12 Phil Blundell wrote: > 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.
OK, I had just assumed you would just get errors about missing syscalls, good to know that it would be more obvious than that. > 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. These sound like good ideas. I'll add them to my todo list to have a look at if nobody else gets there first. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
