12155 2017-10-02 21:48:45 +0000 Building MACHINE=<mach1> then building MACHINE=<mach2> w/ same tmp fails while doing -c populate_sdk_ext 2017-10-02 22:01:56 +0000 1 1 6 Yocto Project Subprojects eSDK eSDK 2.4 x86 Multiple RESOLVED DUPLICATE 12115 Undecided normal --- 1 brian.avery bluelightning francisco.j.pedraza.gonzalez --- --- No (bug/feature does not impact docs) oldest_to_newest 77283 0 brian.avery 2017-10-02 21:48:45 +0000 meta-yocto-bsp = "master:fcdfe09d9cc4e2977bd602dfd18f729cd9f6d73d" NOTE: Executing RunQueue Tasks ERROR: core-image-base-1.0-r0 do_populate_sdk_ext: The recipe core-image-base is trying to install files into a shared area when those files already exist. Those files and their manifest location are: <path>/build/tmp/deploy/sdk/poky-glibc-x86_64-core-image-base-core2-64-toolchain-ext-2.4.testdata.json (matched in manifest-qemux86-64-core-image-base.populate_sdk_ext) <path>/build/tmp/deploy/sdk/poky-glibc-x86_64-core-image-base-core2-64-toolchain-ext-2.4.sh (matched in manifest-qemux86-64-core-image-base.populate_sdk_ext) Please verify which recipe should provide the above files. The build has stopped, as continuing in this scenario WILL break things - if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would, however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error, however switching DISTRO_FEATURES on an existing build directory is not supported - you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_DUPWHITELIST may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above. ERROR: core-image-base-1.0-r0 do_populate_sdk_ext: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases. ERROR: core-image-base-1.0-r0 do_populate_sdk_ext: Function failed: sstate_task_postfunc ERROR: Logfile of failure stored in:<path>/build/tmp/work/genericx86_64-poky-linux/core-image-base/1.0-r0/temp/log.do_populate_sdk_ext.29915 ERROR: Task (/big/src/myBugs/poky/meta/recipes-core/images/core-image-base.bb:do_populate_sdk_ext) failed with exit code '1' NOTE: Tasks Summary: Attempted 4713 tasks of which 4711 didn't need to be rerun and 1 failed. Summary: 1 task failed: /big/src/myBugs/poky/meta/recipes-core/images/core-image-base.bb:do_populate_sdk_ext Summary: There were 3 ERROR messages shown, returning a non-zero exit code. To replicate: in local.conf add: MACHINE = "genericx86-64" # MACHINE = "qemux86-64" IMAGE_INSTALL_append=" wget bash coreutils procps packagegroup-core-full-cmdline " EXTRA_IMAGE_FEATURES_append = " ssh-server-openssh " IMAGE_ROOTFS_EXTRA_SPACE = "10242880" # sysd DISTRO_FEATURES_append = " systemd" VIRTUAL-RUNTIME_init_manager = "systemd" DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit" VIRTUAL-RUNTIME_initscripts = "systemd-compat-units" NOISO="1" NOHDD="1" IMAGE_FSTYPES="wic wic.vmdk" +++++ Then build $ bitbake core-image-base $ bitbake core-image-base -c populate_sdk_ext +++ Then change in local.conf to # MACHINE = "genericx86-64" MACHINE = "qemux86-64" ++++ Then Build $ bitbake core-image-base $ bitbake core-image-base -c populate_sdk_ext # and you will see a long error paragraph about how you should wipe out tmp. # it is likely that all you need to do is switch machines using an unmodified local.conf but I am not certain. 77284 1 bluelightning 2017-10-02 22:01:56 +0000 Right, I've seen this before. The file names are not unique, that's probably what we need to change. *** This bug has been marked as a duplicate of bug 12115 ***