caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: caml-list@inria.fr
Cc: Emmanuel Onzon <emmanuel.onzon@ens-lyon.fr>
Subject: Windows 64 bit Ocaml port
Date: Thu, 21 Jun 2007 16:18:56 +1000	[thread overview]
Message-ID: <1182406736.9364.255.camel@rosella.wigram> (raw)

We found building 3.10 on Windows for amd64, 64 bit code,
it was *necessary* to increase the stack size. This is done
by editing Makefile.msvc64 so you have:

NATIVECC=cl /nologo /F104857600

This could also be done for Makefile.msvc32 I think.

It may be a good idea if Inria explicitly put the /F option
in this variable with a reasonable amount of stack. RF reckons
the default is 1M which is way too small for an FPL.

[Report added to bugtracker]

-- 
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net


                 reply	other threads:[~2007-06-21  6:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1182406736.9364.255.camel@rosella.wigram \
    --to=skaller@users.sourceforge.net \
    --cc=caml-list@inria.fr \
    --cc=emmanuel.onzon@ens-lyon.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).