[bitbake-devel] [PATCH 1/4] hashserv: Add support for equivalent hash reporting

Richard Purdie richard.purdie at linuxfoundation.org
Wed Dec 4 18:22:25 UTC 2019


On Wed, 2019-12-04 at 10:20 -0800, akuster808 wrote:
> 
> On 12/4/19 3:52 AM, Richard Purdie wrote:
> > The reason for this should be recorded in the commit logs. Imagine
> > you have a target recipe (e.g. meta-extsdk-toolchain) which depends
> > on
> > gdb-cross. sstate in OE-Core allows gdb-cross to have the same hash
> > regardless of whether its built on x86 or arm. The outhash will be
> > different.
> > 
> > We need hashequiv to be able to adapt to the prescence of sstate
> > artefacts
> > for meta-extsdk-toolchain and allow the hashes to re-intersect,
> > rather than
> > trying to force a rebuild of meta-extsdk-toolchain. By this point
> > in the build,
> > it would have already been installed from sstate so the build needs
> > to adapt.
> > 
> > Equivalent hashes should be reported to the server as a taskhash
> > that
> > needs to map to an specific unihash. This patch adds API to the
> > hashserv
> > client/server to allow this.
> > 
> > [Thanks to Joshua Watt for help with this patch]
> 
> This sounds like 1.44 backport worthy?

Yes. Needs a little settling time in master first though.

Cheers,

Richard



More information about the bitbake-devel mailing list