g++ -I../../include -I ../../include -I ../../include /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.2/../../../../x86_64-pc-linux-gnu/bin/ld: /var/tmp/portage/pil /var/tmp/portage/pilot-link-0.11.8-r1/temp/cc9RGgw8.o: could not read symbols: Bad value collect2: ld returned 1 exit status make[3]: *** [java_lib] ?????? 1 make[3]: Leaving directory `/var/tmp/portage/pilot-link-0.11.8-r1/work/pilot-link-0.11.8/bindings/J Reproducible: Always Steps to Reproduce: 1. 2. 3.
I'd remove /var/tmp/portage/* and try again. Attach emerge info after you try again.
This looks like a duplicate of bugs #37048, #57268 and #66087. Luckily someone posted a workaround in bug #63024. It's a pity that it hasn't been fixed yet.
hasn't it been fixed? bug 63024 seems to imply the fix has been committed. is it not working?
I am on 0.11.8. Recompiling with USE=java still gives the same linker error.
0.11.8-r1 compiles on amd64. Would it be possible to make that the stable version?
can you guys check if the latest pilot-link is stable on amd64? thanks
*** This bug has been marked as a duplicate of 77512 ***