On Mon, 2018-05-28 at 20:55 +0200, Jens Rehsack wrote:
> The modern the time, the improvements in ExtUtils::MakeMaker.
>
> Nowadays, .packlist and perllocal.pod aren't touched anymore when appropriate
> flags set during configure stage. Controlling the flags globally avoids
> dual-life recipes need share patching.
>
> Further: remove prepending ${PERL_ARCHLIB} in PERL5LIB - it's wrong (search
> order is site_lib, vendor_lib, core) - and ${PERL_ARCHLIB} contains core
> libpath only ...
>
> Signed-off-by: Jens Rehsack <s...@netbsd.org>
> ---
> meta/classes/cpan.bbclass | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
I put this in for testing but I see:
$ SDKMACHINE="i686" bitbake nativesdk-libxml-parser-perl
[...]
ERROR: nativesdk-libxml-parser-perl-2.44-r0 do_package:
nativesdk-libxml-parser-perl: chrpath command failed with exit code 7:
b'/media/build1/poky/build/tmp-222/work/i686-nativesdk-pokysdk-linux/nativesdk-libxml-parser-perl/2.44-r0/package/opt/poky/2.5+snapshot/sysroots/i686-pokysdk-linux/usr/lib/perl/vendor_perl/5.24.1/auto/XML/Parser/Expat/Expat.so:
RPATH=/media/build1/poky/build/tmp-222/work/i686-nativesdk-pokysdk-linux/nativesdk-libxml-parser-perl/2.44-r0/recipe-sysroot/opt/poky/2.5+snapshot/sysroots/i686-pokysdk-linux/usr/lib\n'b"new
rpath
'$ORIGIN/../../../../../../../../../../../../../../media/build1/poky/build/tmp-222/work/i686-nativesdk-pokysdk-linux/nativesdk-libxml-parser-perl/2.44-r0/recipe-sysroot/opt/poky/2.5+snapshot/sysroots/i686-pokysdk-linux/usr/lib'
too large; maximum length 176\n"
ERROR: nativesdk-libxml-parser-perl-2.44-r0 do_package: Function failed:
perform_packagecopy
ERROR: Logfile of failure stored in:
/media/build1/poky/build/tmp-222/work/i686-nativesdk-pokysdk-linux/nativesdk-libxml-parser-perl/2.44-r0/temp/log.do_package.23783
ERROR: Task
(virtual:nativesdk:/media/build1/poky/meta/recipes-devtools/perl/libxml-parser-perl_2.44.bb:do_package)
failed with exit code '1'
which seems to reproduce fairly readily both locally and on the
autobuilders. Reverting this patch resolves it.
Cheers,
Richard
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
