Add archiver folder to SSTATE_DUPWHITELIST
Bitbake fails with an error message such as "The recipe bla is trying to install files into a shared area when those files already exist." Conditions:
- The archiver class is active
- Bitbake is called more than once e.g. to compile two images for different architectures
At least for me, the patch bellow seems to solve the issue...
From 5ca1a06c7e004f9ecda2e34c49e0cf5ad490582a Mon Sep 17 00:00:00 2001
From: Adrian <[email protected]>
Date: Fri, 13 Mar 2015 17:39:45 +0100
Subject: [PATCH] Add archiver folder to SSTATE_DUPWHITELIST
Without this patch the source archiver class is not allowed to archive the same source archive for different builds.
Signed-off-by Adrian <[email protected]>
--- meta/classes/sstate.bbclass | 2 ++ 1 file changed, 2 insertions(+)
meta/classes/sstate.bbclass +2 -0
@@ -25,6 +25,8 @@ SSTATE_EXTRAPATH[vardepvalue] = "" SSTATE_DUPWHITELIST = "${DEPLOY_DIR_IMAGE}/ ${DEPLOY_DIR}/licenses/ ${DEPLOY_DIR_RPM}/all/" # Avoid docbook/sgml catalog warnings for now SSTATE_DUPWHITELIST += "${STAGING_ETCDIR_NATIVE}/sgml ${STAGING_DATADIR_NATIVE}/sgml" +# Archive the sources for many architectures in one deploy folder +SSTATE_DUPWHITELIST += "${DEPLOY_DIR_SRC}" SSTATE_SCAN_FILES ?= "*.la *-config *_config" SSTATE_SCAN_CMD ?= 'find ${SSTATE_BUILDDIR} \( -name "${@"\" -o -name \"".join(d.getVar("SSTATE_SCAN_FILES", True).split())}" \) -type f'
Signature · 1 line
1.9.1