From: Joshua Lock <joshua.g.lock@linux.intel.com>
To: akuster808 <akuster808@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] multilib_header: avoid sstate checksum issues for -nativesdk recipes
Date: Fri, 30 Sep 2016 16:52:35 +0100 [thread overview]
Message-ID: <1475250755.3096.11.camel@linux.intel.com> (raw)
In-Reply-To: <353ba145-4e04-d586-8bf9-d9058339efbd@gmail.com>
On Fri, 2016-09-30 at 08:29 -0700, akuster808 wrote:
>
> On 09/30/2016 02:09 AM, Joshua Lock wrote:
> >
> > Much as with -native recipes, as addressed in commit
> > b15730caf0d4c40271796887505507f2501958bb, arch specific variables
> > like MIPSPKGSFX_ABI were affecting -nativesdk sstate checksums for
> > recipes like nativesdk-glibc-initial.
> Since commit
>
> b15730caf0d4c40271796887505507f2501958bb is in Jethro and Krogoth, do
> both of those branch need this fix?
This patch improves sstate object reuse for nativesdk recipes when
switching between a mips and non-mips MACHINE.
It's no doubt useful to have in krogoth and jethro too.
Joshua
> - armin
>
> >
> >
> > Disable multilib_header for nativesdk as we don't use multilibs in
> > this scenario.
> >
> > [YOCTO #10320]
> >
> > Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
> > ---
> > meta/classes/multilib_header.bbclass | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/meta/classes/multilib_header.bbclass
> > b/meta/classes/multilib_header.bbclass
> > index 5ee0a2d..304c28e 100644
> > --- a/meta/classes/multilib_header.bbclass
> > +++ b/meta/classes/multilib_header.bbclass
> > @@ -52,3 +52,8 @@ oe_multilib_header() {
> > oe_multilib_header_class-native () {
> > return
> > }
> > +
> > +# Nor do we need multilib headers for nativesdk builds.
> > +oe_multilib_header_class-nativesdk () {
> > + return
> > +}
>
prev parent reply other threads:[~2016-09-30 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 9:09 [PATCH] multilib_header: avoid sstate checksum issues for -nativesdk recipes Joshua Lock
2016-09-30 15:29 ` akuster808
2016-09-30 15:52 ` Joshua Lock [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=1475250755.3096.11.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.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