On Tue, 2022-07-05 at 18:39 +0200, Alexander Kanavin wrote:
> Otherwise lock files appearing and disappearing can interfere
> with reproducibility code enumerating source files in do_unpack():
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/3745/steps/14/logs/stdio
>
> Signed-off-by: Alexander Kanavin <a...@linutronix.de>
> ---
> meta/classes/externalsrc.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/externalsrc.bbclass
> b/meta/classes/externalsrc.bbclass
> index 90792a737b..b326f10050 100644
> --- a/meta/classes/externalsrc.bbclass
> +++ b/meta/classes/externalsrc.bbclass
> @@ -88,7 +88,7 @@ python () {
> bb.build.deltask(task, d)
> elif os.path.realpath(d.getVar('S')) ==
> os.path.realpath(d.getVar('B')):
> # Since configure will likely touch ${S}, ensure only we
> lock so one task has access at a time
> - d.appendVarFlag(task, "lockfiles", " ${S}/singletask.lock")
> + d.appendVarFlag(task, "lockfiles", " ${T}/singletask.lock")
>
> for funcname in [task, "base_" + task, "kernel_" + task]:
> # We do not want our source to be wiped out, ever
> (kernel.bbclass does this for do_clean)
Not an option I'm afraid as it is in ${S} for a reason. This is two
recipes both pointing at the same source (e.g. a recipe and it's
BBCLASSEXTEND native version) can work.
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#167671):
https://lists.openembedded.org/g/openembedded-core/message/167671
Mute This Topic: https://lists.openembedded.org/mt/92188777/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
