From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] sstatesig: include native/cross/nativesdk deps in target signatures
Date: Mon, 27 Jan 2014 16:53:19 +0100 [thread overview]
Message-ID: <20140127155319.GI3718@jama> (raw)
In-Reply-To: <1390834275.17424.256.camel@ted>
[-- Attachment #1: Type: text/plain, Size: 2535 bytes --]
On Mon, Jan 27, 2014 at 02:51:15PM +0000, Richard Purdie wrote:
> On Sat, 2014-01-18 at 15:02 +0100, Martin Jansa wrote:
> > * I don't have any real evidence or good statistics for this, but when
> > comparing signature dumps from my big bitbake world builds I usually
> > see a lot of rebuilds caused by changes in .bbclasses and only very
> > rare would be the case where oe-core upgrade brings changes in -native
> > recipes and no change in .bbclasses used from target recipes
> > * changing the default to include them shouldn't cause significant
> > increase in rebuilds and sstate reuse a bit safer
> > * people working on toolchain (e.g. using gcc from AUTOREV) can easily
> > extend sstate_rundepfilter to ignore them again (it's easier than
> > removing existing filter), example how add own signature handler in
> > your layer is here:
> > https://github.com/openwebos/meta-webos/commit/9ac3a7c803e7793b3274e4998f167b6278db8042
> >
> > Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> > ---
> > meta/lib/oe/sstatesig.py | 4 ----
> > 1 file changed, 4 deletions(-)
>
> Whilst I merged this, we do have a problem here. This change means that
> the sstate is locked to the build system architecture.
>
> For example, if you have a 32 bit machine, it can't use any of the
> sstate built on a 64 bit machine and vice versa.
>
> I'm not sure what we do about this but its a problem...
Agreed, that's bad, I was testing it in setup where we publish the
sstate archive from the builder with the same architecture and have
similar setup building just -native recipes on 32bit for 32bit devs.
So this problem should have hit us as well, I'll recheck.
> Cheers,
>
> Richard
>
> > diff --git a/meta/lib/oe/sstatesig.py b/meta/lib/oe/sstatesig.py
> > index 3011f16..8b0e344 100644
> > --- a/meta/lib/oe/sstatesig.py
> > +++ b/meta/lib/oe/sstatesig.py
> > @@ -36,10 +36,6 @@ def sstate_rundepfilter(siggen, fn, recipename, task, dep, depname, dataCache):
> > if isPackageGroup(fn):
> > return False
> >
> > - # Drop native/cross/nativesdk dependencies from target recipes
> > - if isNative(depname) or isCross(depname) or isNativeSDK(depname):
> > - return False
> > -
> > # Exclude well defined machine specific configurations which don't change ABI
> > if depname in siggen.abisaferecipes and not isImage(fn):
> > return False
>
>
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2014-01-27 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 14:02 [PATCH 0/2] sstate improvements Martin Jansa
2014-01-18 14:02 ` [PATCH 1/2] sstatesig: include native/cross/nativesdk deps in target signatures Martin Jansa
2014-01-27 14:51 ` Richard Purdie
2014-01-27 15:53 ` Martin Jansa [this message]
2014-01-18 14:02 ` [PATCH 2/2] allarch: Set empty TARGET_PREFIX and TARGET_FPU Martin Jansa
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=20140127155319.GI3718@jama \
--to=martin.jansa@gmail.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