From: "David Allsopp" <dra-news@metastack.com>
To: "OCaml List" <caml-list@inria.fr>
Subject: [Caml-list] ocaml-ssl on Windows
Date: Tue, 2 Aug 2011 14:34:49 +0100 [thread overview]
Message-ID: <000401cc5118$f4499630$dcdcc290$@metastack.com> (raw)
It took a bit of fighting, but I managed to persuade ocaml-ssl 0.4.4 to
compile with OCaml 3.12.0 using MinGW against a MinGW build of openssl
1.0.0d.
The problem is that I get an Ssl.Connection_error Ssl.Error_syscall
exception from Ssl.open_connection no matter what server I use. I can tell
with a protocol analyser that a connection is made to the given server and a
small amount of traffic is exchanged before the exception is raised.
Has anyone else managed to get ocaml-ssl working on Windows and, if so,
might they offer any pointers? OpenSSL doesn't seem to offer any kind of
clue either to aid debugging further.
Connecting to the same server works using openssl s_client (and the build of
openssl passed everything in make test)
TIA,
David
reply other threads:[~2011-08-02 13:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000401cc5118$f4499630$dcdcc290$@metastack.com' \
--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).