[yocto] Another sstate rebuild issue, badly need help understanding sstate

[Vuille, Martin (Martin)]

Hi Paul,

> -----Original Message-----
> From: Paul Eggleton [mailto:paul.eggleton at linux.intel.com]
> Sent: November 03, 2014 9:13 AM
> 
> On Monday 03 November 2014 12:53:23 Vuille, Martin wrote:
> > Poky 1.6.1 / daisy
> >
> > I have a variable "REV_TOOLS" defined in distro/conf/somename.conf in
> > a custom distro layer from a git repo.
> >
> > This variable is assigned to SRCREV in a number of recipes (SRCREV =
> > "${REV_TOOLS}") for packages included in my images and SDKs.
> >
> > Pulled an update to the distro layer that changed the value of REV_TOOLS.
> >
> > Rebuilt all my images and SDKs, but bitbake decided there was nothing to
> do.
> >
> > Looking at toaster, all the do_build tasks for the packages affected
> > by this change say "Prebuilt" and the other tasks say "Covered". If I
> > understand correctly, this means sstate didn't detect any change.
> >
> > I am continually running into this problem and am at my wits' end. Why
> > didn't the affected packages get rebuilt? Clearly there is something I
> > don't understand and would appreciate some hint.
> 
> I honestly don't know how to explain this behaviour either, because it
> should not happen this way. BitBake automatically extracts variable
> references within variable values and adds them to the dependencies of
> the variable, so a change to REV_TOOLS should have resulted in the
> signatures changing for the do_fetch tasks for all of the recipes where
> SRCREV contained the reference and thus all of those recipes and the ones
> that depend upon them getting rebuilt.
> 
> Did you use oe-init-build-env or oe-init-build-env-memres to initialise your
> build environment?
> 

oe-init-build-env, prefixed with TEMPLATECONF to point to our custom
distro layer.

MV