From: "Nicolás Ojeda Bär" <nicolas.ojeda.bar@lexifi.com>
To: Per Larsson <per.larsson@prover.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] ocaml on cygwin64
Date: Sun, 30 Jun 2019 18:22:48 +0000 [thread overview]
Message-ID: <CADK7aFNgpL62EQsSZgh7V05yf9Jg5XaVuL9r4QJm7dkkXNfdkw@mail.gmail.com> (raw)
In-Reply-To: <AM0PR08MB3554076588FF2C8A4BC5C9D88EFE0@AM0PR08MB3554.eurprd08.prod.outlook.com>
Dear Per,
I think it will be easier for people to help you if you provide more
details about the problems you are facing, such as what errors are you
getting, reproduction steps, etc.
As far as I know, the cygwin port of OCaml is not abandoned and there
are no plans to do so.
Best wishes,
Nicolás
On Sun, Jun 30, 2019 at 2:15 PM Per Larsson <per.larsson@prover.com> wrote:
>
> We have standardized on the cygwin (64-bit) platform at my workplace. The latest version of ocaml available for this platform in the cygwin-package tool is 4.04.2. This is also the latest version which has worked without problems for me. Later versions can be be installed using opam, but as soon one tries to use the compile suit or install extra libraries with opam there are problems connected to loading shared libraries. Some googling gives that there is a problem concerning flexdll/flexlink causing this. I hope someone can give me more information on this. Is the cygwin64 platform presently abandoned or is this worked on or planned to be fixed in some future version (which) ? Is there a plan to update the version at the cygwin package tool soon?
prev parent reply other threads:[~2019-06-30 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-30 12:15 Per Larsson
2019-06-30 18:22 ` Nicolás Ojeda Bär [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=CADK7aFNgpL62EQsSZgh7V05yf9Jg5XaVuL9r4QJm7dkkXNfdkw@mail.gmail.com \
--to=nicolas.ojeda.bar@lexifi.com \
--cc=caml-list@inria.fr \
--cc=per.larsson@prover.com \
/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).