simonpj at microsoft.com
Fri Oct 5 01:46:59 EDT 2007
| > Duncan, the error message I get is
| > Configuring bytestring-0.9...
| > Setup: Cabal was not bootstrapped correctly
| This is an error from Cabal. This is bad. We get this error when Cabal does
| know its own version number and so cannot compare its version number to the
| that the bztestring package is requesting.
| So something is going wrong building Cabal and this is being triggered with
Duncan, even if cabal is at fault, the protocol is that you should validate before committing. Currently every nightly build is failing, I think.
Can you commit a patch which stops bytestring tickling the bug, and then go back to the right thing when cabal gets fixed?
(I managed to get things working by unpulling two or three bytestring patches, but that's a bit brutal.)
Or maybe someone can fix cabal at the hackathon. But regardless, the nightly builds should not fall over.
More information about the Cvs-ghc