Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: tromey@redhat.com, Elena Zannoni <ezannoni@redhat.com>,
	gdb-patches@sources.redhat.com
Subject: Re: RFA: osabi.c correctness patch (Was: new build failure)
Date: Tue, 27 Aug 2002 20:12:00 -0000	[thread overview]
Message-ID: <3D6C264F.3FDCD67F@redhat.com> (raw)
In-Reply-To: <3D6C0D42.8030401@ges.redhat.com>

Andrew Cagney wrote:
> 
> >>>>>> "Elena" == Elena Zannoni <ezannoni@redhat.com> writes:
> >
> >
> > Elena> I wonder if we should enable ,-Werror by default on certain
> > Elena> platforms.
> >
> > I was under the impression that the maintainers used it regularly.
> > That's why I enabled it in my builds -- to avoid submitting
> > embarrassing patches in the future :-)
> 
> BTW, your warnings had me puzzled.  I'm building on 7.3, and wasn't
> seeing these!  It turns out that I wasn't using the pre-installed
> compiler :-(
> 
> Anyway, yes, maintainers should have -Werror enabled.  Unfortunatly, the
> best laid plans can occasionally fall down during the implementation stage.

I wonder if we could arrange some sort of makefile switch 
that would be on by default, but turned off by the release
process?


  reply	other threads:[~2002-08-28  1:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87n0r8i35t.fsf@fleche.redhat.com>
     [not found] ` <15723.52602.741154.488098@localhost.redhat.com>
2002-08-27 13:37   ` Tom Tromey
2002-08-27 13:58     ` Tom Tromey
2002-08-27 15:37       ` Elena Zannoni
2002-08-27 15:42         ` Tom Tromey
2002-08-27 16:53           ` Andrew Cagney
2002-08-27 20:12             ` Michael Snyder [this message]
2002-08-27 15:32     ` Elena Zannoni

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=3D6C264F.3FDCD67F@redhat.com \
    --to=msnyder@redhat.com \
    --cc=ac131313@ges.redhat.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=tromey@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