This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: building
- From: Ben Elliston <bje at wasabisystems dot com>
- To: gcc at gcc dot gnu dot org
- Date: 14 Jul 2003 12:17:14 +1000
- Subject: Re: building
- References: <200306181709.25512.peteman@math.unm.edu> <200306201024.48220.peteman@math.unm.edu> <1056168167.2464.1.camel@fizzgig> <200306201125.29015.peteman@math.unm.edu> <3EF7B33F.1000501@tuliptree.org>
Jim Wilson <wilson@tuliptree.org> writes:
> There is a much simpler explanation for your problem. Gcc uses the
> environment variable $CPP to run the preprocessor if it is set,
> otherwise it uses "gcc -E". If you have this environment variable
> set to something which isn't a preprocessor, then you will get this
> configure error. Get rid of the CPP environment variable, and gcc
> will build.
I also tripped over this problem recently, but with a different cause.
I was using a version of bash from NetBSD's pkgsrc system (2.05, I
believe) that exhibited a bug that was causing the relevant cpp
config.cache shell variable to be set to "$gcc -E". Upgrading to the
latest version (2.05b) in pkgsrc made the problem go away.
Ben