Bug 240

Summary: libproxy fails to build on x86_64 host
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Mark Hatle <mark.hatle>
Component: coreAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: Undecided CC: kevin.tian, meta.mr.watcher, meta.watcher, sgw
Version: 0.9   
Target Milestone: ---   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Mark Hatle 2010-08-27 09:16:05 UTC
Recieved the following error when attempting to build a poky-image-sato build, from libproxy:

| /home/mhatle/git/poky/build/tmp/sysroots/x86_64-linux/usr/libexec/i586-poky-linux/gcc/i586-poky-linux/4.5.0/ld: skipping incompatible /home/mhatle/git/poky/build/tmp/sysroots/x86_64-linux/usr/lib/perl/5.8.8/CORE/libperl.so when searching for -lperl
/home/mhatle/git/poky/build/tmp/sysroots/x86_64-linux/usr/libexec/i586-poky-linux/gcc/i586-poky-linux/4.5.0/ld: cannot find -lperl
collect2: ld returned 1 exit status

I traced down the problem to a bad link line:

 /home/mhatle/git/poky/build/tmp/sysroots/x86_64-linux/usr/bin/i586-poky-linux/i586-poky-linux-g++  -fPIC -march=i586  --sysroot=/home/mhatle/git/poky/build/tmp/sysroots/i586-poky-linux  -Wl,-O1 -Wl,--as-needed -shared -Wl,-soname,Libproxy.so -o ../../../perl/blib/arch/auto/Net/Libproxy.so CMakeFiles/PLlibproxy.dir/Libproxy.c.o -L/home/mhatle/git/poky/build/tmp/sysroots/x86_64-linux/usr/lib/perl/5.8.8/CORE -lperl ../../../libproxy/libproxy.so.1.0.0 ../../../libmodman/libmodman.so.0.0.0 -lm -lpthread -ldl -Wl,-rpath,/home/mhatle/git/poky/build/tmp/sysroots/x86_64-linux/usr/lib/perl/5.8.8/CORE:/home/mhatle/git/poky/build/tmp/work/i586-poky-linux/libproxy-0.4.3-r0/libproxy-0.4.3/libproxy:/home/mhatle/git/poky/build/tmp/work/i586-poky-linux/libproxy-0.4.3-r0/libproxy-0.4.3/libmodman:

As you can see from the above it's attempting to link the perl-native files into the target build.

Note:  reverting commit eaf2a94e11b70dacd58f9f0a8d05631383814e16 allows me to continue my build.
Comment 2 Richard Purdie 2010-08-31 09:30:38 UTC
The commit mentioned here fixed this issue