<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 10, 2013 at 7:32 AM, Martin Jansa <span dir="ltr"><<a href="mailto:martin.jansa@gmail.com" target="_blank">martin.jansa@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Tue, Dec 10, 2013 at 07:44:49AM +0100, Mike Looijmans wrote:<br>
> I've been struggling with this for a few days.<br>
><br>
> We have a build server that build various images overnight. One of the<br>
> packages in that image is "fpga-image", which takes more than an hour to build.<br>
><br>
> We have been sharing the the build server's sstate-cache via HTTP and this has<br>
> worked excellently up until yesterday.<br>
><br>
> The current situation is that a client will grab everything from the<br>
> buildserver's HTTP sstate-cache, potentially finishing a build from scratch in<br>
> about five minutes. However, for some reason, the fpga-image does not fall<br>
> into this category, and eache machine insists on re-building it from scratch.<br>
> I've been trying to debug this, but the sstate-cache is on another machine. I<br>
> tried copying part of the build server's sstate-cache onto my machine, but<br>
> that only results in "bitbake-diffsigs -t fpga-image .." yielding "ERROR: No<br>
> sigdata files found matching fpga-image .." so that apparently is a dead end.<br>
><br>
> How can I determine what is causing the system to think that it needs to<br>
> rebuild this package?<br>
<br>
</div>I use this script:<br>
openembedded-core/scripts/sstate-diff-machines.sh<br>
<br>
to create "backup" of sstate signatures and when some next build<br>
unexpectedly doesn't reuse some sstate packages I use the script again<br>
and compare new and old signatures to see why.<br>
<br>
As bonus each build which populates out SSTATE_MIRROR also creates tarball<br>
with these signatures, so I can easily download one tarball and compare<br>
what and why won't be reused from sstate.</blockquote></div><br>You can also directly use bitbake-whatchanged -v <target>, with STAMPS_DIR set to the automated build’s stamps directory w/ sstates included.<br>-- <br>
Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics
</div></div>