From: Xavier Leroy <xavier.leroy@inria.fr>
To: Rolf Wester <rolf.wester@ilt.fhg.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Problem building custom toplevel
Date: Thu, 25 Jul 2002 11:16:53 +0200 [thread overview]
Message-ID: <20020725111653.B22996@pauillac.inria.fr> (raw)
In-Reply-To: <200207221608.17010.rolf.wester@ilt.fraunhofer.de>; from rolf.wester@ilt.fhg.de on Mon, Jul 22, 2002 at 04:08:16PM +0200
> I have a c++-library compiled with the icc-compiler, a c-interface to this
> library (cinterface.h and cinterface.cpp) and stubs files generated using
> camlidl (ocaml_opt.idl, ocaml_opt_stubs.cpp, ocaml_opt.ml, ocaml_opt.mli).
> I try to build a custom toplevel with:
> [...]
> but get an almost endless list of undefined references (almost 6000 lines of
> output). Here some examples:
I avoid C++ as much as I can, so this is just a wild guess. Could it
be that you're calling the wrong linker? ocamlmltop -custom performs
its linking stage by calling the C compiler that was used to build
OCaml, usually cc or gcc. (You can see exactly how the linker is
called by adding the flag -verbose.) Maybe you need to use icc as the
linker, or pass some magic flag to it telling that you're using C++
libraries. You can do that with the -cc flag, e.g.
ocamlmktop -cc "icc <whatever options>" -custom ...
Good luck,
- Xavier Leroy
-------------------
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:[~2002-07-25 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 14:08 Rolf Wester
2002-07-24 8:28 ` Alessandro Baretta
2002-07-25 9:16 ` 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=20020725111653.B22996@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=rolf.wester@ilt.fhg.de \
/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