relocation x86_64 errors and gcc-4.3

gjohnson5 tonyjohn5 at yahoo.com
Fri May 30 16:05:44 UTC 2008


I've been reading that this is a common problem gcc-4.3

/usr/bin/ld: .libs/bytebuffer.o: relocation R_X86_64_32 against `a local
symbol' can not be used when making a shared object; recompile with -fPIC
.libs/bytebuffer.o: could not read symbols: Bad value
collect2: ld returned 1 exit status
make[4]: *** [libakode.la] Error 1
make[4]: Leaving directory `/usr/local/rpmbuild/BUILD/akode-2.0.2/akode/lib'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/usr/local/rpmbuild/BUILD/akode-2.0.2/akode/lib'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/local/rpmbuild/BUILD/akode-2.0.2/akode'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/rpmbuild/BUILD/akode-2.0.2'
make: *** [all] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.35312 (%build)

I'm just wondering if there are some flags I can pass the compiler instead
of having to build the whole SRPM with -fPIC?  It's definitly an easy fix,
but compiling executables fPIC doesn't seem optimal performance wise
-- 
View this message in context: http://www.nabble.com/relocation-x86_64-errors-and-gcc-4.3-tp17562637p17562637.html
Sent from the Fedora Test List mailing list archive at Nabble.com.




More information about the test mailing list