Fixed
Created: Apr 10, 2017
Updated: Nov 16, 2017
Resolved Date: Nov 8, 2017
Found In Version: 9.0.0.5
Fix Version: 9.0.0.6
Severity: Critical
Applicable for: Wind River Linux 9
Component/s: BSP
When building a system with both BSPs, the following message appears:
ERROR: autoconf-archive-2016.09.16-r0 do_populate_lic: The recipe autoconf-archive is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
/git/lpd/CGP9-251/build/tmp/deploy/licenses/autoconf-archive/generic_GPLv2
Matched in b'manifest-intel_x86_64-autoconf-archive.populate_lic'
/git/lpd/CGP9-251/build/tmp/deploy/licenses/autoconf-archive/generic_GPLv3
Matched in b'manifest-intel_x86_64-autoconf-archive.populate_lic'
/git/lpd/CGP9-251/build/tmp/deploy/licenses/autoconf-archive/COPYING
Matched in b'manifest-intel_x86_64-autoconf-archive.populate_lic'
/git/lpd/CGP9-251/build/tmp/deploy/licenses/autoconf-archive/recipeinfo
Matched in b'manifest-intel_x86_64-autoconf-archive.populate_lic'
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.
configure system
$ MACHINE=intel-x86-64 bitbake autoconf-archive
$ MACHINE=qemux86-64 bitbake autoconf-archive
