From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: nix@esperi.demon.co.uk (Nix)
Cc: eggert@twinsun.com, haible@ilog.fr, bug-gnu-gettext@gnu.org,
gcc@gcc.gnu.org, zackw@stanford.edu
Subject: Re: gcc 3.2's cpp breaks configure scripts
Date: Sat, 03 Aug 2002 14:55:00 -0000 [thread overview]
Message-ID: <200208032155.g73LtTmE003316@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <87sn1v4r4b.fsf@amaterasu.srvr.nix> from "Nix" at Aug 3, 2002 09:36:04 pm
> On Fri, 2 Aug 2002, Paul Eggert said:
> > If GCC warned only when there was a real problem, a lot of these issues
> > would go away.
>
> Alternatively, GCC could simply ignore the -I switches that would
> trigger those warnings in situations where those warnings are now
> emitted. Is there ever any reason you'd *want* GCC to do that
I think you have to assume the user knows best and wants the change
in ordering and error treatment. If you want to test warnings from
system headers, you can use -nostdinc and configure system and user
headers as you wish.
> reordering? I can't think of any occasion when I'd want to avoid
> fixincluded headers... they have after all been fixincluded for a
> reason (and if the fixincluded headers are broken the solution is
> to delete the broken ones and fix fixincludes, not to supply
> an extra -I/usr/include switch to everything!)
Agreed but hey this is "unix". Anybody know which autoconf macro
was responsible for the "-I/usr/include" in the original problem
report? The current gettext macros which have caused problems
for me don't add /usr/include.
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
next prev parent reply other threads:[~2002-08-03 21:55 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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-11 10:27 John David Anglin
2002-08-12 14:40 ` Nix
-- strict thread matches above, loose matches on Subject: below --
2002-08-01 16:54 Gareth Pearce
[not found] <no.id>
2002-08-01 12:02 ` John David Anglin
2002-08-01 0:15 Gareth Pearce
2002-08-01 0:35 ` Jakub Jelinek
2002-08-01 0:03 Gareth Pearce
2002-08-01 0:07 ` Jakub Jelinek
2002-07-31 23:52 Gareth Pearce
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
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
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=200208032155.g73LtTmE003316@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=bug-gnu-gettext@gnu.org \
--cc=eggert@twinsun.com \
--cc=gcc@gcc.gnu.org \
--cc=haible@ilog.fr \
--cc=nix@esperi.demon.co.uk \
--cc=zackw@stanford.edu \
/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).