Bug 8840 - Failure to build 32 bit eSDK on a 64 bit host
Summary: Failure to build 32 bit eSDK on a 64 bit host
Status: RESOLVED WONTFIX
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 2.1
Hardware: x86 Multiple
: Low enhancement
Target Milestone: Future
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
: 8929 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-12-18 19:19 UTC by Juro Bystricky
Modified: 2020-05-28 08:12 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Juro Bystricky 2015-12-18 19:19:12 UTC
When running

$ bitbake core-image-sato -c populate_sdk_ext

on a 64 bit host, with the SDKMACHINE="i686"

we get an error:

ERROR: The extensible SDK can currently only be built for the same architecture as the machine being built on - SDK_ARCH is set to i686 (likely via setting SDKMACHINE) which is different from the architecture of the build machine (x86_64). Unable to continue.
ERROR: Function failed: do_populate_sdk_ext
ERROR: Logfile of failure stored in: /data/swat/poky/build-mastersdk-exe/tmp/work/qemuppc-poky-linux/core-image-sato/1.0-r0/temp/log.do_populate_sdk_ext.20509
ERROR: Task 12 (/data/swat/poky/meta/recipes-sato/images/core-image-sato.bb, do_populate_sdk_ext) failed with exit code '1'

The point is, we get this error AFTER the core-image-sato was built, which can take a loooong time. Unless this is just a temporary limitation, this should be addressed, otherwise there will be some disgruntled users.
Comment 1 Randy Witt 2016-02-11 21:25:04 UTC
*** Bug 8929 has been marked as a duplicate of this bug. ***
Comment 2 Paul Eggleton 2018-04-18 15:06:00 UTC
The problem here is that we don't have a convenient mechanism for disabling individual tasks in a manner such that an error is shown if they are called (similar to SkipRecipe for entire recipes). However, Richard suggests a possible workaround in the form of deleting the do_populate_sdk_ext task in anonymous python and then re-creating it as a task with no dependencies that shows an appropriate error - in that case that task would be able to be scheduled early in the build.
Comment 3 Randy MacLeod 2020-05-28 08:12:37 UTC
Too many technical significant challenges involved.