> -----Original Message-----
> From: openembedded-core@lists.openembedded.org 
> <openembedded-core@lists.openembedded.org> On Behalf Of Richard Purdie
> Sent: den 7 november 2022 15:26
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH] gcc-source: Ensure deploy_date_epoch sstate hash 
> doesn't change
> 
> Currently if you switch machines, gcc-source do_deploy_source_date_epoch
> would reun-run as the stamps are tune specific. This hasn't caused much

Change "reun-run" to "re-run".

> of an issue until now however if we fix the gcc recipes to reuse the

For better readability, I would change the above line to:

of an issue until now. However, if we fix the gcc recipes to reuse the

> timestamp from this task, it does then create problems.
> 
> Copy code from allarch to ensire this task hash doesn't change between

Change "ensire" to "ensure".

> machines/tunes.
> 
> Signed-off-by: Richard Purdie <richard.pur...@linuxfoundation.org>
> ---
>  meta/recipes-devtools/gcc/gcc-source.inc | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/meta/recipes-devtools/gcc/gcc-source.inc 
> b/meta/recipes-devtools/gcc/gcc-source.inc
> index bf33a4b31ff..265bcf4bef5 100644
> --- a/meta/recipes-devtools/gcc/gcc-source.inc
> +++ b/meta/recipes-devtools/gcc/gcc-source.inc
> @@ -17,6 +17,13 @@ STAMPCLEAN = "${STAMPS_DIR}/work-shared/gcc-${PV}-*"
>  INHIBIT_DEFAULT_DEPS = "1"
>  DEPENDS = ""
>  PACKAGES = ""
> +TARGET_ARCH = "allarch"
> +TARGET_AS_ARCH = "none"
> +TARGET_CC_ARCH = "none"
> +TARGET_LD_ARCH = "none"
> +TARGET_OS = "linux"
> +baselib = "lib"
> +PACKAGE_ARCH = "all"
> 
>  B = "${WORKDIR}/build"
> 
> --
> 2.34.1

//Peter

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#172930): 
https://lists.openembedded.org/g/openembedded-core/message/172930
Mute This Topic: https://lists.openembedded.org/mt/94866899/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to