/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.1/../../../../x86_64-pc-linux-gnu/bin/ld: /var/tmp/portage/pilot-link-0.11.8/temp/ccaon9Fw.o: relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC /var/tmp/portage/pilot-link-0.11.8/temp/ccaon9Fw.o: could not read symbols: Bad value collect2: ld returned 1 exit status make[3]: *** [java_lib] Error 1 make[3]: Leaving directory `/var/tmp/portage/pilot-link-0.11.8/work/pilot-link-0.11.8/bindings/Java' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/pilot-link-0.11.8/work/pilot-link-0.11.8/bindings' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/pilot-link-0.11.8/work/pilot-link-0.11.8' make: *** [all-recursive-am] Error 2 !!! ERROR: app-pda/pilot-link-0.11.8 failed. !!! Function src_compile, Line 57, Exitcode 2 !!! (no error message) Despite the fact that the output instructs me to use -fPIC and recompile, using 'CFLAGS="-fPIC" emerge -v pilot-link' yields the same results (including the note to use -fPIC) Reproducible: Always Steps to Reproduce: 1.emerge -v pilot-link 2. 3. Actual Results: see relevant section of output in "details" Expected Results: successfully install pilot-link 2.6.7-gentoo-r10 gcc 3.4.1 CFLAGS="-O3 -march=k8 -mtune=k8 -fomit-frame-pointer -fprefetch-loop-arrays -pipe -maccumulate-outgoing-args" USE="multilib alsa avi crypt cups fbcon gif gtk java jikes jpeg maildir mozilla mpeg oggvorbis opengl pda pdflib perl png quicktime samba sdl slp svga tcltk tiff truetype usb aim yahoo X amd64"
Same error here. Has something to do with USE'ing java. Some java so may be 32 bit. USE'ing -java allowed the compile to succeed. I'm using blackdown-jdk-1.4.2_rc1. Running qpkg -nc -l blackdown-jdk-1.4.2_rc1-r1 | grep '\.so' | awk '{ print $1 }' | xargs file | grep -v 64 did yield any suspects. :( I haven't managed to sucessfully use pilot-link yet though.
Argh, that's "did _not_ yield any suspects."
not quite sure how to help with amd64. any tips guys?
Just wanted to chime in: I am having the same problem. 2004.2~amd64 on an eMachines laptop USE="-java" does allow me to compile pilot-link 0.11.8, which in turn allows me to compile gaim, and "novell" ximian evolution. :) Thanks for the tip!
'm getting closer to the problem but need help how to solve it... First I changed from blackdown to sun java VM. This gives me a different error when emerging pilot-link: a unmappable character for encoding ASCII. I checked the file (test.java) and indeed it prints some unrecognized characters by java So reading for hours several forums, I could see that my locale were set by the default values: POSIX and LANG was empty. I export new values for LANG (trying severals)..and now I get the same error as previously.. make[3]: Entering directory `/var/tmp/portage/pilot-link-0.11.8/work/pilot-link-0.11.8/bindings/Java' /opt/sun-jdk-1.5.0_beta2/bin/javac -d . ./org/gnu/pilotlink/AddressRecord.java ./org/gnu/pilotlink/AppInfo.java ./org/gnu/pilotlink/DatebookRecord.java ./org/gnu/pilotlink/MemoRecord.java ./org/gnu/pilotlink/PilotLink.java ./org/gnu/pilotlink/RawAppInfo.java ./org/gnu/pilotlink/RawRecord.java ./org/gnu/pilotlink/Record.java ./org/gnu/pilotlink/SysInfo.java./org/gnu/pilotlink/User.java ./test.java Note: ./test.java uses unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. g++ -I../../include -I ../../include -I ../../include -I /opt/sun-jdk-1.5.0_beta2/include -I /opt/sun-jdk-1.5.0_beta2/include/linux -L ../../libpisock/.libs -lpisock -shared -o libjpisock.so ./libjpisock.c /usr/lib/gcc-lib/x86_64-pc-linux-gnu/3.3.3/../../../../x86_64-pc-linux-gnu/bin/ld: /var/tmp/portage/pilot-link-0.11.8/temp/ccglpa6h.o: relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC /var/tmp/portage/pilot-link-0.11.8/temp/ccglpa6h.o: could not read symbols: Bad value collect2: ld returned 1 exit status make[3]: *** [java_lib] Error 1 make[3]: Leaving directory `/var/tmp/portage/pilot-link-0.11.8/work/pilot-link-0.11.8/bindings/Java' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/pilot-link-0.11.8/work/pilot-link-0.11.8/bindings' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/pilot-link-0.11.8/work/pilot-link-0.11.8' make: *** [all-recursive-am] Error 2 !!! ERROR: app-pda/pilot-link-0.11.8 failed. !!! Function src_compile, Line 57, Exitcode 2 !!! (no error message) I really think that the problem is that it can't map those strange characters in the test.java because of java ...
I've got the same symptoms. Maybe the solution is allready described in bug #63024 (and the fix hasn't propagated).
Yes, the patch in http://bugs.gentoo.org/show_bug.cgi?id=63024 is correct. The reason the initial description didn't work with the "CFLAGS=-fPIC", was that it probably should have been "CXXFLAGS=-fPIC".
Bug was opened Jul 17th, A fix was posted on Sept 9th with bug #63024 We're living near the end of November now... MOETEN WE WACHTEN TOT WE EEN ONS WEGEN? (sorry for switching to Dutch.)
fixed. btw: speaking dutch doesn't help much. if you want that we understand you, please speak english.
FYI: I am still having this excat problem. It appears that the Portage ebuilds are still broken for this package. I have checked the other bug (referenced below) and it shows that this has been fixed -- and indicates that the fix is in Portage. However, I still get the exact same error. Should this be reopened???
pilot-link-0.11.8-r1 somehow got installed on my machine; I forgot exactly how.
This bug is *not* fixed, the stable amd64 version of pilot-link fails to compile with the error given at the top of this bug. The -r1 ebuild does compile, can we get that keyworded?
we can't mark it stable before maintainer did so.. pda herd: do you think we can mark this package stable? there are no open bugs beside a ebuild request for 0.12.0_pre2 and a bug for 0.9.6
Hello, If you will not mark the -r1 ebuild stable, might I suggest you mask this one, as it doesn't work? Throw "pda" in the profile use.mask and nobody will trigger it. Leaving it in this state is silly, I'll leave it at that.
