From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patrick Ohly <patrick.ohly@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3 3/8] -cross recipes: ignore TARGET_ARCH sstate hash
Date: Tue, 11 Apr 2017 19:25:53 +0100 [thread overview]
Message-ID: <1491935153.12091.37.camel@linuxfoundation.org> (raw)
In-Reply-To: <c647b8b4229e8862b8066f52aaefee133a65e6ee.1491922350.git-series.patrick.ohly@intel.com>
I'd tweak the subject line to recipes/*-cross:
On Tue, 2017-04-11 at 16:56 +0200, Patrick Ohly wrote:
> "yocto-compat-layer.py --machines" showed that shared packages like
> gcc-cross-powerpc64 have a sstate signature that depends on
> TUNEFLAGS. As a result, there are unnecessary rebuilds and potential
> conflicts in a multiconfig.
>
> That's due to the way how TARGET_ARCH is set. Richard Purdie
> suggested
> setting TARGET_ARCH[vardepvalue] as fix, which works. It would be
> shorter to do that in cross.inc instead of repeating the relevant
> line
> in different recipes, but Richard was concerned about potential
> side-effects in other usages of cross.inc.
s/cross.inc/cross.bbclass/g
Cheers,
Richard
next prev parent reply other threads:[~2017-04-11 18:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 14:56 [PATCH v3 0/8] yocto-compat-layer: bitbake-diffsigs support + per machine checks + OE-core fixes Patrick Ohly
2017-04-11 14:56 ` [PATCH v3 1/8] go-cross: avoid libgcc dependency Patrick Ohly
2017-04-11 14:56 ` [PATCH v3 2/8] gdb-cross: avoid tune specific paths Patrick Ohly
2017-04-11 15:16 ` Mark Hatle
2017-04-11 16:29 ` Patrick Ohly
2017-04-11 16:56 ` Khem Raj
2017-04-11 17:19 ` Richard Purdie
2017-04-11 18:12 ` Mark Hatle
2017-04-11 14:56 ` [PATCH v3 3/8] -cross recipes: ignore TARGET_ARCH sstate hash Patrick Ohly
2017-04-11 18:25 ` Richard Purdie [this message]
2017-04-11 18:28 ` Patrick Ohly
2017-04-11 14:56 ` [PATCH v3 4/8] yocto-compat-layer: include bitbake-diffsigs output Patrick Ohly
2017-04-11 14:56 ` [PATCH v3 5/8] yocto-compat-layer: also determine tune flags for each task Patrick Ohly
2017-04-11 14:56 ` [PATCH v3 6/8] yocto-compat-layer: add --additional-layers Patrick Ohly
2017-04-11 14:57 ` [PATCH v3 7/8] yocto-compat-layer: test signature differences when setting MACHINE Patrick Ohly
2017-04-11 14:57 ` [PATCH v3 8/8] yocto-compat-layer: better handling of per-machine world build breakage Patrick Ohly
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=1491935153.12091.37.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=patrick.ohly@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.