On Sat, 2018-12-15 at 20:19 -0500, Jason Andryuk wrote:
> As far as I can tell, pysh is working properly - it's just the
> bb_codeparser.dat which is returning the incorrect shellCacheLine
> entry.  It seems like I have an md5 collision between a pyro core2-64
> binutils do_install and core2-32 python-async distutils_do_install in
> the shellCacheLine.  python-async's entry got in first, so that's why
> binutils run.do_install doesn't include autotools_do_install - the
> shellCacheLine `execs` entry doesn't include it.  Or somehow the
> `bb_codeparser.dat` file was corrupted to have an incorrect `execs`
> for the binutils do_install hash.

That is rather worrying. Looking at the known issues with md5, I can
see how this could happen though.

I think this means we need to switch to a better hash mechanism. I've
sent a patch changing this to sha256 on the bitbake list.

We also probably need to change over the code in siggen for the sstate
hashes too but one step at a time...

Cheers,

Richard

-- 
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to