Hello,<br /><br />It seems that I get the same behavior, but with other steps: having 2 images that uses the same dtbs for booting. First image will complete the build fine and the dtbs are in the deploydir.<br />The 2nd image does not complete the build because the dtbs are already in the deploydir.<br />This happens because of the introduction of the do_copy_boot_files_setscene() where this verification takes place. From my perspective a possible solution would be to copy those files<br />only if they don't exist.<br /><br />diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass<br />index d9fc04eb..070a14dd 100644<br />--- a/meta/classes/image.bbclass<br />+++ b/meta/classes/image.bbclass<br />@@ -393,7 +393,10 @@ do_copy_boot_files() {<br />             die "${file} not found"<br />         fi<br /> <br />-        cp -f "$dtb" "${DEPLOYDIR}/"<br />+        dtb_name=$(basename "${file}")<br />+        if [ ! -f "${DEPLOY_DIR_IMAGE}/${dtb_name}" ]; then<br />+            cp -f "$dtb" "${DEPLOYDIR}/"<br />+        fi<br />     done<br /> }<br /> addtask copy_boot_files before do_rootfs_postprocess after do_rootfs_install<br /><br /><br /><br /><br /><div class="gmail_quote"><div dir="auto" class="gmail_attr">On Wednesday, January 31, 2024 at 4:45:48 PM UTC+2 Ilia Skochilov wrote:<br/></div><blockquote class="gmail_quote" style="margin: 0 0 0 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">When building different distros with the same machine
<br>(e.g., phyboard-mira-bullseye and phyboard-mira-bookworm) the following error
<br>occurs:
<br>do_copy_boot_files: The recipe isar-image-base is trying to install files
<br>into a shared area when those files already exists.
<br>It happens when some files have the same names (e.g., dtb files) for different
<br>distros.
<br>
<br>Signed-off-by: Ilia Skochilov &lt;<a href data-email-masked rel="nofollow">iskoc...@ilbers.de</a>&gt;
<br>---
<br> RECIPE-API-CHANGELOG.md | 8 ++++++++
<br> meta/conf/bitbake.conf  | 2 +-
<br> 2 files changed, 9 insertions(+), 1 deletion(-)
<br>
<br>diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
<br>index bea1287..c9c1eae 100644
<br>--- a/RECIPE-API-CHANGELOG.md
<br>+++ b/RECIPE-API-CHANGELOG.md
<br>@@ -566,3 +566,11 @@ supported, but a warning is issued when it is used. Future versions will drop
<br> When building a custom kernel module, the `KBuild` file might be located in
<br> a subdirectory. To support this use-case, set `MODULE_DIR=$(PWD)/subdir` in
<br> the module build recipe.
<br>+
<br>+### Change DEPLOY_DIR_IMAGE
<br>+Change DEPLOY_DIR_IMAGE from ${DEPLOY_DIR}/images/${MACHINE} to
<br>+${DEPLOY_DIR}/images/${MACHINE}-${DISTRO}. When building different distros
<br>+with the same machine the following error occurs:
<br>+do_copy_boot_files: The recipe isar-image-base is trying to install files
<br>+into a shared area when those files already exists. It happens when some
<br>+files have the same names (e.g., dtb files) for different distros.
<br>diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
<br>index 80dc01c..006ac14 100644
<br>--- a/meta/conf/bitbake.conf
<br>+++ b/meta/conf/bitbake.conf
<br>@@ -56,7 +56,7 @@ WORKDIR = &quot;${TMPDIR}/work/${DISTRO}-${DISTRO_ARCH}/${PN}/${PV}-${PR}&quot;
<br> GIT_DL_LINK_DIR = &quot;${TMPDIR}/work/${DISTRO}-${DISTRO_ARCH}&quot;
<br> DEPLOY_DIR_BOOTSTRAP = &quot;${DEPLOY_DIR}/bootstrap&quot;
<br> DEPLOY_DIR_SDKCHROOT = &quot;${DEPLOY_DIR}/sdkchroot&quot;
<br>-DEPLOY_DIR_IMAGE = &quot;${DEPLOY_DIR}/images/${MACHINE}&quot;
<br>+DEPLOY_DIR_IMAGE = &quot;${DEPLOY_DIR}/images/${MACHINE}-${DISTRO}&quot;
<br> DL_DIR ?= &quot;${TOPDIR}/downloads&quot;
<br> SSTATE_DIR ?= &quot;${TOPDIR}/sstate-cache&quot;
<br> SSTATE_MANIFESTS = &quot;${TMPDIR}/sstate-control/${DISTRO}-${DISTRO_ARCH}&quot;
<br>-- 
<br>2.39.2
<br>
<br></blockquote></div>