Alex Ferguson <[EMAIL PROTECTED]> writes:
> > It does for me - but the sense of the link is reversed (i.e. now ghc
> > points to ghc-2.09, which is the real driver).
>
> Odd. It doesn't seem to do this at all for me. There's no "ghc-2.09",
> and "ghc" isn't a link. I can't see where in the makefile this should
> be happening, either, but as I said, ah dinnae ken GHC makefiles...
Did you do 'make install' in ghc, instead of using the binary
distribution? That might cause the script to be installed as 'ghc'
instead of 'ghc-2.09'. Will fix for the next release.
> Why not make it a "hard" link, in the same directory, thereby making
> the point of which one is the real one moot?
Hard links are a pain for several reasons - if you install a new ghc
over the existing one, you have to be sure to remove the old one
first, or you might stomp on the ghc-2.09 link too...
Cheers,
Simon
--
Simon Marlow [EMAIL PROTECTED]
University of Glasgow http://www.dcs.gla.ac.uk/~simonm/
finger for PGP public key
