From: Robert Roessler <roessler@rftp.com>
To: Caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Undefined symbols error (Was: ocamlc vs ocamlc.opt?)
Date: Sun, 04 Feb 2007 06:08:45 -0800 [thread overview]
Message-ID: <45C5E8ED.4010409@rftp.com> (raw)
In-Reply-To: <45C45229.5030208@rftp.com>
Robert Roessler wrote:
> ...
> And libcamlrun.a is sitting right there on the command line - or at
> least an instance of this library is... OTOH, are you sure you want to
> build the DLL this way? I build the static lib with libasmrun, but
> supply the ocamlrun lib to the DLL build. Check the lib$(PACKAGE).$(A)
> and dll$(PACKAGE).$(SO) targets in the Makefile.
Ack. I am not sure if I intended to go off on a discussion of Windows
vs Linux builds, but ocamlrun.lib is used on Windows for the DLL,
while libcamlrun.a is used for the DLL (.so) on Linux.
They both use libasmrun.$(A) for their respective static lib builds.
Robert Roessler
roessler@rftp.com
http://www.rftp.com
prev parent reply other threads:[~2007-02-04 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 22:51 Nathaniel Gray
2007-02-03 9:13 ` [Caml-list] " Robert Roessler
2007-02-04 14:08 ` Robert Roessler [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=45C5E8ED.4010409@rftp.com \
--to=roessler@rftp.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).