<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Aug 5, 2013 at 5:19 PM, Saul Wold <span dir="ltr"><<a href="mailto:sgw@linux.intel.com" target="_blank">sgw@linux.intel.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="im"></div>
I could not replicate this, can you provide more details about how you setup the failure, was it from a clean sstate?<br></blockquote><div> </div><div> It was with clean sstate, but I can switch between libxml-sax-perl task hashes with a regular clean or setscene of perl. In my existing workspace, I ran<br>
<br></div><div>$ bitbake -c clean perl<br></div><div>$ STAMPS_DIR=perl-stamps bitbake -S libxml-sax-perl<br></div><div>$ bitbake perl # From sstate<br></div><div>$ STAMPS_DIR=perl-stamps bitbake -S libxml-sax-perl<br><br>
and got the error for several do_package tasks<br><div style="margin-left:40px">ERROR: Bitbake's cached basehash does not match the one we just generated (/.../oe-core/meta/recipes-extended/perl/libxml-sax-base-perl_1.08.bb.do_package)!<br>
</div><br></div><div>I think you have to trigger a re-parse (which -S seems to do) since the perl files being in the sysroot wouldn't invalidate the cache.<br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Are you working with master or 1.4 or something else?<br></blockquote><div> </div><div>I first noticed it on 1.4 and reproduced it on master, which was 09deeef20ee5a0c12ad4fd89cace6e0fb832d5b1 at the time.<br><br></div><div>
Thanks,<br>Tyler<br></div><br></div></div></div>