[Bug go/71697] go link error

2016-06-29 Thread rootkit85 at yahoo dot it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71697 --- Comment #5 from Matteo Croce --- $ x86_64-linux-gnu-gcc -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -Wov

[Bug go/71697] go link error

2016-06-29 Thread rootkit85 at yahoo dot it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71697 --- Comment #4 from Matteo Croce --- /home/matteo/src/openwrt/build_dir/toolchain-i386_pentium4_gcc-5.3.0_glibc-2.22/gcc-5.3.0-final/./gcc/collect-ld -plugin /home/matteo/src/openwrt/build_dir/toolchain-i386_pentium4_gcc-5.3.0_glibc-2.22/gcc-5.3.

[Bug go/71697] go link error

2016-06-29 Thread ian at airs dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71697 --- Comment #3 from Ian Lance Taylor --- The running the failing command yourself with the -v option and see which options are being passed to the linker.

[Bug go/71697] go link error

2016-06-29 Thread rootkit85 at yahoo dot it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71697 --- Comment #2 from Matteo Croce --- I run Ubuntu 16.04, how can I check if --no-add-needed is default?

[Bug go/71697] go link error

2016-06-29 Thread ian at airs dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71697 --- Comment #1 from Ian Lance Taylor --- Note that as far as I can tell that error is only emitted by the GNU linker when the --no-add-needed option is passed to the linker. Is something on your system adding that option or making it the default