From: Richard Jones <rich@annexia.org>
To: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Dynlink problems
Date: Tue, 29 Jul 2003 16:43:45 +0100 [thread overview]
Message-ID: <20030729154345.GA32764@redhat.com> (raw)
In-Reply-To: <20030729174830D.garrigue@kurims.kyoto-u.ac.jp>
The problem seems to be that Dynlink simply doesn't work when called
from code in a shared library (.so file).
The first problem is that Dynlink.init () causes a nasty crash - it
tries to open ("") and fails. This seems to be indicative of something
Very Bad happening in Dynlink library.
If I comment out the call to Dynlink.init (), then things just don't
work either.
Here is the smallest example I could make to demonstrate the failure:
http://www.annexia.org/tmp/dynlink-failure.tar.gz
*Please!* someone download this & tell me how to fix it. I spent much
of yesterday night trying to workaround the problems.
Rich.
--
Richard Jones. http://www.annexia.org/ http://freshmeat.net/users/rwmj
Merjis Ltd. http://www.merjis.com/ - all your business data are belong to you.
NET::FTPSERVER is a full-featured, secure, configurable, database-backed
FTP server written in Perl: http://www.annexia.org/freeware/netftpserver/
-------------------
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
next prev parent reply other threads:[~2003-07-29 15:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 9:49 Richard Jones
2003-07-28 10:07 ` Jacques Garrigue
2003-07-28 10:22 ` Nicolas Cannasse
2003-07-28 17:41 ` Richard Jones
2003-07-29 8:48 ` Jacques Garrigue
2003-07-29 15:43 ` Richard Jones [this message]
2003-07-29 16:28 ` Richard Jones
2003-07-31 17:31 ` Richard Jones
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=20030729154345.GA32764@redhat.com \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=garrigue@kurims.kyoto-u.ac.jp \
/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).