On Fri, Jan 16, 2009 at 09:32:47AM +, Simon Marlow wrote:
>
> and I have no idea what the problem is here. Why are we using
> c:\cygwin\bin\gcc.exe? That seems highly dubious.
Neither the old build system nor the new build system put gcc where
Cabal expects it, so it was falling back to lo
On Fri, Jan 16, 2009 at 09:14:23AM +, Simon Marlow wrote:
>
> Setup.exe: Cannot find the program 'ghc' at
> '/cygdrive/c/builds/ghc-HEAD/ghc/stage2-inplace/ghc' or on the path
Now fixed.
Thanks
Ian
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
htt
On Fri, 2009-01-16 at 09:32 +, Simon Marlow wrote:
> and I have no idea what the problem is here. Why are we using
> c:\cygwin\bin\gcc.exe? That seems highly dubious.
If it is Cabal that is calling the dubious version of gcc then it may be
due to:
Fri Jan 9 15:35:07 GMT 2009 Ian Lynagh
Simon Marlow wrote:
With Cygwin - this has been broken for a couple of days now, I'm waiting
to get a working validate so I can push two validate fixes :-(
make[1]: Entering directory
`/cygdrive/c/builds/ghc-HEAD/testsuite/tests/ghc-regress'
Looks like you don't have timeout, building it firs
With Cygwin - this has been broken for a couple of days now, I'm waiting to
get a working validate so I can push two validate fixes :-(
make[1]: Entering directory
`/cygdrive/c/builds/ghc-HEAD/testsuite/tests/ghc-regress'
Looks like you don't have timeout, building it first...
make -C ../../ti
