From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: joaomarcos.costa@bootlin.com, openembedded-core@lists.openembedded.org
Cc: thomas.petazzoni@bootlin.com, raj.khem@gmail.com
Subject: Re: [OE-core] [PATCH v2 4/5] llvm-project-source.inc: add vardeps to do_preconfigure
Date: Sun, 28 Jun 2026 11:25:49 +0100 [thread overview]
Message-ID: <9ec404ced0ab0f4762d9c4e863ffe67de4baa025.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260623120818.110754-5-joaomarcos.costa@bootlin.com>
On Tue, 2026-06-23 at 14:08 +0200, Joao Marcos Costa via lists.openembedded.org wrote:
> The task's signature should change if CLANG_EXTRA_OE_DISTRO and/or
> CLANG_EXTRA_OE_VENDORS, considering the couple of for loops in
> do_preconfigure iterate over their values.
>
> By adding them to 'vardeps', bitbake will correctly detect if
> do_preconfigure needs to be executed.
>
> Signed-off-by: João Marcos Costa <joaomarcos.costa@bootlin.com>
> ---
> meta/recipes-devtools/clang/llvm-project-source.inc | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-devtools/clang/llvm-project-source.inc b/meta/recipes-devtools/clang/llvm-project-source.inc
> index 85b5ef06dc..84d4bae0ab 100644
> --- a/meta/recipes-devtools/clang/llvm-project-source.inc
> +++ b/meta/recipes-devtools/clang/llvm-project-source.inc
> @@ -90,4 +90,5 @@ python do_preconfigure() {
>
> do_patch[vardepsexclude] += "MULTILIBS MULTILIB_VARIANTS"
> addtask do_preconfigure after do_patch
> +do_preconfigure[vardeps] += "CLANG_EXTRA_OE_DISTRO CLANG_EXTRA_OE_VENDORS"
> do_create_spdx[depends] += "${PN}:do_preconfigure"
We require that tasks can run in isolation and that can happen for many
different reasons. Your fix does improve things a bit but it doesn't
fix the underlying problem.
Ideally we'd change the search/replace expressions so that they always
change/update the required entries. That does sometimes need a bit more
thought about how the expressions work and it means you can't use
replacement tokens (unless as a comment on the line above?).
Another less optimal way to improve things is to change do_preconfigure
into a postfunc for do_unpack, but it wouldn't be able to change things
altered by do_patch. You can't make it a do_patch postfunc as it could
still have the current issues with the changes not being updated.
Cheers,
Richard
next prev parent reply other threads:[~2026-06-28 10:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 12:08 [PATCH v2 0/5] llvm/clang: fix some syntax issues in llvm-project-source João Marcos Costa
2026-06-23 12:08 ` [PATCH v2 1/5] llvm-project-source.inc: fix string replacements in do_preconfigure João Marcos Costa
2026-06-23 12:08 ` [PATCH v2 2/5] llvm-project-source.inc: fix end of line in triple variable João Marcos Costa
2026-06-23 12:08 ` [PATCH v2 3/5] clang/llvm: add missing instance of Distro class in Linux.cpp João Marcos Costa
2026-06-23 12:08 ` [PATCH v2 4/5] llvm-project-source.inc: add vardeps to do_preconfigure João Marcos Costa
2026-06-28 10:25 ` Richard Purdie [this message]
2026-06-29 8:09 ` [OE-core] " Joao Marcos Costa
2026-06-29 9:39 ` Richard Purdie
2026-06-29 9:51 ` Joao Marcos Costa
2026-06-23 12:08 ` [PATCH v2 5/5] llvm-project-source.inc: add vardeps to do_unpack João Marcos Costa
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=9ec404ced0ab0f4762d9c4e863ffe67de4baa025.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=joaomarcos.costa@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=thomas.petazzoni@bootlin.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