From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Hugues CASSE <casse@irit.fr>, CAML <caml-list@inria.fr>
Subject: Re: Error whith DynLink module
Date: Tue, 9 Mar 1999 15:42:48 +0100 [thread overview]
Message-ID: <19990309154248.34853@pauillac.inria.fr> (raw)
In-Reply-To: <36DE5A47.6E0C@irit.fr>; from Hugues CASSE on Thu, Mar 04, 1999 at 11:02:47AM +0100
> let load_prog name =
> Dynlink.init ();
> print_endline "OK !"; flush stdout;
> Dynlink.add_interfaces
> ["Syntax"]
> [...]
> with Dynlink.Error err ->
> print_endline (Dynlink.error_message err); false
>
> Zhen I execute the program, I get the following output...
>
> OK !
> KO !
> no implementation available for Digest
>
> Can somenody help me ?
What about adding "Digest" to your call to Dynlink.add_interfaces?
Dynlink.add_interfaces ["Syntax"; "Digest"; ...] ...
Actually, you should add all standard library modules that the
dynamically-linked module might need, e.g. Pervasives, String, Char,
List, etc.
Yes, it is a pain to list them all, but for dynamic linking of
untrusted code in a secure environment (the initial application of
Dynlink), it must be done this way.
Hope this helps,
- Xavier Leroy
prev parent reply other threads:[~1999-03-10 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-04 10:02 Hugues CASSE
1999-03-09 14:42 ` Xavier Leroy [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=19990309154248.34853@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=casse@irit.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