On Fri, Aug 08, 2008 at 09:28:50PM +0100, Claus Reinke wrote: > >>>Running Haddock for ghc-6.9... > >>>Heap exhausted; > >>>Current maximum heap size is 268435456 bytes (256 Mb); > >>This is haddock failing, right? What version do you have? > > > >Yes. Though I've got no idea how to get the RTS option to it, > >as it is called via cabal (which has --prog-options for build, but > >not for haddock?). Version is 0.8.
You should be able to pass --haddock-options to "Setup configure". > It seemed odd that the buildbot fast head for windows doesn't > have this problem, so I switched to validate and experimented some > more. The logs don't tell me which haddock is used there, but I > happened to have a haddock 0.9 somewhere - makes no difference. > > Next, I upgraded my build compiler, from 6.6.1 to 6.8.3 (which is > what the builder is using). This shouldn't affect the haddock command, > but I wanted to minimize the differences. More to the point, I also > rebuilt haddock 0.9 with ghc 6.8.3, adding -O to configure. > > And now, validate is well into tests, past haddocking ghc-6.9! OK, great. It also works fine with my self-compiled haddock 0.8, which also doesn't understand +RTS --info. Anyway, this will Just Work once we build a haddock 2 during the GHC build. > It would be useful if > +RTS --info also gave the commandline used for compilation, > or at least whether or not -O was used. Hmm, but the modules weren't necessarily all compiled with the same flags. It's probably possible to do something here, but it would require a bit of work. Thanks Ian _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
