bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/17219] ld/mips: can no longer build libstdc++ (gcc 4.8/4.9)


From: manuel.lauss at gmail dot com
Subject: [Bug ld/17219] ld/mips: can no longer build libstdc++ (gcc 4.8/4.9)
Date: Wed, 20 Aug 2014 20:07:09 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=17219

--- Comment #2 from Manuel Lauss <manuel.lauss at gmail dot com> ---
native builds are also affected: for example gcc-4.9.1 built natively fails
with
libtool: link: mipsel-softfloat-linux-gnu-gcc -shared  .libs/lto-plugin.o   
-Wl,--as-needed  -static-libgcc -Wl,-O1 ../libiberty/pic/libiberty.a  
-Wl,-soname -Wl,liblto_plugin.so.0 -o .libs/liblto_plugin.so.0.0.0
/usr/lib/gcc/mipsel-softfloat-linux-gnu/4.9.1/../../../../mipsel-softfloat-linux-gnu/bin/ld:
error: .libs/lto-plugin.o: relocation 4 against `a local symbol' can not be
used when making a shared object; recompile with -fPIC
/usr/lib/gcc/mipsel-softfloat-linux-gnu/4.9.1/../../../../mipsel-softfloat-linux-gnu/bin/ld:
error: .libs/lto-plugin.o: relocation 5 against `a local symbol' can not be
used when making a shared object; recompile with -fPIC
/usr/lib/gcc/mipsel-softfloat-linux-gnu/4.9.1/../../../../mipsel-softfloat-linux-gnu/bin/ld:
error: .libs/lto-plugin.o: relocation 5 against `a local symbol' can not be
used when making a shared object; recompile with -fPIC
/usr/lib/gcc/mipsel-softfloat-linux-gnu/4.9.1/../../../../mipsel-softfloat-linux-gnu/bin/ld:
error: .libs/lto-plugin.o: relocation 4 against `a local symbol' can not be
used when making a shared object; recompile with -fPIC
/usr/lib/gcc/mipsel-softfloat-linux-gnu/4.9.1/../../../../mipsel-softfloat-linux-gnu/bin/ld:
error: .libs/lto-plugin.o: relocation 5 against `stderr' can not be used when
making a shared object; recompile with -fPIC
/usr/lib/gcc/mipsel-softfloat-linux-gnu/4.9.1/../../../../mipsel-softfloat-linux-gnu/bin/ld:
error: non-dynamic relocations refer to dynamic symbol stderr

and so on.  Again, reverting the above mentioned commit fixes everything.

-- 
You are receiving this mail because:
You are on the CC list for the bug.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]