6856 2014-10-17 19:53:52 +0000 sanity.bbclass should check OLDEST_KERNEL 2015-02-17 15:05:44 +0000 1 1 7 Build System, Metadata & Runtime OE-Core configuration 1.7 All Multiple RESOLVED FIXED Medium minor 1.8 1 jch richard.purdie richard.purdie --- --- Yes (doc changes required) oldest_to_newest 46421 0 jch 2014-10-17 19:53:52 +0000 meta/conf/bitbake.conf defines OLDEST_KERNEL (currently 2.6.32), however running bitbake on a system with this kernel version will not generate an error until gcc-cross-initial-sdk do_install step. It would be much more user-friendly to check and fail in sanity.bb A pull request will be forthcoming. Thanks. Jeff 46422 1 jch 2014-10-17 20:14:59 +0000 I mean sanity.bbclass, not sanity.bb. I've fixed the description but am unable to edit my comment. 46537 2 richard.purdie 2014-10-23 14:45:33 +0000 There seems to be some confusion with this bug. OLDEST_KERNEL affects the oldest kernel either the target binaries or the SDK will run on. Neither should be affected by the kernel of the *build* system which is the kind of tests sanity.bbclass would perform. Could you describe the problem you're trying to solve in more detail please. 47369 3 richard.purdie 2014-12-04 16:01:09 +0000 No response to the question so assuming there was some confusion and the issue wasn't correctly described. If a better description is forthcoming, please reopen. 47372 4 jch 2014-12-04 16:27:21 +0000 The problem is that we can build a builtools tarball on a system with an older kernel, but are unable to use it on that system. There should at least be a warning from the build system that the generated SDK is not usable on the build system. The only indication is somewhat obscure message (FATAL: kernel too old) when you attempt to use the SDK. Additional there could be a check in the SDK installer that provides a more descriptive message. Thanks. Jeff 48882 5 richard.purdie 2015-02-17 15:05:44 +0000 http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=508509d150e375ed5701190ec4bb1259709b576c