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. -- Tom
signature.asc
Description: PGP signature
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
