Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: RE: [OE-core] [PATCH] gcc-source: Ensure deploy_date_epoch sstate hash doesn't change
Date: Mon, 7 Nov 2022 18:37:32 +0000	[thread overview]
Message-ID: <7043881828034920aa5327304ff2ed75@axis.com> (raw)
In-Reply-To: <20221107142609.1509126-1-richard.purdie@linuxfoundation.org>

> -----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.purdie@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



      reply	other threads:[~2022-11-07 18:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 14:26 [PATCH] gcc-source: Ensure deploy_date_epoch sstate hash doesn't change Richard Purdie
2022-11-07 18:37 ` Peter Kjellerstedt [this message]

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=7043881828034920aa5327304ff2ed75@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /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