Hi Simon. DOC STUFF
Thanks for your suggestion: | Also, the SGMLDocWays test in the install-docs rule isn't necessary, as | far as I can tell. I suggest we remove this, and change the test in the | binary-dist rule to look at $(DOCBOOK_CATALOG) instead. I carried out those mods and built; it worked as required with no doc tools available. | Also, you committed directly to ghc-6-2-branch, which is something we | don't normally do. "Standard Practice" is to commit to the HEAD and | then merge to the branch (or put a note in the log message and I'll do | the merge). Again I've committed the change you suggested against your stated preference as I had no way of testing and possibly further modifying the HEAD etc etc before you close 6.2.1 on Monday - it also means the change gets tested on the normal build systems over the weekend. Hope you'll forgive the indiscretion on that basis - I'll try and be a better citizen in future! The diff that went in is as follows - I'll aim to put it into HEAD next week after I've tested it in that source tree: --------------------------------------------------------------------- $ cvs diff Makefile Enter passphrase for key '/home/miketh/.ssh/id_dsa': Index: Makefile =================================================================== RCS file: /home/cvs/root/fptools/Makefile,v retrieving revision 1.100.2.2 diff -r1.100.2.2 Makefile 122d121 < ifneq "$(SGMLDocWays)" "" 130d128 < endif 263c261 < ifneq "$(SGMLDocWays)" "" --- > ifneq "$(DOCBOOK_CATALOG)" "" --------------------------------------------------------------------- TEST STUFF ON WINDOWS As you're about to close for 6.2.1 I thought I'd run the regression tests in my stable test build today as well - the log should make it onto this mailing list. The network stuff has troubles - net002 in particular just hangs indefinitely (overnight in fact, until I kill explicitly) and further along the line there are a number of ghc compiler crashes which are unfortunately not reflected as such in the test log posted - I keep having to tell XP not to notify Microsoft when the crash requestor comes up. On the other hand perhaps they would kindly pass the messages on to Cambridge!? The overall test system doesn't really work on Windows (as I'm sure you're aware) due to improper handling of CR/LF line endings and improperly interpreted exit values. In other words, most of the failures are not really failures at all. Unfortunately I'm not best descibed as "Mr Perl" and the preliminary mods I've made in my local HEAD source tree (ie not yet checked in) have only slightly dented the false negatives on Windows. I do think this an area which urgently needs attention from some expert Windows Perl hacker though, as clearly there are undetected problems on Windows (at least on my particular computer). Similar comments apply to fixing the the nofib tests which are equally important in my opinion (although if memory serves there are no crashes there). Cheers Mike Thomas. _______________________________________________ Cvs-fptools mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/cvs-fptools
