oe-core b59eee7bebd413c7abe5626f69508e1fe47dd0ac means that building the eSDK requires uninative to be enabled. However, we only enable uninative for poky, and oe-core nodistro doesn't use it. As policy goes this is probably reasonable, but it breaks the autobuilder which expects to be able to build a eSDK for oe-core as well as poky. The least invasive option that I can see is to enable uninative in the nightly-oecore builds: INHERIT += "uninative" require conf/distro/include/yocto-uninative.inc
Oh, and remember to gate the addition on layer version, so old releases without uninative don't try to use it.
So I'm all for building the eSDK with this enabled (or we won't get a non-Poky test), however if we were to use this for the entire OE-Core build on the autobuilder that might not be the best thing. Before we start diverging in what we use to test OE-Core, we should explore whether people would be in favour of enabling uninative in OE-Core itself - I don't think anyone has asked the community yet. That would avoid any divergence *and* allow building the eSDK out of the box in OE-Core.
As being the SWAT this week, including the AB URL for this problem. https://autobuilder.yoctoproject.org/main/builders/nightly-oecore/builds/970/steps/BuildImages_1/logs/stdio And some log: NOTE: recipe core-image-minimal-1.0-r0: task do_populate_sdk_ext: Started ERROR: core-image-minimal-1.0-r0 do_populate_sdk_ext: The extensible SDK requires uninative to be enabled. Enabling this is straightforward - just add the following to your configuration: require meta/conf/distro/include/yocto-uninative.inc INHERIT += "uninative" ERROR: core-image-minimal-1.0-r0 do_populate_sdk_ext: Function failed: do_populate_sdk_ext ERROR: Logfile of failure stored in: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oecore/build/build/tmp-glibc/work/qemuarm-oe-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_populate_sdk_ext.27473 NOTE: recipe core-image-minimal-1.0-r0: task do_populate_sdk_ext: Failed ERROR: Task (/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oecore/build/meta/recipes-core/images/core-image-minimal.bb:do_populate_sdk_ext) failed with exit code '1' NOTE: Tasks Summary: Attempted 2220 tasks of which 2187 didn't need to be rerun and 1 failed. NOTE: The errors for this build are stored in /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oecore/build/build/tmp-glibc/log/error-report/error_report_20161112004859.txt You can send the errors to a reports server by running: send-error-report /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oecore/build/build/tmp-glibc/log/error-report/error_report_20161112004859.txt [-s server] NOTE: The contents of these logs will be posted in public if you use the above command with the default server. Please ensure you remove any identifying or proprietary information when prompted before sending. Summary: 1 task failed: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oecore/build/meta/recipes-core/images/core-image-minimal.bb:do_populate_sdk_ext Summary: There were 2 ERROR messages shown, returning a non-zero exit code. program finished with exit code 1 elapsedTime=249.946861
Observed again on Nov 23, 2016: Build worker for this Build: debian8.osl.yoctoproject.org Complete logs for all build steps: http://autobuilder.yoctoproject.org/main/builders/nightly-oecore/builds/979 Detailed log of last build step: http://autobuilder.yoctoproject.org/main/builders/nightly-oecore/builds/979/steps/BuildImages_1/logs/stdio
This is a duplicate of 10566. *** This bug has been marked as a duplicate of bug 10566 ***