| Summary: | SSTATE confused with dbg dev and other packages | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | yoctoproject |
| Component: | bitbake | Assignee: | Richard Purdie <richard.purdie> |
| Status: | CLOSED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Undecided | CC: | poky.bs.watcher, poky.watcher, randy.macleod, yoctoproject |
| Version: | 3.2.2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
Some error has happened and you have no alternative but to remove the temp dir and rebuild. Setting SSTATE_DUPWHITELIST_append = " /"` is not a good work-around. If you can provide a way to reproduce this, please re-open the bug. Thanks for your reply! Interesting enough first me and then my collegue got this error, although we deleted the whole build folder (except for the conf directory). I'm trying to reproduce the error again, but I ssaw it with the zlib package as well. I will reply here, if I'm able to reproduce it again :) Thanks for your help so far. This happened today again.
I wiped my entire CACHE, SSTATE_CACHE and TMPDIR, but it still hapened.
I'm building under WSL2, maybe that helps.
Unfortunately I don't see a reason why this happenes, the error log doesn't really say anything and the offending packages have no *files* in common.
```
ERROR: autoconf-archive-2019.01.06-r0 do_package_write_ipk: 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:
/builddir/build/deploy/ipk/all/autoconf-archive_2019.01.06-r0_all.ipk
(not matched to any task)
/builddir/build/deploy/ipk/all/autoconf-archive-doc_2019.01.06-r0_all.ipk
(not matched to any task)
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: autoconf-archive-2019.01.06-r0 do_package_write_ipk: 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: Logfile of failure stored in: /builddir/build/tmp/work/all-unknown-linux/autoconf-archive/2019.01.06-r0/temp/log.do_package_write_ipk.16917
ERROR: Task (/builddir/source/poky/meta/recipes-devtools/autoconf-archive/autoconf-archive_2019.01.06.bb:do_package_write_ipk) failed with exit code '1'
ERROR: shadow-securetty-4.6-r3 do_package_write_ipk: The recipe shadow-securetty is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
/builddir/build/deploy/ipk/my_dist/shadow-securetty-dbg_4.6-r3_my_dist.ipk
(not matched to any task)
/builddir/build/deploy/ipk/my_dist/shadow-securetty_4.6-r3_my_dist.ipk
(not matched to any task)
/builddir/build/deploy/ipk/my_dist/shadow-securetty-dev_4.6-r3_my_dist.ipk
(not matched to any task)
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: shadow-securetty-4.6-r3 do_package_write_ipk: 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: Logfile of failure stored in: /builddir/build/tmp/work/my_dist-unknown-linux-gnueabi/shadow-securetty/4.6-r3/temp/log.do_package_write_ipk.18292
ERROR: Task (/builddir/source/poky/meta/recipes-extended/shadow/shadow-securetty_4.6.bb:do_package_write_ipk) failed with exit code '1'
ERROR: volatile-binds-1.0-r0 do_package_write_ipk: The recipe volatile-binds is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
/builddir/build/deploy/ipk/all/volatile-binds_1.0-r0_all.ipk
(not matched to any task)
/builddir/build/deploy/ipk/all/volatile-binds-dev_1.0-r0_all.ipk
(not matched to any task)
/builddir/build/deploy/ipk/all/volatile-binds-dbg_1.0-r0_all.ipk
(not matched to any task)
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: volatile-binds-1.0-r0 do_package_write_ipk: 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: Logfile of failure stored in: /builddir/build/tmp/work/all-unknown-linux/volatile-binds/1.0-r0/temp/log.do_package_write_ipk.18431
ERROR: Task (/builddir/source/poky/meta/recipes-core/volatile-binds/volatile-binds.bb:do_package_write_ipk) failed with exit code '1'
```
What can I do, to debug this problem further?
|
When I'm doing a clean build on the gatesgarth branch, the following error message happens: ``` ERROR: zlib-1.2.11-r0 do_package_write_ipk: The recipe zlib is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libz-src_1.2.11-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libz-dbg_1.2.11-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libz-staticdev_1.2.11-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libz-dev_1.2.11-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libz-doc_1.2.11-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libz1_1.2.11-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) 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: zlib-1.2.11-r0 do_package_write_ipk: 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: Logfile of failure stored in: /builddir/build/tmp/work/cortexa7t2hf-neon-vfpv4-unknown-linux-gnueabi/zlib/1.2.11-r0/temp/log.do_package_write_ipk.1701822 ERROR: Task (/builddir/source/poky/meta/recipes-core/zlib/zlib_1.2.11.bb:do_package_write_ipk) failed with exit code '1' ERROR: gdbm-1.18.1-r0 do_package_write_ipk: The recipe gdbm is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libgdbm-locale-uk_1.18.1-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libgdbm-locale-da_1.18.1-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libgdbm-locale-eo_1.18.1-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libgdbm-dev_1.18.1-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libgdbm-locale-ja_1.18.1-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libgdbm-locale-vi_1.18.1-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libgdbm-doc_1.18.1-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libgdbm-dbg_1.18.1-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libgdbm-bin_1.18.1-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libgdbm-locale-es_1.18.1-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libgdbm-locale-pl_1.18.1-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libgdbm-src_1.18.1-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libgdbm-locale-de_1.18.1-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libgdbm-locale-fi_1.18.1-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libgdbm-locale-pt-br_1.18.1-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libgdbm-locale-sv_1.18.1-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libgdbm-locale-fr_1.18.1-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libgdbm6_1.18.1-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libgdbm-locale-sr_1.18.1-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) /builddir/build/deploy/ipk/cortexa7t2hf-neon-vfpv4/libgdbm-compat4_1.18.1-r0_cortexa7t2hf-neon-vfpv4.ipk (not matched to any task) 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: gdbm-1.18.1-r0 do_package_write_ipk: 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: Logfile of failure stored in: /builddir/build/tmp/work/cortexa7t2hf-neon-vfpv4-unknown-linux-gnueabi/gdbm/1.18.1-r0/temp/log.do_package_write_ipk.1702550 ERROR: Task (/builddir/source/poky/meta/recipes-support/gdbm/gdbm_1.18.1.bb:do_package_write_ipk) failed with exit code '1' ``` Currently I'm doing `SSTATE_DUPWHITELIST_append = " /"`, but that's something I want to do in the future. What is the culprit here for theses errors? If you need more information, I'm glad to provide it.