a bunch of windows problems

[anonymous]

From Bryn Keller

I took a better look at the GNUMakefile for Cabal-1.1.1 and realized it 
was a complete red herring - best ignored altogether under Windows! 
Doing the regular cabal dance worked just fine and I now have 
Cabal-1.1.1 installed.

As for cabal-get, I ran into a couple of problems - first of all, 
"./setup" fails because the shell that runs it (even if invoked under 
Cygwin) is cmd.exe, not bash. Second, the sudo command doesn't exist 
even in Cygwin. I'm attaching patches for these issues. Finally, the 
install script fails because GNUpgp package has an error in its cabal 
file - it specifies "hs-source-dirs: src," but it should be 
"hs-source-dir", not "hs-source-dirs", and the source is not actually in 
a "src" dir at all. Removing that line from the .cabal file fixed that 
problem.

Also, I keep getting warnings from ghc like:

ghc: unknown package: Cabal-1.0

though this doesn't actually seem to cause a problem so far. Not sure 
why it's looking for Cabal-1.0 when I already have Cabal-1.1.1. (I had 
to unregister Cabal-1.0 to avoid other errors).  Interestingly, many 
packages wouldn't compile until I removed Crypto-2.0.2 from my system.  
I would have expected that different version could coexist... oh well.

More seriously, I get this compile error:

Compiling Network.Hackage.CabalGet.Install ( 
./Network/Hackage/CabalGet/Install.
hs, dist\build\./Network/Hackage/CabalGet/Install.o )

./Network/Hackage/CabalGet/Install.hs:118:45: Not in scope: `installHandler'

./Network/Hackage/CabalGet/Install.hs:118:60: Not in scope: `keyboardSignal'

./Network/Hackage/CabalGet/Install.hs:118:76:
   Not in scope: data constructor `Catch'

./Network/Hackage/CabalGet/Install.hs:120:31: Not in scope: `installHandler'

./Network/Hackage/CabalGet/Install.hs:120:46: Not in scope: `keyboardSignal'

Thanks,
Bryn

[duncan]

I think all of the problems reported here are rather out of date now. We don't use any makefile now to bootstrap and cabal-get has been replaced.