diff options
| author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2018-11-20 14:05:08 +0000 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2018-11-21 11:54:48 +0000 |
| commit | 264f19f6862dbab5abf7ff27a79bd088ac44b6c4 (patch) | |
| tree | a583175792365034e2fbc950e9535d85927b8b6a /meta-poky/conf/layer.conf | |
| parent | 83b587e77baac9991a1073af99c82210d07e2b90 (diff) | |
| download | poky-264f19f6862dbab5abf7ff27a79bd088ac44b6c4.tar.gz | |
poky.conf: Add MACHINE to SDK_NAME
Avoid errors from:
MACHINE=qemux86-64 bitbake core-image-sato:do_populate_sdk
then:
MACHINE=genericx86-64 bitbake core-image-sato:do_populate_sdk
which gives:
ERROR: core-image-sato-1.0-r0 do_populate_sdk: The recipe core-image-sato is trying
to install files into a shared area when those files already exist. Those files and
their manifest location are:
deploy/sdk/poky-glibc-x86_64-core-image-sato-core2-64-toolchain-2.6+snapshot.host.manifest
(matched in manifest-qemux86_64x86_64-core-image-sato.populate_sdk)
deploy/sdk/poky-glibc-x86_64-core-image-sato-core2-64-toolchain-2.6+snapshot.testdata.json
(matched in manifest-qemux86_64x86_64-core-image-sato.populate_sdk)
deploy/sdk/poky-glibc-x86_64-core-image-sato-core2-64-toolchain-2.6+snapshot.target.manifest
(matched in manifest-qemux86_64x86_64-core-image-sato.populate_sdk)
deploy/sdk/poky-glibc-x86_64-core-image-sato-core2-64-toolchain-2.6+snapshot.sh
(matched in manifest-qemux86_64x86_64-core-image-sato.populate_sdk)
Please verify which recipe should provide the above files.
Adding MACHINE to the artefact name will avoid this. The issue was highlighted by
changes to the autobuilder configuration.
(From meta-yocto rev: 3614dd4aee9d19f1024edb6a36b2862c2d726c04)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-poky/conf/layer.conf')
0 files changed, 0 insertions, 0 deletions