From: Dave Berry <dave@kal.com>
To: Mattias Waldau <mattias.waldau@abc.se>,
wester@ilt.fhg.de, caml-list@inria.fr
Subject: RE: [Caml-list] Cygwin ocaml crashes
Date: Mon, 23 Apr 2001 17:49:50 +0100 [thread overview]
Message-ID: <3145774E67D8D111BE6E00C0DF418B6641348C@nt.kal.com> (raw)
My experience of Cygwin, when working at Harlequin, is that it was very
flakey. New versions would fix earlier bugs but introduce new ones, and
versions would be incompatible. I was rather hoping that this would have
improved by now. We ended up keeping a known working version stored
locally, and always using that, if necessary patching it ourselves.
Fortunately this was all for internal tools, and we never had to worry about
distributing them.
Is it possible for INRIA to distribute the exact version of Cygwin needed
for OCaml? I remember Cygwin having fairly nasty licensing restrictions.
-----Original Message-----
From: Mattias Waldau [mailto:mattias.waldau@abc.se]
Sent: Monday, April 23, 2001 16:59
I didn't get that kind of behaviour using the pre 3.01 cygwin-versions.
Maybe the error isn't that you need the latest cygwin,
but the same cygwin that was used to build ocaml. (I used the
binary installs.)
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next reply other threads:[~2001-04-23 16:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 16:49 Dave Berry [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-23 10:05 wester
2001-04-23 13:49 ` Alan Schmitt
2001-04-23 14:16 ` wester
2001-04-23 15:39 ` Alan Schmitt
2001-04-23 15:59 ` Mattias Waldau
2001-04-24 7:00 ` wester
2001-04-24 7:44 ` Alan Schmitt
2001-04-24 20:52 ` Mattias Waldau
2001-04-25 10:02 ` Christophe Macabiau
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=3145774E67D8D111BE6E00C0DF418B6641348C@nt.kal.com \
--to=dave@kal.com \
--cc=caml-list@inria.fr \
--cc=mattias.waldau@abc.se \
--cc=wester@ilt.fhg.de \
/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).