From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: caml-list@inria.fr
Subject: [Caml-list] weird behavior with ocaml + mingw32 + bytecode + ssh
Date: Wed, 11 Jun 2003 09:11:35 -0400 [thread overview]
Message-ID: <20030611131135.GD9367@alan-schm1p> (raw)
Hi,
As we are porting some ocaml applications to win32, we are using the
mingw32 version of the ocaml compiler. Yesterday I noticed something
strange: when using ocaml (or ocamlc) over ssh, nothing gets printed to
the screen (for instance, 'ocamlc -h' does not give any output). Doing
so directly from the machine or using ocamlc.opt (from ssh) works fine.
I do not think this is a bug with ocaml, I suspect it is some issue with
ocamlrun (maybe the dll cannot be loaded under ssh). Has anyone seen
something like this, and where should I look to investigate ?
Thanks a lot,
Alan Schmitt
--
The hacker: someone who figured things out and made something cool happen.
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
reply other threads:[~2003-06-11 13:14 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=20030611131135.GD9367@alan-schm1p \
--to=alan.schmitt@polytechnique.org \
--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).