[MLton-user] Which MinGW version is recommended?

[Brent Fulgham]

> The upshot is that you will see this problem when bootstrapping from
> clean sources on a Cygwin machine, because the first-round compiler
> will be built with the stubs.  The easiest way I can think of to work
> around this is to edit mlton/Makefile to avoid using the stubs.
> Adding the following line after the other CM lines should do it.
> 
>   CM = $(NAME).cm
> 
> This should work fine when you're compiling the sources that come with
> the MLton binary package, since the MLton structure is the same in
> both versions, making the stubs unnecessary.

This build is even worse than before -- it segfaults when the newly-built
MLton tries to build the basis:

make[2]: Leaving directory `/cygdrive/c/fulgham/projects/mlton-20030716.orig/mlton'
/bin/cp -fpR /cygdrive/c/fulgham/projects/mlton-20030716.orig/mlton/mlton-compile /cygdrive/c/fulgham/projects/mlton-20030716.orig/build/lib/
Processing basis library.
/cygdrive/c/fulgham/projects/mlton-20030716.orig/build/lib/mlton-compile @MLton
-- /cygdrive/c/fulgham/projects/mlton-20030716.orig/basis-library /cygdrive/c/fu
lgham/projects/mlton-20030716.orig/build/lib/world
make[1]: *** [world] Segmentation fault (core dumped)
make[1]: Leaving directory `/cygdrive/c/fulgham/projects/mlton-20030716.orig'
make: *** [all] Error 2

Note:  This was done with GCC 3.2.3, so I'll try again with GCC 2.95 to see what
happens.

Also -- MLton seems to really hog system resources.  I get virtual memory complaints
from the OS when running MLton when bootstrapping.  Can this be clamped somehow to
lower the resources it uses?

Thanks,

-Brent