https://sourceware.org/bugzilla/show_bug.cgi?id=33162
--- Comment #10 from Rainer Orth <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #8 from Nick Alcock <nick.alcock at oracle dot com> --- > Yes -- but if GCC wasn't built with GNU ld, collect2 appears to run the > non-GNU > ld anyway, ignoring(?) -B: Such a gcc is almost guaranteed to fail when used with ld: gcc/configure.ac detects the linker type and uses different options depending on the configure time linker. Same for as, btw. For the record, here's how I've configure gcc to be used for binutils testing: * First build some version of binutils, install into $buprefix. I use configure --build=<build triple> --prefix=<buprefix> * Then, build gcc with those binutils first in PATH: configure --build=<build triple> --prefix=<buprefix> --with-gnu-as --with-gnu-ld --enable-languages=c,c++,lto Be careful to use the proper value for <build triple>: config.guess makes a total mess with configure triple detection on Solaris, so much so that I've given up on getting fixes in. I use sparc-sun-solaris2.11 32-bit Solaris/SPARC sparcv9-sun-solaris2.11 64-bit Solaris/SPARC i386-pc-solaris2.11 32-bit Solaris/x86 amd64-pc-solaris2.11 32-bit Solaris/x86 Also, *don't* specify --with=as=/path/to/as or --with-ld=/path/to/ld, otherwise you won't be able to override those PATHs at runtime. I use four different builds of GCC for full testing; I had problems getting the proper -m32/-m64 options all the way through the binutils build and test framework. -- You are receiving this mail because: You are on the CC list for the bug.
