https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #21 from Thomas Koenig <tkoenig at gcc dot gnu.org> --- (In reply to Jonathan Wakely from comment #20) > For libstdc++ the default (without --enable-werror or --disable-werror) is > to add $(WERROR_FLAG) to WARN_FLAGS. WERROR_FLAG is empty by default, but > contains -Werror for maintainer mode. > > So if you use --enable-maintainer-mode --disable-werror then -Werror won't > be added to the libstdc++ flags. > > Is that an acceptable workaround for now? No code changes required. > > When I'm back from holiday I'll look into the libstdc++ warning flags and > determine why -Wabi was added and how to make it actually work as intended. --disable-werror does allow bootstrap to complete for me. I'll post a message to the gcc, gcc-patches and fortran mailing list so people don't fall into the same trap that Steve and I did.
