I suspect that is my fault, although I did validate. I will check Ian: could validate continue after a Haddock failure, and simply report it along with other test failures? That would stop a Haddock failure completely borking the validate run. Or would that be hard?
Simon | -----Original Message----- | From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Manuel M T | Chakravarty | Sent: 21 August 2008 03:20 | To: [email protected] | Subject: After enjoying a working GHC HEAD build for a few days... | | ...I know get: | | Registering ghc-6.9... | Reading package info from "dist-stage2/inplace-pkg-config" ... done. | Writing new package config file... done. | make -C compiler stage=2 doc | /Users/chak/Code/ghc-test/libraries/cabal-bin /opt/local/bin/ghc / | Users/chak/Code/ghc-test/libraries/bootstrapping.conf haddock -- | distpref dist-stage2 | Preprocessing library ghc-6.9... | Running Haddock for ghc-6.9... | dist-stage2/build/tmp/typecheck/TcGenDeriv.hs: 1300:41: Parse error | make[2]: *** [doc.stage.2] Error 1 | make[1]: *** [stage2] Error 2 | make: *** [bootstrap2] Error 2 | TacticalGrace chak 4 (.../Code/ghc-test): | | What a pity! | Manuel | | PS: This is running validate on Mac OS X. I don't care about haddock, | I just want to validate the ghc build... | | _______________________________________________ | Cvs-ghc mailing list | [email protected] | http://www.haskell.org/mailman/listinfo/cvs-ghc _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
