Re: [Hackage] #349: cabal install hangs using CPU when resolving dependencies on ghc 6.9

#349: cabal install hangs using CPU when resolving dependencies on ghc 6.9 -+-- Reporter: ganesh |Owner: Type: defect | Status: new Priority: high

patch applied (cabal): filter mingw include directories out of rts's installDirs

Thu Sep 18 07:29:58 PDT 2008 Ian Lynagh <[EMAIL PROTECTED]> * filter mingw include directories out of rts's installDirs GHC < 6.10 put "$topdir/include/mingw" in rts's installDirs. This breaks when you want to use a different gcc, so we need to filter it out. M ./Distribution/Simple/G

patch applied (cabal): Tell gcc on Windows where include/mingw is

Thu Sep 18 06:57:18 PDT 2008 Ian Lynagh <[EMAIL PROTECTED]> * Tell gcc on Windows where include/mingw is We need to tell the gcc bundled with GHC on Windows where its mingw include directory is M ./Distribution/Simple/GHC.hs -1 +2 View patch online: http://darcs.haskell.org/cabal/_darc

Re: Who defines __GLASGOW_HASKELL__, __HADDOCK__, etc?

On Thu, Sep 18, 2008 at 12:30:42AM +0100, Claus Reinke wrote: > So far, I had assumed that every tool defined its own macro, > but it seems that __GLASGOW_HASKELL__ is defined by > ghc and by cabal, while __HADDOCK__ is defined only by > the latter. Is that right? Yes, Cabal defines __HADDOCK__ on