From: Gary Thomas <gary@mlbassoc.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: paul.eggleton@linux.intel.com, poky@pokylinux.org
Subject: Re: [PATCH 0/1] Fix weird rebuild issue even when sstate signature doesn't change
Date: Wed, 15 Dec 2010 09:10:16 -0700 [thread overview]
Message-ID: <4D08E868.6090606@mlbassoc.com> (raw)
In-Reply-To: <1292404338.26558.1582.camel@rex>
On 12/15/2010 02:12 AM, Richard Purdie wrote:
> On Tue, 2010-12-14 at 21:40 +0800, Kevin Tian wrote:
>> This patch is to fix one weird issue I've keeping seeing recently when using sstate.
>> Even with a minimal build, there're around 50 recipes rebuilt from scratch even though
>> sstate packages in sstate_cache do match. Actually the end result is to just overwrite
>> sstate packages again with same sigature for those recipes.
>> https://lists.yoctoproject.org/pipermail/poky/2010-December/001063.html
>>
>> The cause for this mess is from misinterpretation of the index of a list, which then
>> points to wrong setscene tasks instead of desired ones. The end result is that some
>> tasks which don't need execution are scheduled while other setscene tasks which need
>> run are simply skipped.
>>
>> It's based on Paul's sstate branch.
>
> I've merged this patch into master, good catch and hopefully this gets
> sstate into a good working state.
>
> I've merged an updated version of Paul's sstate branch too.
>
> I'm hoping this makes sstate packages finally usable!
Mucho bettero (TM) :-)
I just tried this from master and at least on the same machine
but different build paths, it performed much as hoped. My initial
build (step 1) took some 165 minutes, building the same target using
the sstate cache from step 1 took only 22. The only packages rebuilt
during step 2 were the kernel and the image tasks (I tested this with
my own image+kernel recipes, so it's OK if this differs a little from
other's results).
Bottom line, it seems to be working much better now.
Note to Paul: I also still see lots of LD_PRELOAD messages like
ERROR: ld.so: object 'libpseudo.so' from LD_PRELOAD cannot be preloaded: ignored.
but they did not seem to affect the result.
Note to Richard: I'm still seeing a ton of Noexec messages every time I rebuild
a package in this tree. I thought I understood you to say they should happen
at most once?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2010-12-15 16:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 13:40 [PATCH 0/1] Fix weird rebuild issue even when sstate signature doesn't change Kevin Tian
2010-12-15 9:12 ` Richard Purdie
2010-12-15 11:12 ` Tian, Kevin
2010-12-15 16:10 ` Gary Thomas [this message]
2010-12-15 16:17 ` Paul Eggleton
2010-12-16 1:43 ` Tian, Kevin
2010-12-16 8:45 ` Tian, Kevin
2010-12-16 9:48 ` about 'noexec' message Tian, Kevin
2010-12-16 15:19 ` Richard Purdie
2010-12-17 2:48 ` Tian, Kevin
2010-12-17 4:23 ` Tian, Kevin
2010-12-20 15:04 ` Richard Purdie
2010-12-16 15:29 ` [PATCH 0/1] Fix weird rebuild issue even when sstate signature doesn't change Richard Purdie
2010-12-20 21:23 ` Richard Purdie
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=4D08E868.6090606@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=paul.eggleton@linux.intel.com \
--cc=poky@pokylinux.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.