I tested against pyro 2.3.1 (which is not an option here to choose from). Build Configuration: BB_VERSION = "1.34.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "arm-poky-linux-gnueabi" MACHINE = "multi-v7-ml" DISTRO = "poky" DISTRO_VERSION = "2.3.1" TUNE_FEATURES = "arm armv7a vfp neon" TARGET_FPU = "softfp" meta meta-poky meta-yocto-bsp = "heads/2017-08-21-pyro-2.3.1+:92a17c9074538a38d3d11c063be624f6c62a6352" meta-mainline multi-v7-ml = "heads/pyro-training-v4.9.x:69961a6b8ab4961b90e5aee51bb6b92b91c4062e" Initialising tasks: 100% |######################################################################################################################| Time: 0:00:16 Checking sstate mirror object availability: 100% |##############################################################################################| Time: 0:00:00 NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks WARNING: core-image-sato-sdk-1.0-r0 do_sdk_depends: Manifest /tmp/yocto-autobuilder/yocto-autobuilder/yocto-worker/res-custom-pyro-multi-v7-core-image-minimal-sato-sdk-ext/build/build/tmp/sstate-control/manifest-allarch-kernel-devsrc.populate_sysroot not found? WARNING: core-image-sato-sdk-1.0-r0 do_populate_sdk_ext: Manifest /tmp/yocto-autobuilder/yocto-autobuilder/yocto-worker/res-custom-pyro-multi-v7-core-image-minimal-sato-sdk-ext/build/build/tmp/sstate-control/manifest-allarch-kernel-devsrc.populate_sysroot not found? NOTE: Tasks Summary: Attempted 8211 tasks of which 8208 didn't need to be rerun and all succeeded. Now what's curious is that somehow allarch made it into SSTATE_ARCHS for kernel-devsrc, but there is no tmp/sstate-control/manifest-allarch-kernel-devsrc.populate_sysroot. bitbake -e kernel-devsrc | grep ^SSTATE_ARCHS= SSTATE_ARCHS=" x86_64 x86_64_x86_64_linux x86_64_arm x86_64_linux x86_64_multi_v7_ml allarch multi_v7_ml multi-v7-ml" A quick look at busybox shows, that it also has allarch in SSTATE_ARCHS, there is no manifest-allarch-busybox and it does not complain. bitbake -e busybox | grep ^SSTATE_ARCHS= SSTATE_ARCHS=" x86_64 x86_64_x86_64_linux x86_64_arm x86_64_linux x86_64_armv7a-neon allarch armv7a-neon multi-v7-ml" I am confused. How can I get rid of this warnings? my kernel recipe is here: https://github.com/RobertBerger/meta-mainline/tree/pyro-training-v4.9.x/multi-v7-ml/recipes-kernel/linux my poky is here: https://github.com/RobertBerger/poky/tree/2017-08-21-pyro-2.3.1+
with rocko: + build the extensible sdk: + bitbake core-image-sato-sdk -c populate_sdk_ext + press <ENTER> to go on NOTE: Started PRServer with DBfile: /tmp/yocto-autobuilder/yocto-autobuilder/yocto-worker/res-custom-rocko-multi-v7-core-image-minimal-sato-sdk-ext/build/build /cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 36277, PID: 10297 Loading cache: 100% |###########################################################################################################################| Time: 0:00:00 Loaded 1376 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.35.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "arm-poky-linux-gnueabi" MACHINE = "multi-v7-ml" DISTRO = "poky" DISTRO_VERSION = "2.4" TUNE_FEATURES = "arm armv7a vfp neon" TARGET_FPU = "softfp" meta meta-poky meta-yocto-bsp = "heads/2017-10-02-rocko-2.4-pre-release:e632745c4e7a39f5461a23a99e72036281c56917" meta-mainline multi-v7-ml = "heads/rocko-training-v4.9.x:4a60eac6a9b1586caeec812a801915c6b58314df" Initialising tasks: 100% |######################################################################################################################| Time: 0:00:13 Checking sstate mirror object availability: 100% |##############################################################################################| Time: 0:00:00 NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks WARNING: core-image-sato-sdk-1.0-r0 do_populate_sdk_ext: Manifest /tmp/yocto-autobuilder/yocto-autobuilder/yocto-worker/res-custom-rocko-multi-v7-core-image-minimal-sato-sdk-ext/build/build/tmp/sstate-control/manifest-allarch-kernel-devsrc.populate_sysroot not found?
Richard made some changes recently to do with manifest handling that he thinks may fix this - will test here.
We went through a phase of fixing these warnings and we no longer see them on the autobuilder which does test these kinds of builds.