Bug 8660

Summary: uninative.bbclass causes build to fail strangely when expected tarball is missing
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Paul Eggleton <bluelightning>
Component: devtools / tool chainAssignee: Paul Eggleton <bluelightning>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: meta.mr.watcher, meta.watcher, richard.purdie
Version: 2.0   
Target Milestone: 2.1   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
Log of preparing build system from ext SDK none

Description Paul Eggleton 2015-11-06 12:03:59 UTC
Created attachment 2841 [details]
Log of preparing build system from ext SDK

If you inherit uninative.bbclass, run a build and the expected tarball isn't available, the build fails in a rather odd way - see attached log. uninative is used within the extensible SDK and it kind of looks like the bitbake run might be failing without actually returning an exit code, because the install script seems to think it succeeded.

(Reproducer for this currently is to set SDKMACHINE to "i686" on a 64-bit build host, build the extensible SDK and then try to install it on a 32-bit machine - in this case uninative-tarball will have built an x86-64 tarball, but uninative.bbclass will be looking for an i686 one when preparing the build system and thus it will fail.)
Comment 1 Paul Eggleton 2015-11-06 12:12:53 UTC
FYI I've also filed bug 8661 for the (apparently unrelated) git errors at the top of the log.
Comment 2 Richard Purdie 2016-01-22 16:20:38 UTC
I believe my proposed uninative patch should improve the error handling for this.
Comment 3 Paul Eggleton 2016-03-04 02:36:20 UTC
This is now fixed in master.