From: Ranjan Bagchi <ranjan@frotz.com>
To: Richard Jones <rich@annexia.org>
Cc: caml-list@inria.fr
Subject: [Caml-list] Re: ocamlc -linkall: problems with external functions?
Date: Tue, 24 Feb 2004 10:01:50 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0402240958440.16980@manjula.frotz.bogus> (raw)
In-Reply-To: <20040224083544.GA13071@redhat.com>
Rich,
Looks more or less identical:
$ ocamlc -linkall -custom -g -w s -I /usr/lib/ocaml/3.07/pcre -verbose dynlink.cma str.cma pcre.cma unix.cma dbi.cmo apache.cmo mod_caml_config.cmo mod_caml.cmo cgi.cmo apache_c.o wrappers.o dummy.o -o mod_caml_executable
+ gcc -Wl,-E -o 'mod_caml_executable' -I'/usr/lib/ocaml/3.07' /tmp/camlprim3a1c34.c '-L/usr/lib/ocaml/3.07/pcre' '-L/usr/lib/ocaml/3.07' '-lunix' '-lpcre_stubs' '-lpcre' '-lstr' 'apache_c.o' 'wrappers.o' 'dummy.o' -lcamlrun -lm -ldl -lcurses -lpthread
$ ocamlc -custom -g -w s -I /usr/lib/ocaml/3.07/pcre -verbose dynlink.cma str.cma pcre.cma unix.cma dbi.cmo apache.cmo mod_caml_config.cmo mod_caml.cmo cgi.cmo apache_c.o wrappers.o dummy.o -o mod_caml_executable
+ gcc -Wl,-E -o 'mod_caml_executable' -I'/usr/lib/ocaml/3.07' /tmp/camlprimcecba1.c '-L/usr/lib/ocaml/3.07/pcre' '-L/usr/lib/ocaml/3.07' '-lunix' '-lpcre_stubs' '-lpcre' '-lstr' 'apache_c.o' 'wrappers.o' 'dummy.o' -lcamlrun -lm -ldl -lcurses -lpthread
I'll check out what Vlad had done.
Ranjan
On Tue, 24 Feb 2004, Richard Jones wrote:
> On Mon, Feb 23, 2004 at 10:37:45PM -0800, Ranjan Bagchi wrote:
> > 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'
>
> I'm guessing that this is something to do with the link order ...?
>
> You could try adding the -verbose option to ocamlc which should
> display the actual commands it is executing.
>
> > (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)
>
> Hopefully I'm going to be able to fix some of this soon ... by using
> the same tricks that Vlad Seryakov uses in his AOLServer/caml program
> (see an earlier posting on caml-list).
>
> Rich.
>
> --
> Richard Jones. http://www.annexia.org/ http://www.j-london.com/
> Merjis Ltd. http://www.merjis.com/ - improving website return on investment
> http://www.YouUnlimited.co.uk/ - management courses
>
>
-------------------
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
prev parent reply other threads:[~2004-02-24 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 6:37 [Caml-list] " Ranjan Bagchi
2004-02-24 8:35 ` [Caml-list] " Richard Jones
2004-02-24 18:01 ` Ranjan Bagchi [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=Pine.LNX.4.58.0402240958440.16980@manjula.frotz.bogus \
--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