Re: [yocto] Shared state doesn't live up to its name?

2016-12-01 Thread Gary Thomas
On 2016-12-01 18:35, Paul Eggleton wrote: On Thu, 01 Dec 2016 10:27:50 Gary Thomas wrote: I have a build machine where I build for lots of targets. On all of these targets (save a primary), I set the SSTATE_MIRROR to point to the sstate-cache of the primary target. I always build for the

Re: [yocto] Shared state doesn't live up to its name?

2016-12-01 Thread Paul Eggleton
On Thu, 01 Dec 2016 10:27:50 Gary Thomas wrote: > I have a build machine where I build for lots of targets. On > all of these targets (save a primary), I set the SSTATE_MIRROR > to point to the sstate-cache of the primary target. I always build > for the primary target first, then later the

Re: [yocto] Shared state doesn't live up to its name?

2016-12-01 Thread Martin Jansa
Compare the signatures of these 2 native builds. I'm still using sstate-diff-machines.sh to create archives of sstate signatures for interesting builds, so that I can easily compare them with other builds or the same build performed on different builder to see why something wasn't reused form

[yocto] Shared state doesn't live up to its name?

2016-12-01 Thread Gary Thomas
I have a build machine where I build for lots of targets. On all of these targets (save a primary), I set the SSTATE_MIRROR to point to the sstate-cache of the primary target. I always build for the primary target first, then later the secondary ones. For the most part, the sstate mechanism