caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David Allsopp <dra-news@metastack.com>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] OCaml installer on Windows no longer installs MinGW?
Date: Mon, 15 Jul 2013 12:21:22 +0000	[thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D9CC91F268@Remus.metastack.local> (raw)
In-Reply-To: <51E3E70F.9010202@inria.fr>

Romain Bardou wrote:
> I just installed OCaml from http://protz.github.io/ocaml-installer/ on a
> fresh Windows 7 32bit installation, in VirtualBox, and run into several
> problems.

I haven't yet got around to trying this installer out, though I think it is being actively maintained.

However...

> During Cryptokit compilation...
> 
> - The configure step returned no error although it should have (see
> below).
> 
> - It failed to compile because it could not find i686-w64-mingw32-gcc.
>   Apparently it was not installed by the OCaml installer.
> 
> - I found no way to specify the GCC executable name during the "setup.ml -
> configure" step. Can OASIS handle this?

If correctly configured, you shouldn't need to do this - OCaml itself should know it. I believe that OASIS compiles .c files the "correct" way (i.e. using ocamlopt which itself calls the correct gcc).

> - I installed the Cygwin packages mingw64-i686-gcc and mingw64-i686-
> headers myself.
>   Then, compiling Cryptokit failed: ocamlmklib raised End_of_file while
> trying to read libmoldname.a, which happens to be 8 bytes long.

I don't think it's related, but I use the following patch for Cryptokit (based on info from Sylvain):

diff -Naur cryptokit-1.7/myocamlbuild.ml cryptokit-1.7/myocamlbuild.ml
--- cryptokit-1.7/myocamlbuild.ml	2011-06-23 18:57:04.000000000 +0100
+++ cryptokit-1.7/myocamlbuild.ml	2011-08-12 16:01:55.867588300 +0100
@@ -473,7 +473,7 @@
             [
                (OASISExpr.EBool true, S []);
                (OASISExpr.EFlag "zlib",
-                 S [A "-ccopt"; A "-O"; A "-ccopt"; A "-DHAVE_ZLIB"])
+                 S [A "-ccopt"; A "-O"; A "-ccopt"; A "-DHAVE_ZLIB"; A "-ccopt"; A "-LC:/Dev/OCaml/lib"])
             ]);
           (["oasis_library_cryptokit_cclib"; "link"],
             [
@@ -483,7 +483,7 @@
           (["oasis_library_cryptokit_cclib"; "ocamlmklib"; "c"],
             [
                (OASISExpr.EBool true, S []);
-               (OASISExpr.EFlag "zlib", S [A "-lz"])
+               (OASISExpr.EFlag "zlib", S [A "-LC:/Dev/OCaml/lib"; A "-lz"])
             ])
        ];
      }

But that's simply to pass a link directory for zlib. With that patch, I have no problems running:

ocaml setup.ml -configure --enable-zlib
ocaml setup.ml -build
ocaml setup.ml -doc
ocaml setup.ml -install

And it does seem to work.

HTH,


David

  reply	other threads:[~2013-07-15 12:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 12:11 Romain Bardou
2013-07-15 12:21 ` David Allsopp [this message]
2013-07-15 12:22 ` Matthieu Dubuget
2013-07-15 12:37   ` Romain Bardou
2013-07-15 12:42     ` Matthieu Dubuget
     [not found] ` <51E3E975.7020708@gmail.com>
2013-07-15 12:39   ` Matthieu Dubuget
2013-07-15 14:16     ` Romain Bardou
2013-07-15 15:34       ` Jonathan Protzenko
2013-07-15 15:59         ` Romain Bardou

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=E51C5B015DBD1348A1D85763337FB6D9CC91F268@Remus.metastack.local \
    --to=dra-news@metastack.com \
    --cc=caml-list@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).