caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: William Smith <bills@emu-bark.com>
To: caml-list@inria.fr, markr@raymonds.org.uk
Subject: Re: [Caml-list] Compiling OCaml on win64
Date: Sun, 17 Mar 2013 14:12:10 -0400	[thread overview]
Message-ID: <5146077A.7000009@emu-bark.com> (raw)
In-Reply-To: <000901ce2286$61eb84b0$25c28e10$@raymonds.org.uk>

Hi,

I had problems like that.   One thing that happened was that I wasn't 
using the right version of flexlink.  My Cygwin installed version 0.26 
but you need 0.29 or later

Another related problem I found was that the README.win32 says to set up 
PATH="$VCPATH:$FLPATH:$PATH"  in .msenv32. I found that the right code 
for that is PATH="$FLPATH:$VCPATH:$PATH" to help insure that you get the 
right flexlink.

Bill

On 3/16/2013 4:39 PM, Mark Raymond wrote:
> I am trying to compile OCaml 4.00.1 using MSVC 64-bit. When make tries to
> build the ocamlbuild.byte target, I get the following error:
>
> ''../ocamlcomp.sh -c -I ocamlbuild -I stdlib -o
> ocamlbuild/ocamlbuild_unix_plugin.cmo ocamlbuild/ocamlbuild_unix_plugin.ml
> File "ocamlbuild/ocamlbuild_unix_plugin.ml", line 20, characters 4-39:
> Error: Unbound module Unix
> Exit code 2 while executing this command:
>    ''../ocamlcomp.sh -c -I ocamlbuild -I stdlib -o
> ocamlbuild/ocamlbuild_unix_plugin.cmo ocamlbuild/ocamlbuild_unix_plugin.ml
> make: *** [ocamlbuild.byte] Error 2
>
> The unix files have been built in otherlibs/win32unix, but are not present
> in ocamlbuild or stdlib. All the other dependencies listed in
> ocamlbuild_unix_plugin.ml.depends are present in either ocamlbuild or
> stdlib. Any ideas?
>
>



      reply	other threads:[~2013-03-17 18:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-16 20:39 Mark Raymond
2013-03-17 18:12 ` William Smith [this message]

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=5146077A.7000009@emu-bark.com \
    --to=bills@emu-bark.com \
    --cc=caml-list@inria.fr \
    --cc=markr@raymonds.org.uk \
    /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).