https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #26 from Jonathan Wakely ---
No, I needed far more than that. Obviously I needed the right versions of
autoconf and automake first in my PATH, which is simple. But I also needed to
use contrib/gcc_update to fix all the timestamps, so
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #25 from Steve Kargl ---
On Tue, Jul 17, 2018 at 01:24:00PM +, redi at gcc dot gnu.org wrote:
>
> --- Comment #23 from Jonathan Wakely ---
> This should be fixed now, please confirm (I can't even get a
> build to complete with -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
Thomas Koenig changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #23 from Jonathan Wakely ---
This should be fixed now, please confirm (I can't even get a build to complete
with --enable-maintainer-mode, I continue to be amazed you rely on something so
fragile).
--enable-maintainer-mode no longer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #22 from Jonathan Wakely ---
Author: redi
Date: Tue Jul 17 13:18:47 2018
New Revision: 262824
URL: https://gcc.gnu.org/viewcvs?rev=262824&root=gcc&view=rev
Log:
PR libstdc++/86450 use -Wabi=2 and simplify -Werror use
Use -Wabi=2 to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #21 from Thomas Koenig ---
(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
> conta
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #20 from Jonathan Wakely ---
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 --e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #19 from Thomas Koenig ---
As a more long-term solution, I think that having -Werror on as the
default should actually be preferred, at least for those parts of
gcc which are clean at the moment.
If somebody then does something which
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #18 from Steve Kargl ---
On Tue, Jul 10, 2018 at 10:11:54PM +, redi at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
>
> --- Comment #17 from Jonathan Wakely ---
> The problem is that gfortran devel
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #17 from Jonathan Wakely ---
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #16 from Steve Kargl ---
On Tue, Jul 10, 2018 at 09:40:16PM +, redi at gcc dot gnu.org wrote:
>
> > There is an obvious patch.
> > I will commit my patch by the end of the day,
> > or revert the patch causing the problem.
>
> O
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #15 from Thomas Koenig ---
(In reply to Jonathan Wakely from comment #11)
> (In reply to Thomas Koenig from comment #9)
> > (In reply to Jonathan Wakely from comment #7)
> > > These warnings have been present for weeks - the idea that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #14 from Jonathan Wakely ---
Because we haven't decided what the fix is.
Something like this seems better than dealing with each warning one by one
every time this happens:
--- a/libstdc++-v3/acinclude.m4
+++ b/libstdc++-v3/acinclud
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #13 from Steve Kargl ---
On Tue, Jul 10, 2018 at 08:24:57PM +, redi at gcc dot gnu.org wrote:
>
> --- Comment #7 from Jonathan Wakely ---
> Why can't you use autoconf or autoreconf like everybody else?
>
Why not fix the under
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #12 from Jonathan Wakely ---
(In reply to Steve Kargl from comment #10)
> On Tue, Jul 10, 2018 at 08:35:48PM +, redi at gcc dot gnu.org wrote:
> >
> > See https://gcc.gnu.org/ml/gcc-patches/2018-06/msg01923.html
> > and https://g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #11 from Jonathan Wakely ---
(In reply to Thomas Koenig from comment #9)
> (In reply to Jonathan Wakely from comment #7)
> > These warnings have been present for weeks - the idea that they're suddenly
> > preventing anybody from worki
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #10 from Steve Kargl ---
On Tue, Jul 10, 2018 at 08:35:48PM +, redi at gcc dot gnu.org wrote:
>
> See https://gcc.gnu.org/ml/gcc-patches/2018-06/msg01923.html
> and https://gcc.gnu.org/ml/gcc-patches/2018-07/msg00059.html
>
Why
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #9 from Thomas Koenig ---
(In reply to Jonathan Wakely from comment #7)
> These warnings have been present for weeks - the idea that they're suddenly
> preventing anybody from working on gfortran is odd. Why can't you use
> autoconf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #8 from Jonathan Wakely ---
(In reply to Steve Kargl from comment #5)
> This fixes the bootstrap failure
>
> Index: libstdc++-v3/acinclude.m4
> ===
> --- libstdc++-v3/ac
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #7 from Jonathan Wakely ---
These warnings have been present for weeks - the idea that they're suddenly
preventing anybody from working on gfortran is odd. Why can't you use autoconf
or autoreconf like everybody else?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #6 from Jonathan Wakely ---
(In reply to Steve Kargl from comment #3)
> On Tue, Jul 10, 2018 at 09:55:15AM +, rguenth at gcc dot gnu.org wrote:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
> >
> > --- Comment #2 from Ri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #5 from Steve Kargl ---
On Tue, Jul 10, 2018 at 06:46:33PM +, sgk at troutmask dot
apl.washington.edu wrote:
>
> % find . -type f | xargs grep Wabi
> ...
> ./libstdc++-v3/acinclude.m4: WARN_FLAGS='-Wall -Wextra -Wwrite-strings
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #4 from Steve Kargl ---
On Tue, Jul 10, 2018 at 09:55:15AM +, rguenth at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
>
> Richard Biener changed:
>
>What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
--- Comment #3 from Steve Kargl ---
On Tue, Jul 10, 2018 at 09:55:15AM +, rguenth at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
>
> --- Comment #2 from Richard Biener ---
> Can you check whether removing --e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86450
Richard Biener changed:
What|Removed |Added
Keywords||build
Component|bootstrap
25 matches
Mail list logo
