Bug 11564

Summary: ERROR: binutils-crosssdk-i686-2.26-r0 do_populate_sysroot: Function failed: sstate_task_postfunc
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Juro Bystricky <juro.bystricky>
Component: coreAssignee: Ross Burton <ross.burton>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium+ CC: meta.mr.watcher, meta.watcher, richard.purdie
Version: 2.1.3   
Target Milestone: 2.1.3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
console output none

Description Juro Bystricky 2017-05-22 20:05:47 UTC
Created attachment 3774 [details]
console output

https://autobuilder.yoctoproject.org/main/builders/nightly-qa-extras/builds/1120/steps/BuildImages_3/logs/stdio


ERROR: binutils-crosssdk-i686-2.26-r0 do_populate_sysroot: The recipe binutils-crosssdk-i686 is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
   /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-qa-extras/build/build/tmp/sysroots/x86_64-linux/sysroot-providers/binutils-crosssdk-i686
 Matched in manifest-x86_64_i686_linux-binutils-crosssdk-i686.populate_sysroot
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: binutils-crosssdk-i686-2.26-r0 do_populate_sysroot: 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: binutils-crosssdk-i686-2.26-r0 do_populate_sysroot: Function failed: sstate_task_postfunc
ERROR: Logfile of failure stored in: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-qa-extras/build/build/tmp/work/i686-linux/binutils-crosssdk-i686/2.26-r0/temp/log.do_populate_sysroot.26668
NOTE: recipe binutils-crosssdk-i686-2.26-r0: task do_populate_sysroot: Failed
ERROR: Task 1008 (/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-qa-extras/build/meta/recipes-devtools/binutils/binutils-crosssdk_2.26.bb, do_populate_sysroot) failed with exit code '1'


Did not succeed when trying to reproduce the problem (clean build):

Build Configuration:
BB_VERSION        = "1.30.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "i586-poky-linux"
MACHINE           = "qemux86"
DISTRO            = "poky"
DISTRO_VERSION    = "2.1.2"
TUNE_FEATURES     = "m32 i586"
TARGET_FPU        = ""
meta              
meta-poky         
meta-yocto-bsp    = "krogoth:7b9e031355a993364a587b9ea878104827e3f799"
meta-mingw        = "krogoth:4fb621f4589f5357622b141ae28dc1018b91bc6e"

NOTE: Preparing RunQueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 2411 tasks of which 1930 didn't need to be rerun and all succeeded.