This is the mail archive of the
mailing list for the GCC project.
Re: New cpp0 warning in 3.1 breaks configure (autoconf)
- From: Phil Edwards <phil at jaj dot com>
- To: H}kan Hjort <d95hjort at dtek dot chalmers dot se>
- Cc: gcc-bugs at gcc dot gnu dot org, gcc at gcc dot gnu dot org, Nathan Sidwell <nathan at codesourcery dot com>, DJ Delorie <dj at redhat dot com>
- Date: Mon, 10 Jun 2002 00:49:09 -0400
- Subject: Re: New cpp0 warning in 3.1 breaks configure (autoconf)
- References: <20020606204404.GA17526@bort.dtek.chalmers.se> <20020607224407.GA25353@bort.dtek.chalmers.se>
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
> Further evidens of problems with these warnings can be found here
> 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
> Is there anyway to get rid of this warning?
> Why is it on by default?
> 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.
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