From: Alain Frisch <alain@frisch.fr>
To: caml-list <caml-list@inria.fr>
Subject: [Caml-list] About the "mingw" port of OCaml
Date: Mon, 12 Dec 2011 13:10:49 +0100 [thread overview]
Message-ID: <4EE5EF49.80108@frisch.fr> (raw)
Dear caml-list,
The mingw port of OCaml was not in a good shape, because of changes in
Cygwin:
- We used to rely on the normal Cygwin gcc compiler, using the
-mno-cygwin flag. This is no longer available for recent versions
of gcc shipped in Cygwin. There is still a gcc-3.exe, but it
is not clear whether it will be supported in the future.
- There are now two modern versions of gcc, available in cygwin,
which supports compiling in "mingw" mode (32-bit mode):
* A packaged version of the compiler from the MinGW.org project:
i686-pc-mingw32-gcc.exe
* A packaged version of the compiler from the mingw-w64 project:
i686-w64-mingw32-gcc
Future versions of the OCaml mingw port should be based on one of these
two versions. I'd be interested to hear if anyone in the community has
any advice on which one to choose. Feel free to comment on this list,
or on the bug tracker:
http://caml.inria.fr/mantis/view.php?id=5179
Currently, flexdll (version 0.27) and OCaml (SVN trunk version) have
been adapted to work with the mingw-w64 version (32-bit only, for now),
but if there are arguments in favor of the other one, it should not be
difficult to switch (supporting both is not technically difficult, but
it might create useless confusion).
It would also be very useful to get some community feedback about the
current version (OCaml trunk + flexdll version 0.27).
Alain
next reply other threads:[~2011-12-12 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 12:10 Alain Frisch [this message]
2011-12-12 12:50 ` Matthieu Dubuget
2011-12-13 13:34 ` Edgar Friendly
2011-12-13 13:58 ` Gerd Stolpmann
2011-12-15 19:20 ` ygrek
[not found] ` <CAL-jcAkt7grC0z7_dVj7zD846zhHdPjWpHZZeCw_m1iEoBf4Fw@mail.gmail.com>
2011-12-15 20:52 ` Edgar Friendly
2011-12-17 21:31 ` ygrek
2011-12-19 3:10 ` Romain Beauxis
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=4EE5EF49.80108@frisch.fr \
--to=alain@frisch.fr \
--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