Summary: | dev-util/kdesvn-0.12 fails to emerge on AMD64 with gcc-4.2.0 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Thomas Veith <th_veith> |
Component: | New packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | 1i5t5.duncan, esigra, george |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
buildlog
emerge --info |
Description
Thomas Veith
2007-05-25 12:42:08 UTC
Created attachment 120278 [details]
buildlog
OOPS.. MY FAULT! When compiling with gcc-4.1.2 it all works! So its a problem related to gcc-4.2.0! Sorry! According to an announcement on gentoo-dev, gcc-4.2.0 is about to go ~arch including ~amd64. Thus, this bug should be reopened and fixed for gcc-4.2.0. FWIW, on ~amd64 I'm failing with gcc-4.2.0 but succeeding with 4.1.2 as well. I hadn't filed a bug however as 4.2 was masked and I couldn't provide a patch. Note that according to bug #184087 there's a new version out, kdesvn-0.12.1, that fixes a linker problem on Mac OSX. It's possible that fix works for the linker problem here too. I expect to test that theory shortly and report my results. (The sources location changed too, so it's not just version bumping the ebuild.) Duncan The kdesvn-0.12.1 from upstream, using the updated Gentoo 0.12.0 ebuild, does /not/ fix the gcc-4.2.0 linking problem as I had hoped. Please reopen this bug and make bug #162167 (the gcc-4.2.0 tracker bug) depend on it. I'll attach my emerge --info output shortly. Duncan Created attachment 124050 [details]
emerge --info
Here's my emerge --info. Note that with gcc-4.1.2, kdesvn-0.12 emerges fine. With 4.2.0, it doesn't. I tried generic C(XX)FLAGS="-march=k8 -O2 -pipe" and even -O instead of -O2, same issue. I blew away the confcache in case that was causing the problem. It wasn't. As stated above, I just tried kdesvn-0.12.1 too, hoping it was fixed upstream. It wasn't. I don't really know what else to try, so I've just been using the gcc-4.1.2 compiled version.
I DO note that it seems to be attempting to link against the static *.a, which AFAIK won't be -fPIC, rather than the dynamic *.so, which should be. Why, I'm not sure, but obviously, gcc-4.2 is screwing up something somewhere.
Duncan
gcc-4.2 bugs need to be tracked Try using binutils-2.17.50.0.17 (in package.mask). kdesvn-0.12.1 compiled for me with gcc-4.2.0 and the masked binutils. I had several packages fail (I don't remember which ones, sorry) with following error message: relocation R_X86_64_PC32 against `xxx' can not be used when making a shared object; recompile with -fPIC until I upgraded binutils when I was trying gcc-4.2 snapshots. Upgrading binutils fixed all of those errors except for one- enigmail. Fortunately, I don't use enigmail and I added the following line: mail-client/mozilla-thunderbird -crypt to my package.use and forgot about it until now. I forgot to mention that I only encountered the relocation errors on my amd64 machine- not on my x86 machine. Maybe gcc-4.2 requires a newer binutils on amd64? This was also discussed on the forums. See http://forums.gentoo.org/viewtopic-t-452816-postdays-0-postorder-asc-start-250.html (In reply to comment #7) > Try using binutils-2.17.50.0.17 (in package.mask). > kdesvn-0.12.1 compiled for me with gcc-4.2.0 and the masked binutils. Just confirming, binutils-2.17.15.0.17 did it (with kdesvn-0.12.1, see comment #3) for me here. It's up and running, compiled with gcc-4.2.0, now. =8^) Thanks, Neil! Looks like there may need to be an amd64 and gcc-4.2.0 conditional dependency on a newer binutils. Duncan *** This bug has been marked as a duplicate of bug 186089 *** |