If the bug is in cabal-install 0.3, that is easy - as HP picks and builds that. If the bug in cabal, that requires a bump in what GHC central builds and packages.
Which is it? - Mark On Wed, Apr 17, 2013 at 8:46 AM, Ian Lynagh <[email protected]> wrote: > On Wed, Apr 17, 2013 at 05:37:37PM +0200, Gabor Greif wrote: > > On 4/17/13, Iavor Diatchki <[email protected]> wrote: > > > Hello, > > > > > > cabal-install 1.16.0 and 1.16.0.1 have some serious bugs that one > > > encounters rather quickly. For example, at work I wasted some time > until I > > > figured out that cabal was generating a 'Paths_' module that does not > > > compile. Because of this, you can't even use it to install a newer > > > version of itself, where the problem is fixed: you have to manually > > > bootstrap the new version with the script! > > > > I came up with this. > > > > http://heisenbug.blogspot.fr/2013/02/old-cabal-subhell.html > > > > Pretty much what you have experienced. > > This doesn't appear to affect the Cabal that GHC 7.6.2 ships with. I get > > ... > > catchIO :: IO a -> (Exception.IOException -> IO a) -> IO a > catchIO = Exception.catch > > ... > > getBinDir = catchIO (getEnv "HTTP_bindir") (\_ -> return bindir) > > in Paths_HTTP. > > > Thanks > Ian > > > _______________________________________________ > Libraries mailing list > [email protected] > http://www.haskell.org/mailman/listinfo/libraries >
_______________________________________________ ghc-devs mailing list [email protected] http://www.haskell.org/mailman/listinfo/ghc-devs
