Compilation bug

[Simon Marlow]

> With 5.02.2, the build system insists on using the first 
> executable in the 
> path named "ghc" to compile some files.  This has been 
> obnoxious, as I've 
> compiled ghc many times now, only to find that I can't run 
> ghci...  I've had 
> to resort to changing my path and settng some symbolic links 
> to work around 
> this issue.

Could you be a bit more specific?  I've checked through the logs of our
nightly builds, and can't find any files that are being compiled with
plain 'ghc'.  

BTW, the right way to bootstrap ghc from an existing build is to
configure using the --with-ghc option, eg:

	$ ./configure
--with-ghc=/path/to/my/fptools/ghc/compiler/ghc-inplace

Cheers,
	Simon