https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88749
--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Romain Geissler from comment #8) > So with these explanations, do you think the patch you proposed should land > in trunk (it worked for me in that specific bootstrap configuration). Yes the patch is correct regardless and I'll commit it shortly. The explanation also makes sense of the results too. (In reply to Romain Geissler from comment #9) > This may be some naive question, but if we are currently trying to build a > libstdc++, shouldn't we assume there is no pre-existing libstdc++ and run > the different checks in the configure script either with the C compiler (if > indeed we never use C++) No, because testing whether a C compiler can use those functions tells us nothing about whether G++ will be able to use them. C libraries expose different declarations to C and C++ programs. > or with CXXFLAGS like -nodefaultlib ? That would also make libc unavailable.
