Re: examine SSTATE_MIRRORS differences

[Martin Jansa <martin.jansa@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]

On Fri, Aug 01, 2014 at 01:46:40PM +0200, Bart Jansseune wrote:
> Hello,
> 
> I'm trying to setup a SSTATE_MIRROR using a fast build server so that a slow virtual machine doesn't have to rebuild everything.
> Both are Ubuntu 14.04 64 bit machines and use the same poky release (daisy).
> What I notice is that for some components the cache is used eg perl-native but not for others.
> I understand that once there is a delta between both machines, all dependent packages also mismatch and need to be rebuilt.
> 
> How do you figure out where things start diverging?
> 
> Are there requirements on the tools of the build to ensure that SSTATE_MIRROR can be used effectively? E.g. the gcc version on both machines might need to be the same.

Run openembedded-core/scripts/sstate-diff-machines.sh on both machines
and compare list.M files in generated folders.

That will give you pointers to interesting .sigdata files, which you can
compare with bitbake-diffsigs - which will reveal more .sigdata files
and so on until you find root cause.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]