| Summary: | net-im/pidgin-2.5.9 fails to compile | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | ~S <prince.of.bb+gentoobugzilla> |
| Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | VERIFIED INVALID | ||
| Severity: | normal | CC: | prince.of.bb+gentoobugzilla |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build log for pidgin 2.5.9
build log for media-libs/lcms build environment of my system |
||
|
Description
~S
2009-08-22 09:44:15 UTC
please attach the full build.log. Reopen when that is provided, thanks Created attachment 202012 [details]
build log for pidgin 2.5.9
Ebuild log for pidgin 2.5.9 attached
i can see 2.6.1 pidgin in portage (~amd64), i am compiling rite now
lets see if its resolved
~S
Update - pidgin 2.6.1 compiled and installed ! so you might want to leave this bug as resolved with resolution to update/upgrade to pidgin 2.6.1 if someone is interested in debugging 2.5.9 i can try recompiling it again for the sake of more info (build log already attached) ~S """ .libs/assert.o: relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC .libs/assert.o: could not read symbols: Bad value """ This means that the file assert.o was not compiled with the -fPIC flag, which it should. When you fix this kind of error, make sure only objects that are used in shared libraries are compiled with -fPIC. --- from http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=3 go to point 3.f. Case 3: Lack of `-fPIC' flag in the software to be built. now I am confused as to which package this bug belongs to python2.6? as the library in question is libpython2.6.a(listobject.o) or does it belong to pidgin? if its the former case then kindly reassign this bug to python devs if latter then pidgin herd should tweak their ebuilds to compile properly pardon me if I am wrong, I am just another bug reporter and I didn't understand the static/non-static .a/.so gibberish :P ~S As mentioned before an upgrade to 2.6 solved the problem, but I searched again for this error as I found similar problems with another package (media-libs/lcms-1.18-r1) if you guys can confirm that this indeed is python problem, then I can file bug to python guys :) here is the info on similar bug (compile fail) on media-libs/lcms-1.18-r1 """ x86_64-pc-linux-gnu-g++ -shared -nostdlib /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.1/../../../../lib64/crti.o /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.1/crtbeginS.o .libs/_lcms_la-lcms_wrap.o -Wl,--rpath -Wl,/var/tmp/portage/media-libs/lcms-1.18-r1/work/lcms-1.18/src/.libs -L/usr/lib64/python2.6/config ../src/.libs/liblcms.so -lpython2.6 -L/usr/lib/gcc/x86_64-pc-linux-gnu/4.4.1 -L/usr/lib/gcc/x86_64-pc-linux-gnu/4.4.1/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -L/usr/lib/gcc/x86_64-pc-linux-gnu/4.4.1/../../../../x86_64-pc-linux-gnu/lib -L/usr/lib/gcc/x86_64-pc-linux-gnu/4.4.1/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.1/crtendS.o /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.1/../../../../lib64/crtn.o -march=nocona -Wl,-O1 -Wl,-soname -Wl,_lcms.so -o .libs/_lcms.so /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.1/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib64/python2.6/config/libpython2.6.a(abstract.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC /usr/lib64/python2.6/config/libpython2.6.a: could not read symbols: Bad value collect2: ld returned 1 exit status make[1]: *** [_lcms.la] Error 1 make[1]: Leaving directory `/var/tmp/portage/media-libs/lcms-1.18-r1/work/lcms-1.18/python' make: *** [all-recursive] Error 1 * * ERROR: media-libs/lcms-1.18-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2569: Called _eapi2_src_compile * ebuild.sh, line 634: Called die * The specific snippet of code: * emake || die "emake failed" * The die message: * emake failed """ attaching complete build.log for media-libs/lcms-1.18-r1 and also attaching build.environment Again, redirect me(this bug) to python people if you think these two bugs are related and are caused by python ~S Created attachment 202337 [details]
build log for media-libs/lcms
build log for media-libs/lcms
one can see the error is with python libraries (.o file)
~S
Created attachment 202338 [details]
build environment of my system
build environment of my system (from media-libs/lcms)
~S
hmmm, looks like i have to file another bug for media-libs/lcms i was really hoping that this was python related bug and fixing a symlink would not be that hard Alas! one more bug to crush :( if anyone knows more about the -fPIC problem, please have a look at the build logs and environment ~S It is strange that the builds are trying to use a static version of libpython -- do you have libpython2.6.so on your system? (In reply to comment #9) > It is strange that the builds are trying to use a static version of libpython > -- do you have libpython2.6.so on your system? > yes I do have ~ $ ls -la /usr/lib64/libpython2.6.so lrwxrwxrwx 1 root root 19 2009-08-25 23:29 /usr/lib64/libpython2.6.so -> libpython2.6.so.1.0 also, strange thing is that I have two versions of python, phyton 2.6 and 3.0 i emerged python manually once (i forgot to add --oneshot) so its in my world file list ~S I've seen this problem before when a someone compiled python by hand based on stupid post in forums.gentoo.org, in his case deleting the /usr/lib64/python2.6/config/libpython2.6.a file and re-emerging python helped. Because you shouldn't have /usr/lib64/python2.6/config/libpython2.6.a anyway, because the file is installed as /usr/lib64/libpython2.6.a from the ebuild. How did you end up having the file there is beyond me... ssuominen@unique ~ $ ls /usr/lib64/python2.6/config/libpython2.6.a ls: cannot access /usr/lib64/python2.6/config/libpython2.6.a: No such file or directory ssuominen@unique ~ $ qfile -v libpython2.6.a dev-lang/python-2.6.2-r1 (/usr/lib64/libpython2.6.a) ssuominen@unique ~ $ ohh god , thank you so much !!! yes I did installed python manually [and yes, call me a moron, but I did emerge -C python :( ] and then emerged python from portage (and completely forgot about the manual install) thanks a lot I was unable to compile loads of other packages and was even thinking of reinstalling gentoo !! *phew* you saved me from a lot of trouble :) thanks again this bug is closed! ~S |
