headless on windows
claus.reinke at talk21.com
Fri Aug 8 16:28:50 EDT 2008
>>> 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.
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!
No idea whether it was 6.8.3 or -O that made the difference,
but a difference there is (my haddock 0.8 was compiled before
+RTS --info, probably with ghc 6.6.1; my haddock 0.9 was
originally compiled with some ghc 6.9). It would be useful if
+RTS --info also gave the commandline used for compilation,
or at least whether or not -O was used.
Just waiting for the test results.. they match the builder, with the
obligatory added unexpected failure ThreadDelay001(normal).
I'm still hoping for a full head with working binary-dist, but at
least I've finally got something to work with again!-)
More information about the Cvs-ghc