https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #18 from Steve Kargl <sgk at troutmask dot apl.washington.edu> --- On Tue, Jul 10, 2018 at 10:11:54PM +0000, redi at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450 > > --- Comment #17 from Jonathan Wakely <redi at gcc dot gnu.org> --- > The problem is that gfortran development is dependent > on a gcc-wide build mode which affects more than just > gfortran. There's no good reason that libstdc++ should > be a blocker for you (for the record, the -Wabi flag > has been present for years, and the -Werror consequence > of maintainer mode has been there for years too, what > changed was not in libstdc++ but g++). https://gcc.gnu.org/install/configure.html --enable-maintainer-mode The build rules that regenerate the Autoconf and Automake output files as well as the GCC master message catalog gcc.pot are normally disabled. This is because it can only be rebuilt if the complete source tree is present. If you have changed the sources and want to rebuild the catalog, configuring with --enable-maintainer-mode will enable this. Note that you need a recent version of the gettext tools to do so. It seems the gfortran contributors use --enable-maintainer-mode as documented. It does not state that -Werror magically appears. It does not say that this option should only be used by an annointed individual. The -Wabi option may have been around for years, but it only recently became a noise emitting useless option. 2018-06-13 Jason Merrill <ja...@redhat.com> * c-opts.c (c_common_post_options): Warn about useless -Wabi. (c_common_handle_option) [OPT_Wabi_]: Remove flag_abi_compat_version handling. I also did not state that libstdc++ was a blocker. The blocker is that bootstrap is broken for me. I wrote BOOTSTRAP. Yes, it was a change in g++ that is the root cause. Unfortunately, the root cause is triggered in libstdc++, because -Wabi has changed, and for some reason libstdc++ developers seem too opposed to fixing the issue! What I find distressing is that I wasted a day finding the problem and developing a patch that was proposed 2 weeks ago. Your review was "No, I don't think we want to simply remove it [-Wabi]." The three follow-up were of the same quality with no actual resolution.
