public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: H}kan Hjort <d95hjort@dtek.chalmers.se>
Cc: gcc-bugs@gcc.gnu.org, gcc@gcc.gnu.org,
	Nathan Sidwell <nathan@codesourcery.com>,
	DJ Delorie <dj@redhat.com>
Subject: Re: New cpp0 warning in 3.1 breaks configure (autoconf)
Date: Sun, 09 Jun 2002 23:04:00 -0000	[thread overview]
Message-ID: <20020610004909.A8924@disaster.basement.lan> (raw)
In-Reply-To: <20020607224407.GA25353@bort.dtek.chalmers.se>; from d95hjort@dtek.chalmers.se on Sat, Jun 08, 2002 at 12:44:07AM +0200

On Sat, Jun 08, 2002 at 12:44:07AM +0200, H}kan Hjort wrote:
> And reports in that thread of extra failurs in the testsuite from this
> change.

Yep.

> Further evidens of problems with these warnings can be found here
> http://gcc.gnu.org/ml/gcc-bugs/2002-04/msg00149.html
> 
> Where can the forbidden directories be found?  
> (Guessing based on gcc -v -E ..., /usr/local/include /usr/include)

Pretty much.  Any of the "standard system" directories on a particular
platform, also (IIRC) any of the include directories under the --prefix
directory.  Which means you must be careful installing symlinks to the
compiler.

> Is there anyway to get rid of this warning?

Nope.

> Why is it on by default?

Nobody knows.

> How are one supposed to workaround this in configure scripts?

You can't.  I changed my local copy of the compiler sources to no longer
warn about it.


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-06-10  4:49 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 [this message]
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
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=20020610004909.A8924@disaster.basement.lan \
    --to=phil@jaj.com \
    --cc=d95hjort@dtek.chalmers.se \
    --cc=dj@redhat.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=nathan@codesourcery.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).