Verified building for qemuppc but suspect it will fail for all archs. Changing the DEPLOY_DIR does NOT fail. To reproduce: $ bitbake core-image-sato-sdk (make sure you have INHERIT += "testimage" in conf) $ bitbake core-image-sato-sdk -c testimage (this should work) $ mv tmp/deploy/image/qemuppc/* /cow in local.conf set: DEPLOY_DIR_IMAGE="/cow" $ bitbake core-image-sato-sdk -c testimage (this should fail) and the failure should say something like: | NOTE: Output from runqemu: | runqemu - INFO - DEPLOY_DIR_IMAGE: /cow | runqemu - INFO - Assuming MACHINE = qemuppc | runqemu - INFO - Running MACHINE=qemuppc bitbake -e... | runqemu - ERROR - bitbake -e ERROR: Only one copy of bitbake should be run against a build directory | | runqemu - ERROR - Try 'runqemu help' on how to use it
Confirmed. Even with the fixes for 10211[1] and 10240[2] I can reproduce this issue. We'll need to figure out how this works with the current, shell based, runqemu (which also usually invokes bitbake -e to determine bitbake variables) and create an equivalent change for the Python3 based runqemu. 1. https://bugzilla.yoctoproject.org/show_bug.cgi?id=10211 2. https://bugzilla.yoctoproject.org/show_bug.cgi?id=10240
I've confirmed that this is a regression compared to the shell runqemu.
http://lists.openembedded.org/pipermail/openembedded-core/2016-September/126346.html
Fixed in OE-Core/Poky master