Simon Marlow wrote:
network is one of those packages that has a configure script, but the configure script is generated by autoconf from configure.ac, so it is not stored in the darcs repository. When you get the network package from darcs, you need to
$ autoreconf $ runhaskell Setup configure etc.
Great -- thanks. I can confirm that with the latest darcs version of the network library, doing that step allowed the library to build and install successfully (though still with the GCC spam I mentioned). (The latest hackage version of network still did not install properly even if I used autoreconf.) My next failing package install attempt was uvector, which fails with messages like those I got with the unix package: Data/Array/Vector/Prim/BUArr.hs:851:26: `haFD' is not a (visible) field of constructor `Handle__' Data/Array/Vector/Prim/BUArr.hs:851:35: `haBuffer' is not a (visible) field of constructor `Handle__' Data/Array/Vector/Prim/BUArr.hs:851:49: `haIsStream' is not a (visible) field of constructor `Handle__' Data/Array/Vector/Prim/BUArr.hs:852:10: Not in scope: data constructor `Buffer' Data/Array/Vector/Prim/BUArr.hs:852:19: `bufBuf' is not a (visible) field of constructor `Buffer' Data/Array/Vector/Prim/BUArr.hs:852:33: `bufWPtr' is not a (visible) field of constructor `Buffer' The latest darcs version of uvector is no different. Will these problems need to be fixed in the code on a per-package basis, or is there a cabal fix that can overcome them? Thanks, Neil.