Another staging question

[Gary Thomas <gary@mlbassoc.com>]

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?

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.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------