http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54820
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bergner at gcc dot gnu.org
--- Comment #14 from Peter Bergner <bergner at gcc dot gnu.org> 2012-10-23
19:09:52 UTC ---
<typed before Ian's comment>
Eric, there seems to be a problem with your toplevel configure change, which
was copied over to the binutils configure script. The problem is that older
GCC's (4.3 is what I'm using to build with), do not return a non-zero value for
-static-libstdc++ even though the option does not exist in 4.3. So I end up
seeing:
configure:4884: checking whether g++ accepts -static-libstdc++ -static-libgcc
configure:4897: g++64 -o conftest -g -O2 -static-libstdc++ -static-libgcc
conftest.cpp >&5
g++: unrecognized option '-static-libstdc++'
configure:4897: $? = 0
configure:4898: result: yes
So configure doesn't correctly catch that -static-libstdc++ doesn't exist and
attempts to use it during the build. It's strange that we do get non-zero
return values for bogus options like -fbogus, etc.
