Bug 9339 - eSDK doesn't build correctly if environment variables are used
Summary: eSDK doesn't build correctly if environment variables are used
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 2.1
Hardware: x86 Multiple
: Medium normal
Target Milestone: 2.1
Assignee: Paul Eggleton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-03-24 13:23 UTC by Richard Purdie
Modified: 2016-04-01 01:14 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Purdie 2016-03-24 13:23:27 UTC
If I set:

MACHINE = "qemux86" in local.conf

but then run:

MACHINE=qemux86-64 bitbake core-image-sato -c populate_sdk_ext

I get an SDK which builds successfully but that has no matching sstate since the MACHINE definition on the SDK is incorrect.

At the very least we should detect this earlier, if not build the correct thing.