On Sun, Mar 03, 2019 at 04:11:36PM -0600, Joshua Watt wrote: > On Sun, Mar 3, 2019 at 3:25 PM Tom Rini <tr...@konsulko.com> wrote: > > > > On Sun, Mar 03, 2019 at 03:21:12PM -0600, Joshua Watt wrote: > > > On Sun, Mar 3, 2019, 2:47 PM Tom Rini <tr...@konsulko.com> wrote: > > > > > > > Hey all, > > > > > > > > As part of the packagegroup-core-base-utils series I noticed that > > > > with rm_work enabled like I usually have, every build was starting over > > > > with rebuilding linux-libc-headers and going down from there. I > > > > finished bisecting this now and it comes down to: > > > > > > Just for reference, are you trying to use hash equivalence? It sounds like > > > not, but I would like to make sure. > > > > I am not. > > > > > Also, it there an AB build that uses rm_work that would have seen this? > > > > OK, so I see I forgot a step that was clear to me, but, uh, not in the > > email. What breaks is for example: > > bitbake core-image-minimal && bitbake core-image-minimal > > That second build, rather than see "nothing to do" (or at least, almost > > nothing to do) says "Oh, I need to build linux-libc-headers from > > scratch" and possibly other stuff too, but that's the first thing I > > notice. > > Ok. I've started a build to test it. Would you mind opening a Bugzilla > for it and assigning it to me? > > For posterity, the poky commit SHA is adc37721a86c
Ah, so "poky" got me thinking this morning. I was just on bitbake v1.40 (since I usually use thud, and that's the version for that). Moving to bitbake master/tip and I don't see the problem anymore. Is it possible to have some logic within OE to check the version of bitbake and throw an error / warning? -- Tom
signature.asc
Description: PGP signature
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
