diff options
author | Yi Zhao <yi.zhao@windriver.com> | 2018-09-06 06:33:49 +0000 |
---|---|---|
committer | Jia Zhang <zhang.jia@linux.alibaba.com> | 2018-09-06 16:57:21 +0800 |
commit | ec8e07c9fd1625f0aef96bac8ea3c84f773cbf3d (patch) | |
tree | 6cf5d5495d9e95284dfe834cf6d0e3a1bd9a1e0f | |
parent | e778286de8294d1c621d6e7619faac77d88e0f10 (diff) | |
download | meta-secure-core-ec8e07c9fd1625f0aef96bac8ea3c84f773cbf3d.tar.gz |
efitools: add the deployed artifacts to SSTATE_DUPWHITELIST
The oe-core commit 05f6042a40bb772f7ce8d6819c5b2937d8c9808d removed
DEPLOY_DIR_IMAGE from SSTATE_DUPWHITELIST which caused a do_depoy error
when enable multilib:
$ bitbake efitools lib32-efitools
ERROR: lib32-efitools-1.7.0+gitAUTOINC+0649468475-r0 do_deploy: The
recipe lib32-efitools is trying to install files into a shared area when
those files already exist. Those files and their manifest location are:
/buildarea/build/tmp-glibc/deploy/images/qemux86-64/LockDown.efi
(matched in manifest-qemux86_64-efitools.deploy)
Please verify which recipe should provide the above files.
Add the deployed artifacts to SSTATE_DUPWHITELIST to fix this issue.
Signed-off-by: Yi Zhao <yi.zhao@windriver.com>
-rw-r--r-- | meta-efi-secure-boot/recipes-bsp/efitools/efitools.inc | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/meta-efi-secure-boot/recipes-bsp/efitools/efitools.inc b/meta-efi-secure-boot/recipes-bsp/efitools/efitools.inc index 8dadf60..0217818 100644 --- a/meta-efi-secure-boot/recipes-bsp/efitools/efitools.inc +++ b/meta-efi-secure-boot/recipes-bsp/efitools/efitools.inc | |||
@@ -61,3 +61,5 @@ do_install() { | |||
61 | } | 61 | } |
62 | 62 | ||
63 | FILES_${PN} += "${EFI_BOOT_PATH}" | 63 | FILES_${PN} += "${EFI_BOOT_PATH}" |
64 | |||
65 | SSTATE_DUPWHITELIST += "${DEPLOY_DIR_IMAGE}/LockDown.efi" | ||