caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Jake Donham" <jake.donham@skydeck.com>
To: caml-list@inria.fr
Subject: camlp4 -I and shared libs
Date: Sun, 24 Jun 2007 23:33:20 -0400	[thread overview]
Message-ID: <c7e4e9f0706242033q2a9a54a1pf3f00dc011255750@mail.gmail.com> (raw)

Hi,

Should the -I flag to camlp4 add the directory to the shared library
search path, as it does with ocamlc?

I was trying to use Micmatch (very nice by the way) with ocamlfind, as follows:

  ocamlfind ocamlc -syntax camlp4o -ppopt pa_micmatch_pcre.cmo
-package micmatch_pcre [...]

but I get an error that it cannot find dllpcre.so. What is happening
is that ocamlfind has pcre-ocaml as a dependency of micmatch_pcre
(even though this is needed only at runtime, not at preprocessing
time), so it adds pcre.cma and -I $SITE_LIB/pcre to the camlp4 command
line. Now pcre.cma needs dllpcre.so, which is in $SITE_LIB/pcre, but
this path is not added to the shared library search path. (It's easy
to work around this by constructing a camlp4 call directly, since
pcre.cma is not needed.)

This is with 3.09.3 but a glance at the 3.10.0 source suggests it has
the same behavior. It's a one-line change (call Dll.add_path after
Dynlink.init in camlp4/odyl/odyl_main.ml or
camlp4/CamlP4/Struct/DynLoader.ml) to fix it.

Thanks,

Jake


             reply	other threads:[~2007-06-25  3:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25  3:33 Jake Donham [this message]
2007-06-25 12:57 ` [Caml-list] " Martin Jambon
2007-06-25 14:19   ` Nicolas Pouillard
2007-06-25 18:24     ` Jake Donham
2007-06-27  5:32       ` Jake Donham
2007-06-29  7:49     ` Hendrik Tews
2007-06-29  9:39       ` Nicolas Pouillard
2007-06-29 10:23         ` Robert Roessler
2007-06-29 10:44           ` Benedikt Grundmann
2007-06-29 14:06             ` Nicolas Pouillard
2007-06-29 12:41         ` skaller
2007-06-29 13:48           ` Nicolas Pouillard

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=c7e4e9f0706242033q2a9a54a1pf3f00dc011255750@mail.gmail.com \
    --to=jake.donham@skydeck.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).