a guest May 24th, 2017 100 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. DEBUG: Executing python function sstate_task_prefunc
  2. DEBUG: Python function sstate_task_prefunc finished
  3. DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']
  4. DEBUG: Executing shell function do_packagedata
  5. DEBUG: Shell function do_packagedata finished
  6. DEBUG: Executing python function sstate_task_postfunc
  7. DEBUG: Staging files from /media/tom/Backup/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/mesa-gl/2_11.1.1-r0/pkgdata to /media/tom/Backup/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am57xx-evm/pkgdata
  8. ERROR: The recipe mesa-gl is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
  9.    /media/tom/Backup/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am57xx-evm/pkgdata/runtime/libgbm
  10.  Matched in manifest-am57xx-evm-libgbm.packagedata
  11.  /media/tom/Backup/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am57xx-evm/pkgdata/runtime/libgbm-dev
  12.  Matched in manifest-am57xx-evm-libgbm.packagedata
  13. Please verify which recipe should provide the above files.
  14. 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.
  15. 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.
  16. DEBUG: Python function sstate_task_postfunc finished
  17. ERROR: Function failed: sstate_task_postfunc
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!