From: Marc Espie <espie@nerim.net>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: New cpp0 warning in 3.1 breaks configure (autoconf)
Date: Tue, 11 Jun 2002 16:11:00 -0000 [thread overview]
Message-ID: <20020611230228.GA1375@tetto.liafa.jussieu.fr> (raw)
In-Reply-To: <or660p1ky9.fsf@free.redhat.lsd.ic.unicamp.br>
On Tue, Jun 11, 2002 at 07:58:54PM -0300, Alexandre Oliva wrote:
> On Jun 11, 2002, Marc Espie <espie@quatramaran.ens.fr> wrote:
>
> > In article <200206112213.g5BMDp3L044244@latour.rsch.comm.mot.com> you write:
> >> I think the current behavior is worth defending since skipping fixed
> >> system headers can cause serve cascading problems that are hard to
> >> debug by the user.
> > Of course, this does assume the compiler and fixincludes are always right.
> -I/usr/include is always wrong. -isystem /usr/include might be
> acceptable.
Well, the problem stemmed from /usr/local/include in the first place.
Entirely different beast.
See what I mean about different assumptions ?
next prev parent reply other threads:[~2002-06-11 23:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020606204404.GA17526@bort.dtek.chalmers.se>
2002-06-07 16:39 ` H}kan Hjort
2002-06-09 23:04 ` Phil Edwards
2002-06-09 23:07 ` Neil Booth
2002-06-09 23:30 ` Russ Allbery
2002-06-10 10:33 ` Jonathan Lennox
2002-06-10 10:22 ` DJ Delorie
2002-06-10 13:36 ` Fergus Henderson
2002-06-11 15:33 ` Loren James Rittle
2002-06-11 15:59 ` Marc Espie
2002-06-11 16:04 ` Alexandre Oliva
2002-06-11 16:11 ` Marc Espie [this message]
2002-06-11 21:12 ` Alexandre Oliva
2002-06-12 5:07 ` Marc Espie
2002-06-12 7:21 ` Alexandre Oliva
2002-06-12 11:14 ` Jason R Thorpe
2002-06-12 23:55 ` Andris Pavenis
2002-06-11 16:25 ` Phil Edwards
2002-06-11 17:15 ` Daniel Jacobowitz
2002-06-11 18:38 ` Zack Weinberg
2002-06-11 18:49 ` Daniel Jacobowitz
2002-06-11 17:06 ` Loren James Rittle
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=20020611230228.GA1375@tetto.liafa.jussieu.fr \
--to=espie@nerim.net \
--cc=aoliva@redhat.com \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).