From: Mark Hatle <mark.hatle@windriver.com>
To: poky@yoctoproject.org
Subject: Re: Another staging question
Date: Tue, 09 Nov 2010 09:32:39 -0600 [thread overview]
Message-ID: <4CD96997.60802@windriver.com> (raw)
In-Reply-To: <4CD94ADD.2090607@mlbassoc.com>
On 11/9/10 7:21 AM, Gary Thomas wrote:
> I've found another peculiarity with the new staging scheme(*).
> I have two target platforms, which for all intents and purposes
> are identical - both are Motorola MPC83xx (e300 core). The only
> reason for two target machines is the kernel, plus platform specifics.
>
> I built totally from scratch (no SSTATE_MIRRORS) for target machine A.
> I then tested the staging by building in a new tree, again for machine A.
> This worked great - the build used mostly the staged packages. About
> the only things that were rebuilt were the target specific packages.
>
> When I tried it for machine B, again in a totally empty directory, using
> the 'sstate-cache' directory of the first build as SSTATE_MIRRORS, all of
> the toolchain was rebuilt (GCC and friends), but there was no need, the
> staged version should have been used.
>
> Is this expected?
> What could I do to fix it?
This tells me that the checksumming code found something that it believed
changed the system behavior. Likely a machine type or CFLAG or similar.
RP -- is there a way to determine "what changed [and why]" without re-running
the build? We found this invaluable when debugging the WR build system's
checksumming, configuration files and packaging recipes.
--Mark
> Thanks
>
> (*) I'm very happy that the new staging is starting to work better.
> As is, it's a great leap forward; I'm just hopeful that the remaining
> kinks can be worked out. I'll be glad to help in this any way I can.
>
next prev parent reply other threads:[~2010-11-09 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 13:21 Another staging question Gary Thomas
2010-11-09 15:32 ` Mark Hatle [this message]
2010-11-23 5:33 ` Tian, Kevin
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=4CD96997.60802@windriver.com \
--to=mark.hatle@windriver.com \
--cc=poky@yoctoproject.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