From: "Dominic Cooney" <dominic@dcooney.com>
To: <caml-list@yquem.inria.fr>
Subject: Mingw Ocaml-3.08.2 "Program too big to fit in memory"?
Date: Wed, 12 Jan 2005 09:46:49 +1000 [thread overview]
Message-ID: <1105487373.15665@mx68.mysite4now.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 482 bytes --]
I built Ocaml-3.08.2 with Cygwin Mingw (all downloaded today) and all of the
binaries (e.g. ocamlc.exe, ocaml.exe, ocamlopt.exe, etc.) report "Program
too big to fit in memory". All of the opt.opt binaries (e.g. ocamlc.opt,
etc.) and OcamlWin.exe seem to work fine (although OcamlWin can't spawn
ocaml.exe, of course.) The machine has 2 GB physical memory and is very
lightly loaded (page file usage is about .5 GB).
Has anybody encountered this problem?
Dominic Cooney
[-- Attachment #2: Type: text/html, Size: 2407 bytes --]
next reply other threads:[~2005-01-11 23:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 23:46 Dominic Cooney [this message]
2005-01-12 9:20 ` [Caml-list] " Frederic van der Plancke
2005-01-12 10:59 ` Dominic Cooney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1105487373.15665@mx68.mysite4now.com \
--to=dominic@dcooney.com \
--cc=caml-list@yquem.inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).