One more thing, I also had to add my cygwin bin directory containing
"sh.exe" to my Windows %PATH% variable. This allowed network to configure
from the windows command prompt.
/jve
On Wed, Oct 29, 2008 at 8:37 PM, John Van Enk
Hello All,
runhaskell Setup configure Configuring hsc2hs-0.67.20061107... Warning: No 'build-type' specified. If you do not need a custom Setup.hs or ./configure script then use 'build-type: Simple'.
I'm trying to reinstall network-2.2.0.0 against Parsec 3 in Windows. Well, this is really hard/impossible to do. Here's what I've done so far: 1) After bashing my face against my desk for a while, I got cabal-install installed in windows. 2) cabal install network --reinstall 3) This freaks out because I don't have hsc2hs installed, but it doesn't tell me that, it just complains about something having to do with sizeof. 4) I figure out that I need hsc2hs installed, and i put cabal-install to use fetching it for me. 5) cabal-install fails because hsc2hs needs the process and directory packages, but they aren't exposed by the cabal file (at least in the version sitting on hackage, I assume this is the right one to use). 6) I give up on using cabal-install to get hsc2hs, so i download the targz for hsc2hs directly. 7) I fix the .cabal file to include process and directory 8) runhaskell Setup configure: 9) runhaskell Setup build: Everything works fine. 10) runhaskell Setup install: Everything works fine. 11) Go back to try and install network-2.2.0.0 again with cabal-install. 12) Gets past the sizeof/hsc2hs errors, but then chokes on spaces in build path names: Preprocessing library network-2.2.0.0... gcc.exe: Files\Haskell\parsec-2.1.0.1\ghc-6.8.3: No such file or directory linking dist\build\Network\BSD_hsc_make.o failed command was: C:\ghc\ghc-6.8.3\gcc.exe -BC:\ghc\ghc-6.8.3\gcc-lib -IC:\ghc\ghc-6.8.3\include\mingw -LC:\Program Files\Haskell\parsec-2.1.0.1\ghc-6.8.3 -LC:\ghc\ghc-6.8.3/lib\base-3.0.2.0 -lwsock32 -lmsvcrt -lkernel32 -luser32 -lshell32 -LC:\ghc\ghc-6.8.3 -LC:\ghc\ghc-6.8.3/gcc-lib -lm -lgmp -lwsock32 dist\build\Network\BSD_hsc_make.o -o dist\build\Network\BSD_hsc_make.exe cabal: Error: some packages failed to install: network-2.2.0.0 failed during the building phase. The exception was:exit: ExitFailure 1 13) And this is where I finally gave up and came here.
Does any one have any insight into: 1) Why cabal doesn't check for hsc2hs during a configure 2) How I can rebuild network-2.2.0.0 on my Windows box without sacrificing a goat to Bill Gates/GHC Gods?
Thanks.
/jve