patch applied (ghc): Simplify utils/pwd
Matthias Kilian
kili at outback.escape.de
Thu May 7 01:40:26 EDT 2009
On Thu, May 07, 2009 at 11:42:18AM +1000, Manuel M T Chakravarty wrote:
> Are you sure, you got that right? I am getting
>
> >limitingfactor chak 16 (.../Code/ghc-test): sh validate
> >Booting .
> >Booting libraries/base
> >Booting libraries/directory
> >Booting libraries/old-time
> >Booting libraries/process
> >Booting libraries/terminfo
> >Booting libraries/unix
> >Creating libraries/Cabal/ghc.mk
> >Creating libraries/Cabal/GNUmakefile
> >[..]
> >checking for ld... /usr/bin/ld
> >checking for path to top of build tree... Bad args: []
> >Usage: pwd {forwardslash|quadruple-backslash}
> >configure: error: cannot determine current directory
> >limitingfactor chak 17 (.../Code/ghc-test):
>
> on Mac OS X.
I'm still not convinced that this pwd thingy isn't completely stupid
(noone explained to me why it is really required for the windows
builds). I hope to get some time next weekend and make it obsolete,
but someone of the windows people have help me with at least a test
build.
If everything else fails, this program should be renamed to something
less confusing (like ghc-pwd or stupid-pwd). It already happened
in the past the pwd got installed into the bindir and then you get
really weird effects.
Ciao,
Kili
More information about the Cvs-ghc
mailing list