At 06.17 -0700 0-09-08, Julian Seward (Intl Vendor) wrote:
>GHC has always been written in a mixture of (more-or-less) standard C,
>along with a small amount of "Haskellised C" (.hc files). Both are
>compiled with the normal GNU tools (GCC etc), and the assembly code
>created by compiling a .hc file needs further architecture-dependent
>processing by a Perl script before it is usable.
>
>So, really, for a new platform, we need the GNU tools and perl to
>work.
Exactly what is the output after the .hs has been treated by the Perl
script, what you call "the assembly code created by compiling a .hc"? Does
it go via native (CPU-dependent) assembly code, or what?
>However, StgHugs will be replaced by GHCi, where we make GHC have an
>interactive component. This reduces the total amount of code we need
>to maintain and will give much higher compatibility between compiled and
>interpreted code that we could achieve with StgHugs.
This sounds fine. As for Mac ports, MacOS X is built up by Mach 2.5/4.4BSD,
so standrads UNIX tools ought to be available. I doubt GHC/GHCi will ever
be compiled under pre-MacOS X, it's not going to be worth the trouble.
Hans Aberg
