From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: ac131313@cygnus.com
Cc: Richard.Earnshaw@arm.com, gdb@sources.redhat.com
Subject: Re: Results of a multi-build (not good)
Date: Tue, 12 Mar 2002 11:24:00 -0000 [thread overview]
Message-ID: <7263-Tue12Mar2002212108+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <3C8E36A9.1060304@cygnus.com> (message from Andrew Cagney on Tue, 12 Mar 2002 12:11:05 -0500)
> Date: Tue, 12 Mar 2002 12:11:05 -0500
> From: Andrew Cagney <ac131313@cygnus.com>
> >
> > IMHO, -Werror is a Bad Idea (tm). With the current trend in GCC and
> > other compilers to print warnings for perfectly valid C, -Werror tends to
> > break good code with every new release of GCC, to say nothing of
> > development snapshots people use.
> >
> > I think we should stop using -Werror, except maybe in maintainer's mode.
>
> -Werror is only enabled when someone explicitly specifies it with
> --enable-gdb-warnings=,-Werror.
Then how come Richard has failures on platforms that didn't use
that? Richard, did you enable -Werror explicitly?
next prev parent reply other threads:[~2002-03-12 19:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-11 10:52 Richard Earnshaw
2002-03-11 11:08 ` Andrew Cagney
2002-03-12 2:12 ` Richard Earnshaw
2002-03-11 12:02 ` Andrew Cagney
2002-03-12 2:14 ` Richard Earnshaw
2002-03-12 9:27 ` Andrew Cagney
2002-03-11 22:13 ` Eli Zaretskii
2002-03-12 9:11 ` Andrew Cagney
2002-03-12 11:24 ` Eli Zaretskii [this message]
2002-03-13 2:00 ` Richard Earnshaw
2002-03-12 3:14 ` Richard Earnshaw
2002-03-12 9:35 ` Andrew Cagney
2002-03-12 9:45 ` Richard Earnshaw
2002-03-14 6:06 ` Richard Earnshaw
2002-03-23 10:45 ` Andrew Cagney
2002-03-23 10:52 ` Richard Earnshaw
2002-03-23 11:33 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7263-Tue12Mar2002212108+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=Richard.Earnshaw@arm.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox