From: Gary Thomas <gary@mlbassoc.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: SSTATE MIRRORS only partly working?
Date: Tue, 17 May 2011 16:52:12 -0600 [thread overview]
Message-ID: <4DD2FC1C.9040409@mlbassoc.com> (raw)
In-Reply-To: <1305629810.3424.224.camel@rex>
On 05/17/2011 04:56 AM, Richard Purdie wrote:
> On Wed, 2011-05-11 at 08:11 -0600, Gary Thomas wrote:
>> Trying my SSTATE_MIRROR test with a recent Poky tree, I find
>> that for the most part, it doesn't work as expected (at least
>> not as I expect).
>>
>> Here's my test setup:
>> * Create a complete build
>> % . /local/poky/oe-init-build-env /local/build_orig
>> % bitbake SOME-RECIPE
>> * Use that build for the SSTATE_MIRROR
>> % . /local/poky/oe-init-build-env /local/build_test
>> -- edit conf/local.conf to have these lines:
>> SSTATE_MIRRORS ?= "\
>> file://.* file:///local/build_orig/sstate-cache/"
>> % bitbake SOME-RECIPE
>>
>> What I find is that this second build is rebuilding a lot of
>> things, most strikingly the -native packages. Looking into
>> it, I see that the original build creates
>> sstate-pseudo-native-i686-linux-1.0-r0-i686-2-999fef0f7f260a6672c3678a831fa36f_populate-sysroot.tgz
>> but when the test build runs, it's looking for
>> sstate-pseudo-native-i686-linux-1.0-r0-i686-2-feb469d055bfc4f32074e7e9499eaf22_populate-sysroot.tgz
>>
>> Odd, but it's not always different, for example
>> sstate-perl-native-i686-linux-5.12.3-r2-i686-2-75d16ce5b7c945262d819c24f59d1c9f_populate-sysroot.tgz
>> is the same in both builds and is thus shared.
>>
>> Note that nothing else has changed, other than the process above.
>> The COREBASE tree is identical/untouched.
>>
>> Am I missing something here?
>
> Did you try comparing the siginfo/sigdata files using bitbake-diffsigs?
>
> That should give some clues about what changed.
Odd - I just tried this again after merging up to 31a763d7bd97f57586c6bb9ec223bfa7e333d21c
I can't make it happen again - SSTATE_MIRROR is working as I expect. Sadly, I don't have
the trees from the previous attempt around any more to diagnose.
My previous merge of f285547a3820f394f7dd9dd974f876353d4ddc6c is when this happened.
I don't see anything obvious that changed between these two revisions that
might affect this, but I'm happy it seems to be working again. If it breaks
again, I'll know what to look at.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2011-05-17 22:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 14:11 SSTATE MIRRORS only partly working? Gary Thomas
2011-05-17 10:56 ` Richard Purdie
2011-05-17 22:52 ` Gary Thomas [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=4DD2FC1C.9040409@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=poky@yoctoproject.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 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.