Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Turn on -Werror by default
Date: Sun, 08 Jan 2006 22:53:00 -0000	[thread overview]
Message-ID: <200601082253.k08MrLY1000252@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060108222546.GA4147@nevyn.them.org> (message from Daniel 	Jacobowitz on Sun, 8 Jan 2006 17:25:47 -0500)

> Date: Sun, 8 Jan 2006 17:25:47 -0500
> From: Daniel Jacobowitz <drow@false.org>
> 
> On Sun, Jan 08, 2006 at 06:59:24PM +0100, Mark Kettenis wrote:
> > A while ago, we basically agreed that this would be a good thing to do
> > after the release.  I tried to steal the code form BFD, but that
> > didn't really fit in very well in our configure.ac.  Anyway, this adds
> > --enable-werror, defaulting to "yes", so to turn it off you'll
> > probably want to use --disable-werror.  This is similar to what BFD
> > does, so you can easily disable -Werror for the whole tree.  To
> > disable -Werror for GDB only, you can use
> > --enable-gdb-build-warnings=,-Wno-error.
> > 
> > ok?
> 
> Unless I've missed quite a lot, all Linux builds and targets are still
> noisy; can we add it but default to disabled for now?  Maybe that'll
> give someone (me?) incentive to finish the cleanup.

Sorry, but I think we've waited long enough.  GCC 4 has been out for 9
months now, so people have had plenty of time to fix issues with it.
In fact, I think people have largely ignored its problems because we
don't enable -Werror by default.  I bet enabling it, will make people
actually fix the problems.

If you're talking about Linux builds that fall over with -Werror even
with older GCC versions, then there is no real excuse.  GDB
maintainers should have been compiling with -Werror for at least the
past four years.

As a compromise, I'm willing to hold off checking in this patch (or
check it in with -enable-werror defaulting to "no"), if we set a fixed
date for enabling it not too far in the future.  The 1st of February
should give people enough time to sort out the last GCC 4 issues.

Mark


  reply	other threads:[~2006-01-08 22:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-08 17:59 Mark Kettenis
2006-01-08 22:25 ` Daniel Jacobowitz
2006-01-08 22:53   ` Mark Kettenis [this message]
2006-01-15 17:01     ` Daniel Jacobowitz
2006-01-15 17:56       ` Mark Kettenis
2006-01-15 18:21         ` Daniel Jacobowitz
2006-01-15 20:04           ` Mark Kettenis
2006-01-15 20:26             ` Daniel Jacobowitz
2006-01-15 20:40               ` Mark Kettenis

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=200601082253.k08MrLY1000252@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    /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