Hi Ian,
But there seems to be no "Latest Successful Build" for each builder,
If someone has code to do it (without altering the code of buildbot
itself, but in master.cfg or buildbot.tac instead) then we can certainly
add it.
Otherwise, I can give it a go some time,
Thanks, that would be helpful.
but of course we have other priorities in the build-up to release.
That confuses me everytime: how can you build up for a release
without working builds?-) and, given the recent lack of working
builds, how can you prepare for a release without pointing people
on the various platforms to the most recent working build for
testing, raising issues before the upcoming branch?
If doing so automatically via buildbot is too complicated, I'm
quite willing to accept a direct recommendation from a human,
in answer to the question below:
what is the recommended procedure for getting a working
build ('make;make binary-dist') and working ghc on windows
at the moment? I'd need a version later than 07/01/08 (with
the fix for #2378).
I don't think "make binary-dist" has worked since then; fixing it is on
my list of things to do. Why is it important for you, out of interest?
If you need to have GHC on a different machine than you build it on then
can't you "make install" and then zip up the directory you install to?
'make; make binary-dist' was recommended to me many years
ago by the folks responsible for making windows snapshots as
the standard way of getting a tar-able relocatable directory full
of GHC goodness on windows, right at the top of the ghc tree
(iirc, one originally had to call some prep-bin-dist-mingw as well).
I've been happy with that procedure since then, provided the
make target isn't broken. Are you saying that has changed as
well, and I should use 'make install' instead in future? Is that
less broken right now?
Claus
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
