From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: pio.lobacz@gmail.com, openembedded-core@lists.openembedded.org,
JPEWhacker@gmail.com
Subject: Re: [OE-core][PATCH] classes/create-spdx-2.2: Fix SPDXDIR affecting multiconfig machines
Date: Mon, 10 Feb 2025 13:42:41 +0000 [thread overview]
Message-ID: <3980bb85057c3c2402714d4c51676d628bf2ef52.camel@linuxfoundation.org> (raw)
In-Reply-To: <20250210125047.2644290-1-pio.lobacz@gmail.com>
On Mon, 2025-02-10 at 13:50 +0100, Piotr Łobacz via lists.openembedded.org wrote:
> Currently SPDXDIR is pointing to `${WORKDIR}/spdx` which means that the by-id
> and by-namespace SPDX files are created without differentiation between machines.
> This means that for two machines using a common package architecture
> (e.g. genericx86-64 and qqemux86-64), there would be overlapping files. This means
> that the build of one can remove files from the other leading to build failures. An
> example would be:
>
> MACHINE=qemux86-64 bitbake core-image-minimal
> MACHINE=genericx86-64 bitbake core-image-minimal
> MACHINE=qemux86-64 bitbake linux-yocto -c clean
> MACHINE=genericx86-64 bitbake core-image-minimal -C rootfs
>
> To fix this, add MACHINE_ARCH to the SPDXDIR path used for the files in order
> to differentiate packages' dependencies between machines.
>
> This commit fixes issue repored by Khem [1]
>
> [1] https://patchwork.yoctoproject.org/comment/13577/
>
> Signed-off-by: Piotr Łobacz <pio.lobacz@gmail.com>
> ---
> meta/classes/create-spdx-2.2.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/create-spdx-2.2.bbclass b/meta/classes/create-spdx-2.2.bbclass
> index ade1a04be3..9e228891ab 100644
> --- a/meta/classes/create-spdx-2.2.bbclass
> +++ b/meta/classes/create-spdx-2.2.bbclass
> @@ -11,7 +11,7 @@ DEPLOY_DIR_SPDX ??= "${DEPLOY_DIR}/spdx"
> CVE_PRODUCT ??= "${BPN}"
> CVE_VERSION ??= "${PV}"
>
> -SPDXDIR ??= "${WORKDIR}/spdx"
> +SPDXDIR ??= "${WORKDIR}/spdx/${MACHINE_ARCH}"
> SPDXDEPLOY = "${SPDXDIR}/deploy"
> SPDXWORK = "${SPDXDIR}/work"
> SPDXIMAGEWORK = "${SPDXDIR}/image-work"
I suspect this is going to cause other challenges since the task stamp
isn't machine specific as far as I know but this change would require
it to be and force all of the SPDX tasks to be machine specific.
Cheers,
Richard
next prev parent reply other threads:[~2025-02-10 13:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 12:50 [OE-core][PATCH] classes/create-spdx-2.2: Fix SPDXDIR affecting multiconfig machines Piotr Łobacz
2025-02-10 13:42 ` Richard Purdie [this message]
2025-02-10 16:58 ` Piotr Łobacz
2025-02-10 17:50 ` Joshua Watt
2025-02-10 20:50 ` Piotr Łobacz
2025-02-12 22:06 ` Joshua Watt
2025-02-13 8:56 ` Piotr Łobacz
2025-02-13 8:59 ` Piotr Łobacz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3980bb85057c3c2402714d4c51676d628bf2ef52.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=JPEWhacker@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pio.lobacz@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox