This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/86450] Bootstrap failure due to -Wabi
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 10 Jul 2018 20:23:13 +0000
- Subject: [Bug libstdc++/86450] Bootstrap failure due to -Wabi
- Auto-submitted: auto-generated
- References: <bug-86450-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Steve Kargl from comment #3)
> On Tue, Jul 10, 2018 at 09:55:15AM +0000, rguenth at gcc dot gnu.org wrote:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
> >
> > --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
> > Can you check whether removing --enable-maintainer-mode fixes the build? I've
> > not had this issue but I see those Wabi warnings as non-error.
> >
>
> Yes, removing --enable-maintainer-mode allows the bootstrap to
> complete. Problem is I need to use that option as I have change
> a chnaged a Makefile.am, so need to regenerate the Makefile.in.
I still don't understand this requirement. Using maintainer mode is not the
only way to regenerate autoconf files, and has the downside of enabling
-Werror.
Can you try --disable-werror ?