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.
*** Bug 8929 has been marked as a duplicate of this bug. ***
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.
Too many technical significant challenges involved.