Created
March 23, 2016 14:57
-
-
Save zskdan/8d8649763e2339eff2e5 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DEBUG: Executing python function sstate_task_prefunc | |
DEBUG: Python function sstate_task_prefunc finished | |
DEBUG: Executing python function do_populate_sysroot | |
DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common'] | |
DEBUG: Executing shell function sysroot_stage_all | |
0 blocks | |
0 blocks | |
0 blocks | |
DEBUG: Shell function sysroot_stage_all finished | |
DEBUG: Executing python function sysroot_strip | |
DEBUG: runstrip: 'arm-poky-linux-gnueabi-strip' --remove-section=.comment --remove-section=.note '/build/zakariae/wayland/agl/mybuild/hammerhead/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/dbus-cynara/1.8.18-r0/sysroot-destdir/usr/lib/dbus/dbus-daemon-launch-helper' | |
DEBUG: Python function sysroot_strip finished | |
DEBUG: Python function do_populate_sysroot finished | |
DEBUG: Executing python function do_qa_staging | |
NOTE: QA checking staging | |
DEBUG: Python function do_qa_staging finished | |
DEBUG: Executing python function sstate_task_postfunc | |
DEBUG: Staging files from /build/zakariae/wayland/agl/mybuild/hammerhead/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/dbus-cynara/1.8.18-r0/sysroot-destdir to /build/zakariae/wayland/agl/mybuild/hammerhead/tmp/sysroots/hammerhead | |
grep: /build/zakariae/wayland/agl/mybuild/hammerhead/tmp/sstate-control/manifest-hammerhead-pulseaudio.populate_sysroot: No such file or directory | |
ERROR: The recipe dbus-cynara is trying to install files into a shared area when those files already exist. Those files and their manifest location are: | |
/build/zakariae/wayland/agl/mybuild/hammerhead/tmp/sysroots/hammerhead/usr/lib/dbus/dbus-daemon-launch-helper | |
Matched in manifest-hammerhead-dbus.populate_sysroot | |
/build/zakariae/wayland/agl/mybuild/hammerhead/tmp/sysroots/hammerhead/lib/systemd/system/dbus.socket | |
Matched in manifest-hammerhead-dbus.populate_sysroot | |
/build/zakariae/wayland/agl/mybuild/hammerhead/tmp/sysroots/hammerhead/lib/systemd/system/dbus.service | |
Matched in manifest-hammerhead-dbus.populate_sysroot | |
/build/zakariae/wayland/agl/mybuild/hammerhead/tmp/sysroots/hammerhead/lib/systemd/system/multi-user.target.wants/dbus.service | |
Matched in manifest-hammerhead-dbus.populate_sysroot | |
/build/zakariae/wayland/agl/mybuild/hammerhead/tmp/sysroots/hammerhead/lib/systemd/system/dbus.target.wants/dbus.socket | |
Matched in manifest-hammerhead-dbus.populate_sysroot | |
/build/zakariae/wayland/agl/mybuild/hammerhead/tmp/sysroots/hammerhead/lib/systemd/system/sockets.target.wants/dbus.socket | |
Matched in manifest-hammerhead-dbus.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: 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. | |
DEBUG: Python function sstate_task_postfunc finished | |
ERROR: Function failed: sstate_task_postfunc |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment