HCoop / hcoop / debian / mlton.git / blame
| Commit | Line | Data |
|---|---|---|
| a441e504 WT |
1 | mlton for Debian |
| 2 | ---------------- | |
| 3 | ||
| 4 | NOTE TO PORTERS AND AUTOBUILDERS | |
| 5 | ||
| 6 | MLton is self-hosting, ie building MLton requires a working ML | |
| 7 | compiler, and the Makefiles assume that this is MLton itself. This | |
| 8 | means MLton build-depends upon itself. Please don't whine about this | |
| 9 | fact (eg file bugs) unless you have something constructive to suggest. | |
| 10 | ||
| 11 | You can build MLton with older versions of itself, as long as the | |
| 12 | command-line switches haven't changed too much. You can also | |
| 13 | bootstrap with SML/NJ. See the User Guide for details. | |
| 14 | ||
| 15 | It is easy enough to manually build: fetch the latest linux binary tgz | |
| 16 | from www.mlton.org, symbolic link the binaries it contains into | |
| 17 | /usr/bin/ and its library directory as /usr/lib/mlton, and you're good | |
| 18 | to go. | |
| 19 | ||
| 20 | HARDWARE REQUIREMENTS | |
| 21 | ||
| 22 | Compiling MLton requires at least 1024M of actual RAM. Thus, if your | |
| 23 | machine has less than this, it is likely that self-compilation will | |
| 24 | take a very long time due to paging. Even if you have enough memory, | |
| 25 | there simply may not be enough available, due to memory consumed by | |
| 26 | other processes. In this case, you may see an ``Out of memory'' | |
| 27 | message, or self-compilation may become extremely slow. The only fix | |
| 28 | is to make sure that enough memory is available. | |
| 29 | ||
| 30 | Now, get out there and have a MLton of fun! | |
| 31 | ||
| 32 | -- Barak Pearlmutter <bap@cs.unm.edu>, Fri, 12 Oct 2001 11:31:16 -0600 | |
| 33 | -- Stephen Weeks <sweeks@sweeks.com>, Fri, 11 Jul 2003 12:27:26 -0700 | |
| 34 | -- Wesley W. Terpstra <terpstra@debian.org>, Tue, 13 Oct 2009 03:47:12 +0200 |