incedentally, we now have various Windows nightly builds, including the test
suite, so Windows-specific breakagaes should be much less common.
right. that is at least the second time you reminded me of that. the reasons i
keep forgetting are that the old sof builds still send their daily failure
email,
whereas the buildbot only sends test summaries. could the buildbot send
a daily build summary email (one email for the latest build on all platforms
would do, just the header of the buildbot status table), with a link to the
buildbot pages, please?
also, the ghc developer wiki only indirectly refers to buildbot - a direct link
from that main page to http://darcs.haskell.org/buildbot/ might help?
Right, I quite agree, the default build/host should be mingw on Windows. I
remember looking into this at some point and concluding that it wasn't easy for
some reason (I forget exactly why). Some people (like me) have the cygwin tools
in their path and use --with-gcc to specify the path to the mingw gcc.
see my other reply. for safety, users with both cygwin and mingw gcc/ld
should get a warning about inconsistent combinations anyway, if they forget
the --with-gcc/ld and configure can't find the right versions by itself.
1. set BIN_DIST=1 in mk/build.mk
2. build as normal
3. 'make binary-dist'
cool!-) i look forward to trying it, once my build goes through. the script
prep-bin-dist-mingw looks plausible even for my older mingw, so it doesn't
seem necessary to pass gcc/perl/ld-locations from autoconf to the script
(as i was afraid it might be).
i know that ghcs tend to be in c:/ghc/*, but if that fails, perhaps you might
want to look in `ghc --print-libdir`?
thanks,
claus
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
