Alex Ferguson <[EMAIL PROTECTED]> writes:
> The configure for ghc does the following:
>
> checking how to run the C preprocessor... (cached) gcc -E
> checking how to invoke GNU cpp directly... (cached)
> /usr/local/lib/gcc-lib/sparc-sun-solaris2.5/2.7.2.3/cpp
>
> Why the latter? And does it only look in the gcc installation
> for cpp, or does it check ones PATH, or whatever, too?
The configure script actuallly runs gcc with '-v' to find out where
the real cpp lives. The reason is that we need a cpp which can be
used in a pipe (i.e. stdin -> stdout) for mkdependHS. This is bogus,
and it's on my list of things to fix.
BTW, if you're installing the same build on different machines, you
should use a binary distribution and re-configure for each one. If
you want the exact same installation to run on machines with different
gcc locations, that won't work I'm afraid.
Cheers,
Simon
--
Simon Marlow [EMAIL PROTECTED]
University of Glasgow http://www.dcs.gla.ac.uk/~simonm/
finger for PGP public key
