Summary: | media-libs/openal-1.15.1-r2 - ld: CMakeFiles/openal.dir/OpenAL32/alAuxEffectSlot.o: relocation R_X86_64_32S against `.text' can not be used when making a shared object; recompile with -fPIC | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | account-removed <account-removed-ee4b8c405f7fc42156f3a4085b4bfa03> |
Component: | [OLD] Library | Assignee: | Gentoo Sound Team <sound> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kde, mgorny |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | openal-1.15.1-r2-logs.tar.xz |
Description
account-removed
2014-02-02 03:04:48 UTC
> -- The C compiler identification is unknown
It seems something is wrong either with gcc or with cmake.
Search for the log of that test.
So, do you have any special setup... like crossdev? clang? custom cmake installation? Anything that might be confusing gcc-config and the build environment? Have you tried the default, selecting compiler with gcc-config again, env-update, source /etc/profile, possible re-emerge of cmake? CCing kde as cmake maintainer. How does the user get the info from Comment #1? No special setup, though ~amd64 in ACCEPT_KEYWORDS. gcc-config reselected, libtool and cmake re-emerged, same result. I'm starting to think this might be an upstream problem (removed -fPIC?) Updated log (about the same) https://gist.github.com/8768831 emerges fine on multiple ~amd64 systems here. both with and without ABI_X86="32" almost 100% sure it's something broken in your toolchain. have you made any radical changes in your toolchain like changed CHOST in make.conf recently? try to be a bit more proactive with the bug since you are the only one who can reproduce it ;) 'emerge -e system' if in doubt why do you have so much free space in your CFLAGS and CXXFLAGS? CFLAGS=" -march=native -O2 -pipe " CXXFLAGS=" -march=native -O2 -pipe " this is just a lame'ish guess, but try deleting the extra spaces, maybe it's confusing the cmake. i don't know why it would, but it's the only thing standing out from the provided files, imho I had free space in there because I defined CFLAGS as such: CFLAGS=" -march=native -pipe -O2 " since I used to add -sse4_2 (and a couple others) on another line before. However, changing CFLAGS line to CFLAGS="-march=native -pipe -O2" and emerging openal fixed the issue (CMake recognized GCC as 4.8.2 and compiled sucessfully). Maybe add into the gcc-optimization wiki page "adding any form of whitespace in USE flags is fine, but in CFLAGS it might break certain packages"? wow :) [Redacting comment to remove PII] (In reply to Michael Palimaka (kensington) from comment #8) > Interesting, this is not the first whitespace-induced compile bug I've seen > before. > > (In reply to [redacted] from comment #6) > > Maybe add into the gcc-optimization wiki page "adding any form of whitespace > > in USE flags is fine, but in CFLAGS it might break certain packages"? > It's a wiki, go for it! |