Re: (alpha) "stick shift" cabal install for GHC 6.12.1
On Dec 18, 2009, at 5:27 AM, Antoine Latter wrote: > Do you have any more information about this failure? It seems like it > would be easier to get zlib to work than to replicate cabal-install. From http://www.reddit.com/r/haskell/comments/afz6n/cabalinstallpy/ : dcoutts BTW, the reason you could not get cabal-install working on your OSX 10.6 is because you did not have a fully working GHC installation and zlib (a dep of cabal-install) was the first thing to trip over this. Since GHC-6.10.4 does not work "out of the box" on OSX 10.6 you followed some hints to modify the ghc wrapper script to pass the gcc flags -m32. The bit you missed is that you need to do the same for hsc2hs. Otherwise hsc2hs generates code that assumes you're targeting the 64bit ABI. That's why the zlib initialisation check fails, because the code calling zlib has been compiled for the wrong size of everything. Syzygies Bingo, that sounds right, it's a relief to know what happened. There's plenty of advice on the web to just modify the ghc script itself for GHC-6.10.4 on OSX 10.6. I knew to modify more scripts, but I missed hsc2hs. I had gotten as far as figuring out that zlib itself was broken, and I had set up some "sandbox" clean development volume images for testing, when I noticed that GHC-6.12.1 was out. And that cabal-install wasn't ready yet.___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Re: (alpha) "stick shift" cabal install for GHC 6.12.1
On Thu, 2009-12-17 at 14:00 -0800, Dave Bayer wrote: > Background: I never got "cabal install" to work on OS X 10.5 with GHC > 6.10.4, basically because zlib wouldn't work. Odd, because a perfectly > good version of gunzip already exists on most platforms, and the code > doesn't fall back to this version if needed. Do you mean OSX 10.5 or 10.6. I've never heard of major problems on 10.5 and lots of problems on 10.6. The latter are all fixable. The issue on 10.6 was that gcc defaults to compiling 64bit, but ghc expects 32bit. The hack for ghc-6.10.4 was to change the wrapper script to pass -optc-m32 -optl-m32. That's enough to get ghc working, but for other packages that bind to foreign libs you also need to apply the same trick to hsc2hs. That's why so many people bumped into zlib not working, it was because their hsc2hs was thinking it should be using 64bit when everything else was expecting 32bit. That manifested in a zlib initialisation error (because the structure size check fails). So in short, the problems are not with cabal or zlib, you just need a fully working ghc installation. Duncan ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Re: (alpha) "stick shift" cabal install for GHC 6.12.1
On Thu, Dec 17, 2009 at 4:00 PM, Dave Bayer wrote: > > Background: I never got "cabal install" to work on OS X 10.5 with GHC 6.10.4, > basically because zlib wouldn't work. Odd, because a perfectly good version > of gunzip already exists on most platforms, and the code doesn't fall back to > this version if needed. > Do you have any more information about this failure? It seems like it would be easier to get zlib to work than to replicate cabal-install. My painful story of getting zlib to work on 10.6 is chronicled here: http://www.haskell.org/pipermail/glasgow-haskell-users/2009-November/018068.html But my problem should only have been an issue on OS X 10.6, not any version lower. Antoine ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
RE: (alpha) "stick shift" cabal install for GHC 6.12.1
Dave Bayer wrote: > There's clearly something wrong with this picture. A Rorschach blot > test as to what's wrong, but I see people overreaching, if I have to > wait weeks for a simple install tool, then months for the Haskell > Platform to be ready. Hopefully future GHC releases will go more smoothly as far as having cabal-install ready is concerned. But generally I think it's right to have a gap between a GHC major release and the corresponding HP release, in which to plan and manage any migration required. In that gap only library authors and users who don't mind some breakage would be expected to use the new GHC. Cheers, Ganesh === Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html === ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Re: (alpha) "stick shift" cabal install for GHC 6.12.1
I put up a web page with better directions, after some good experiences testing this script for my own use: http://www.math.columbia.edu/~bayer/Haskell/cabal-install/ On Dec 17, 2009, at 2:00 PM, Dave Bayer wrote: > I wrote the barest possible python script this morning as a poor-man's > replacement for "cabal install". ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
