After applying any conceivable patch in this mailing list, ghc-2.05
built (almost) fine on our Linux- and HP-boxes. A few glitches:

   * As usual, /tmp is much too small on our machines. The hints from
     installing.lit:

        The quickest way around it is \tr{setenv TMPDIR /usr/tmp} or
        even \tr{setenv TMPDIR .} (or the equivalent incantation with the
        shell of your choice).

        The best way around it is to say
           \begin{verbatim}
             TMPDIR=<dir>
           \end{verbatim}
        in your @build.mk@ file.

     But either way, that doesn't do the right thing: Setting TMPDIR
     seems to be ignored during the compilation of ghc-2.05 (the
     compilation log contains some "TMPDIR=/tmp; export TMPDIR; ..."
     lines). Hacking config.mk permanently sets TMPDIR in the installed
     ghc driver script. But having my personal ~/tmp being compiled in
     isn't a very cunning plan (to use Baldrick's words... :-)
     In a rare glimpse of ingenuity  ;-) , I tried "make TMPDIR=~/tmp all",
     which seems to work. Perhaps the docs and/or Makefiles need some
     fine-tuning here.
     
   * fptools/ghc/lib/cbits/timezone.h is a show-stopper again: On
     Linux (and any other sensible OS, I presume), the type of timezone
     is time_t. But @#$%&! HP-UX-10.20 thinks it's long. This should
     better be figured out by configure. (I think I've mailed this
     already somtime ago, but anyway...)

To share my happiness with others, I make the usual unofficial snapshots
available at

   
ftp://ftp.informatik.uni-muenchen.de/local/pms/ghc-2.05-all-i386-unknown-linux.tar.gz
   ftp://ftp.informatik.uni-muenchen.de/local/pms/ghc-2.05-all-hppa1.1-hp-hpux10.tar.gz

this afternoon. Unpack at / and enjoy...

Some questions:

   * What is this funny object-splitting all about? It seems to blow up
     a 2Mb object file into hundreds of smaller object files, using
     almost 30MB altogether!?

   * I'd like to hear some success stories about booting ghc-2.05 with
     itself, especially compiler/library size/speed.

   * What's the schedule for porting Haggis to ghc-2.x-compliant code?
     (Standard Haskell code would be even better. :-))
     Up to now, one has the options of writing Ancient Haskell
     (= ghc-0.2x code) or giving up the nice GUI stuff.

Sven "device full" Panne

-- 
Sven Panne                                        Tel.: +49/89/2178-2235
LMU, Institut fuer Informatik                     FAX : +49/89/2178-2211
LFE Programmier- und Modellierungssprachen              Oettingenstr. 67
mailto:[EMAIL PROTECTED]            D-80538 Muenchen
http://www.pms.informatik.uni-muenchen.de/mitarbeiter/panne

Reply via email to