From: Ranjan Bagchi <ranjan@frotz.com>
To: caml-list@inria.fr
Cc: Richard Jones <rich@annexia.org>
Subject: [Caml-list] ocamlc -linkall: problems with external functions?
Date: Mon, 23 Feb 2004 22:37:45 -0800 [thread overview]
Message-ID: <403AF139.7030303@frotz.com> (raw)
Hi --
I'm experimenting with mod_caml 1.0.6 (which is very cool, thanks Rich),
and I've found something interesting (this may be an ocaml thing, a
mod_caml thing, or an apache thing since it intersects):
The following line in the Makefile:
mod_caml_executable: $(ALL_CMOS) apache_c.o wrappers.o dummy.o
$(OCAMLC) -custom $(OCAMLCFLAGS) $(ALL_CMAS) $^ -o $@
if changed to
mod_caml_executable: $(ALL_CMOS) apache_c.o wrappers.o dummy.o
$(OCAMLC) -linkall -custom $(OCAMLCFLAGS) $(ALL_CMAS) $^ -o $@
results in the very strange startup error (when doing
/usr/sbin/apachectl start):
Fatal error: unknown C primitive `pcre_get_match_limit_wrapper'
However, in both mod_caml_executables, nm | grep
pcre_get_match_limit_wrapper results in
080571a0 T pcre_get_match_limit_wrapper
Is this a bug? What's happening? Is there a workaround?
Thanks,
Ranjan
(PS -- why I'm doing this. I'm trying to load into the executable the
rpc library. The reason why is that Dynlink seems to really dislike
loading -- at run time -- the rpc.cma and equeue.cma libraries.
However, I've found that building an executable with --linkall produces
a system that Dynlink can use to load in code building **using** rpc:
stub modules, etc)
-------------------
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 reply other threads:[~2004-02-24 6:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 6:37 Ranjan Bagchi [this message]
2004-02-24 8:35 ` [Caml-list] " Richard Jones
2004-02-24 18:01 ` Ranjan Bagchi
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=403AF139.7030303@frotz.com \
--to=ranjan@frotz.com \
--cc=caml-list@inria.fr \
--cc=rich@annexia.org \
/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