[darcs-users] Windows build error (due to ifdef juggling?)
kowey at darcs.net
Fri Mar 13 09:33:45 UTC 2009
On Mon, Mar 09, 2009 at 11:46:06 +0000, Duncan Coutts wrote:
> By the way, can I recommend that your build slaves use -v for the
> configure and build steps. In general it makes diagnosis much easier.
> For example I could see what flags were selected, what versions of libs
> are in use, what version of Cabal and ghc are being used etc etc.
Thanks to Zooko's help, we've got the Windows build slave past the cabal
configure step and are now back to this original problem.
Here is the cabal configure --verbose output:
(note zlib=False; we had simplified the flags to get rid of 'external-')
And the build error:
Phew! We're slowly unpopping the stack! Once we get this licked, we
still have test failures on the Windows slave to look at. Stack:
-lz build error <-- we are here
Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow>
PGP Key ID: 08AC04F9
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: Digital signature
More information about the darcs-users