1132 2011-06-01 00:54:16 +0000 libxml-simple-perl do_configure Failed if being built after libxml-sax-perl 2011-06-26 18:50:41 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core unspecified x86 Multiple RESOLVED FIXED Medium normal 1.1 M2 1 dexuan.cui kai.kang jiajun.xu meta.mr.watcher meta.watcher sgw --- --- --- oldest_to_newest 14110 0 dexuan.cui 2011-06-01 00:54:16 +0000 I happened to find such a bug that was confirmed by Jiajun: Running "bitbake libxml-sax-perl libxml-sax-perl-native -c populate_sysroot; bitbake libxml-simple-perl -c populate_sysroot' can reproduce the issue. NOTE: Running task 270 of 273 (ID: 5, /home/jxu49/osel/poky/meta/recipes-devtools/perl/libxml-simple-perl_2.18.bb, do_configure) NOTE: package libxml-simple-perl-2.18-r1: task do_configure: Started ERROR: '/home/jxu49/osel/poky/meta/recipes-devtools/perl/libxml-simple-perl_2.18.bb' failed ERROR: Logfile of failure stored in: /home/jxu49/osel/poky/build/tmp/work/i586-poky-linux/libxml-simple-perl-2.18-r1/temp/log.do_configure.5541 Log data follows: | could not find ParserDetails.ini in /home/jxu49/osel/poky/build/tmp/sysroots/i686-linux/usr/lib/perl/5.12.3/XML/SAX | Errno architecture (i686-linux-thread-multi-2.6.32-21-generic-pae) does not match executable architecture (i586-linux-2.6.37-rc5-yocto-standard+) at /home/jxu49/osel/poky/build/tmp/sysroots/i686-linux/usr/lib/perl/5.12.3/Errno.pm line 11. | Compilation failed in require at /home/jxu49/osel/poky/build/tmp/sysroots/i686-linux/usr/lib/perl/5.12.3/File/Temp.pm line 148. | BEGIN failed--compilation aborted at /home/jxu49/osel/poky/build/tmp/sysroots/i686-linux/usr/lib/perl/5.12.3/File/Temp.pm line 148. | Compilation failed in require at /home/jxu49/osel/poky/build/tmp/sysroots/i686-linux/usr/lib/perl/5.12.3/XML/SAX/PurePerl/Reader/URI.pm line 8. | BEGIN failed--compilation aborted at /home/jxu49/osel/poky/build/tmp/sysroots/i686-linux/usr/lib/perl/5.12.3/XML/SAX/PurePerl/Reader/URI.pm line 8. | Compilation failed in require at /home/jxu49/osel/poky/build/tmp/sysroots/i686-linux/usr/lib/perl/5.12.3/XML/SAX/PurePerl/Reader.pm line 6. | BEGIN failed--compilation aborted at /home/jxu49/osel/poky/build/tmp/sysroots/i686-linux/usr/lib/perl/5.12.3/XML/SAX/PurePerl/Reader.pm line 6. | Compilation failed in require at /home/jxu49/osel/poky/build/tmp/sysroots/i686-linux/usr/lib/perl/5.12.3/XML/SAX/PurePerl.pm line 11. | BEGIN failed--compilation aborted at /home/jxu49/osel/poky/build/tmp/sysroots/i686-linux/usr/lib/perl/5.12.3/XML/SAX/PurePerl.pm line 11. | Compilation failed in require at (eval 16) line 1. | Checking installed modules ... | ERROR: Function 'do_configure' failed (see /home/jxu49/osel/poky/build/tmp/work/i586-poky-linux/libxml-simple-perl-2.18-r1/temp/log.do_configure.5541 for further information) | ERROR: Function 'do_configure' failed (see /home/jxu49/osel/poky/build/tmp/work/i586-poky-linux/libxml-simple-perl-2.18-r1/temp/log.do_configure.5541 for further information) NOTE: package libxml-simple-perl-2.18-r1: task do_configure: Failed ERROR: Task 5 (/home/jxu49/osel/poky/meta/recipes-devtools/perl/libxml-simple-perl_2.18.bb, do_configure) failed with exit code '1' Kai added the recipe libxml-sax-perl recently, so let's assign this bug to him at present. :-) The bug reveals some kind of dependency we need to address. BTW, Jiajun reproduce the bug using commit 4ff7af11ef69849ef9c16f585eae58ac920b222b Date: Fri May 27 14:11:20 2011 -0700 machine confs: Add xserver-kdrive as PREFERRED_PROVIDER But I believe the latest poky master has the same issue. 14220 1 kai.kang 2011-06-08 03:05:26 +0000 libxml-simple-perl using ${STAGING_LIBDIR_NATIVE} as its module include path, and that cause the failure. 14417 2 sgw 2011-06-24 15:03:10 +0000 Can you confirm that this is still a problem? There was a fix pending, and I wonder if the perlnative work fixes this issue more correctly. 14419 3 kai.kang 2011-06-26 18:50:41 +0000 (In reply to comment #2) > Can you confirm that this is still a problem? There was a fix pending, and I > wonder if the perlnative work fixes this issue more correctly. Yes, it could be built now and I guess Dexuan's patch (a74e428e34d80bdb1bff33ddd8c97709bb08b0ba) works.