From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com, carlton@kealia.com
Cc: gdb@sources.redhat.com
Subject: Re: -Wformat
Date: Fri, 01 Aug 2003 18:25:00 -0000 [thread overview]
Message-ID: <200308011825.h71IPJrs013181@duracef.shout.net> (raw)
David Carlton asks:
> I was wondering about that. Am I the only person who compiles with
> -Werror and who uses GCC 3.x? I would have expected somebody else to
> have noticed. Still, it's only been in the tree for a week.
I build gdb with gcc 3.3 (that's the "host tools" section in my report).
But I don't turn on -Werror.
Michael C
next reply other threads:[~2003-08-01 18:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 18:25 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-01 15:49 -Wformat David Carlton
2003-08-01 16:08 ` -Wformat Andrew Cagney
2003-08-01 16:18 ` -Wformat David Carlton
2003-08-01 16:30 ` -Wformat Andrew Cagney
2003-08-01 16:33 ` -Wformat Daniel Jacobowitz
2003-08-01 16:46 ` -Wformat David Carlton
2003-08-01 16:48 ` -Wformat Daniel Jacobowitz
2003-08-01 17:53 ` -Wformat 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=200308011825.h71IPJrs013181@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@redhat.com \
--cc=carlton@kealia.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