Bug 6856

Summary: sanity.bbclass should check OLDEST_KERNEL
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Jeffrey Honig <jch>
Component: configurationAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED FIXED QA Contact:
Severity: minor    
Priority: Medium CC: richard.purdie
Version: 1.7   
Target Milestone: 1.8   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)

Description Jeffrey Honig 2014-10-17 19:53:52 UTC 
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
Comment 1 Jeffrey Honig 2014-10-17 20:14:59 UTC 
I mean sanity.bbclass, not sanity.bb.  I've fixed the description but am unable to edit my comment.
Comment 2 Richard Purdie 2014-10-23 14:45:33 UTC 
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.
Comment 3 Richard Purdie 2014-12-04 16:01:09 UTC 
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.
Comment 4 Jeffrey Honig 2014-12-04 16:27:21 UTC 
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