Re: git version of Monday crashed on compiling self

On Thu, Jan 30, 2014 at 4:56 PM, John R. Towler <[email protected]> wrote:
> Hello,
>        I am not a subscriber.  I just had a quick error to report.  I
>         set up to build mlton from smlnj on an HP Pavillion with 2
>         Pentiums running NetBSD-6.1.3.  I messed up the pathnames a bit,
>         and after it sort of went with smlnj, I then typed gmake in the
>         mlton directory and it started a long compilation which I think
>         is what I was looking for.
>
>         I just need mlton for a hybrid logic tableau  prover set up to
>         require it.  I am not heavily involved in sml programming.
>
>         The error was an unhandled exception SysErr in the Basis library
>         compilation as far as I could tell.  It is the secondary machine
>         and not locally networked yet.  I just wanted to let someone
>         know so they could put such things on their todo lists.  There
>         was a suggestion to send email with the compilation error which
>         killed gmake.
>
>         The tar archive version from 20130705 doesn't compile.  This
>         laptop has less processor power, and when I tried it before the
>         long, background compilation locked up the machine for days.
>         This compilation with the error ran from around 7 or 8 am until
>         just a few minutes ago at 15:50 CST.  I will look to get
>         something going, and if this is an easy fix, then someone can
>         just reach in and do it.  Thanks in advance.

Sorry that you had difficulty building MLton from source.

In general, building MLton from SML/NJ isn't recommended.  A full
self-compile from a SML/NJ compiled MLton will take orders of
magnitude longer than a self-compile from a MLton compiled MLton.

We recommend at least 2GB (for a 32-bit build) or 4GB (for a 64-bit
build) of RAM to self-compile MLton.  In the past, we've also heard
that the NetBSD VM subsystem might need some tweaking for building
MLton; see http://mlton.org/RunningOnNetBSD.

If you have the compilation logs, then that would be helpful.  An
unhandled SysErr in the Basis Library might be something NetBSD
specific; or, rather, some system call behaving slightly differently
in NetBSD than in other platforms.

To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].

------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable 
security intelligence. It gives you real-time visual feedback on key
security issues and trends.  Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk