[Yocto-builds] buildbot failure in The Yocto Autobuilder on nightly-x86-64-lsb

[Richard Purdie]

On Tue, 2013-09-17 at 19:26 -0700, Saul Wold wrote:
> 
> I am looking into this one, somehow we are getting an LD_RUN_PATH being 
> set by the perl configuration process in the Makefile, it only seems to 
> happen for this library on AB02!
> Yocto-builds at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto-builds

This failure was a bit crazy to track down. There was a problem with the
checksums from bitbake which resulted in tasks re-running between
machine switches for the same package_arch. In this case:

perl:do_populate_sysroot ran for MACHINE=qemux86-64
then
perl:do_populate_sysroot ran for MACHINE=genericx86-64

on the same workdir. Unfortunately the paths in the sstate tarball for
the second run were messed up, half referenced qemux86-64 and half
genericx86-64. Specifically, these were correct and listed in the sstate
fixmelist:

sysroot-destdir/usr/lib/perl/config.sh
sysroot-destdir/usr/lib/perl/5.14.3/CORE/config.h
sysroot-destdir/usr/lib/perl/5.14.3/Config.pm
sysroot-destdir/usr/lib/perl/5.14.3/Config_heavy.pl

whilst these had the wrong paths in:

sysroot-destdir/usr/lib/perl/5.14.3/CORE/perl.h
sysroot-destdir/usr/lib/perl/5.14.3/CORE/pp.h
sysroot-destdir/usr/lib/perl/5.14.3/ExtUtils/Liblist/Kid.pm
sysroot-destdir/usr/lib/perl/5.14.3/FileCache.pm
sysroot-destdir/usr/lib/perl/5.14.3/cacheout.pl

How does this affect libxml-parser-perl? MakeMaker uses Kid.pm when
writing the Makefile from Makefile.PL. If the wrong path is in there,
rpaths get added as it doesn't recognise it as a system path.

The underlying trigger should be fixed with the fix to bitbake's
checksum/variable parsing code. We need to think carefully about how the
incorrect paths managed to propagate though and be sure this can't
happen again.

Cheers,

Richard