public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: Neil Booth <neil@daikokuya.co.uk>
Cc: Joe Buck <Joe.Buck@synopsys.com>,
	Gareth Pearce <tilps@hotmail.com>,
	gcc@gcc.gnu.org
Subject: Re: gcc 3.2's cpp breaks configure scripts
Date: Thu, 01 Aug 2002 12:31:00 -0000	[thread overview]
Message-ID: <20020801153040.A19422@disaster.basement.lan> (raw)
In-Reply-To: <20020801181339.GA8471@daikokuya.co.uk>; from neil@daikokuya.co.uk on Thu, Aug 01, 2002 at 07:13:39PM +0100

On Thu, Aug 01, 2002 at 07:13:39PM +0100, Neil Booth wrote:
> Phil Edwards wrote:-
> > Yes, please.  I'm very annoyed that GCC prints warnings that I cannot disable
> > when I /know/ that they are false or harmless.
> > 
> > I'm wrestling with my development machine at the moment (sysadmin issues),
> > but once it is working again, I will work up such a patch if there is a
> > consensus that it would be worthwhile.  (And if we can agree on option
> > spelling.)
> 
> Please, not more switches.

Fair enough.

> Let's either fix the warning, agree its
> correct, or get rid of it.

Well, you know my opinion.  :-)  I vote for (C).


Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams

  reply	other threads:[~2002-08-01 19:31 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-31  8:58 Jeff Garzik
2002-07-31  9:07 ` Gareth Pearce
2002-07-31 12:44   ` Joe Buck
2002-08-01 10:32     ` Phil Edwards
2002-08-01 11:15       ` Neil Booth
2002-08-01 12:31         ` Phil Edwards [this message]
2002-07-31  9:19 ` Andreas Schwab
2002-07-31  9:39   ` Jeff Garzik
2002-07-31  9:39     ` Jan-Benedict Glaw
2002-07-31  9:54       ` Michael Matz
2002-08-01  9:45         ` Kai Henningsen
2002-08-01 12:40           ` Kevin Handy
2002-08-01  9:45   ` Kai Henningsen
2002-08-01 14:47     ` Joe Buck
2002-08-08 20:39       ` Roger Corman
2002-08-09 12:07         ` Joe Buck
2002-07-31 23:52 Gareth Pearce
2002-08-01  0:03 Gareth Pearce
2002-08-01  0:07 ` Jakub Jelinek
2002-08-01  0:15 Gareth Pearce
2002-08-01  0:35 ` Jakub Jelinek
     [not found] <no.id>
2002-08-01 12:02 ` John David Anglin
     [not found] <200208021635.g72GZDrs008047@hiauly1.hia.nrc.ca>
2002-08-01 14:52 ` H}kan Hjort
2002-08-01 20:09   ` John David Anglin
2002-08-02 11:01   ` Bruno Haible
2002-08-02 12:29     ` John David Anglin
2002-08-02 14:42       ` Paul Eggert
2002-08-03 13:48         ` Nix
2002-08-03 14:55           ` John David Anglin
2002-08-03 15:24             ` Zack Weinberg
2002-08-03 19:34           ` Gareth Pearce
2002-08-03 14:42         ` John David Anglin
2002-08-03 15:36           ` Gabriel Dos Reis
2002-08-03 16:07           ` Zack Weinberg
2002-08-03 20:33             ` John David Anglin
2002-08-03 21:58               ` Miles Bader
2002-08-03 21:58             ` Daniel Jacobowitz
2002-08-01 16:54 Gareth Pearce
2002-08-11 10:27 John David Anglin
2002-08-12 14:40 ` Nix

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=20020801153040.A19422@disaster.basement.lan \
    --to=phil@jaj.com \
    --cc=Joe.Buck@synopsys.com \
    --cc=gcc@gcc.gnu.org \
    --cc=neil@daikokuya.co.uk \
    --cc=tilps@hotmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).