From: car@research.att.com
To: <Alain.Frisch@inria.fr>, <mff@research.att.com>
Cc: <caml-list@inria.fr>, <pdragosh@research.att.com>,
<simeon@us.ibm.com>, <yori@users.sourceforge.net>
Subject: RE: [Caml-list] Link errors with O'Caml 3.09 on MacOS
Date: Tue, 14 Feb 2006 08:24:15 -0500 [thread overview]
Message-ID: <77E42FE8D777074488824B5D4056A2FE0167BD35@NJFPSRVEXG2KCL.research.att.com> (raw)
Thanks!
I fixed the Makefile in our copy of the Camomile source and rebuilt. I
was then able to build our application with ocamlopt and the linking
errors went away.
Let's hope the Camomile developer will put this change into the standard
distribution soon.
Chris Rath
-----Original Message-----
From: Alain Frisch [mailto:Alain.Frisch@inria.fr]
Sent: Tuesday, February 14, 2006 8:00 AM
To: Fernandez,Maria F (Mary)
Cc: Caml List; Rath,Christopher A (Christopher); Dragosh,Pamela L (Pam);
Jerome Simeon; yori@users.sourceforge.net
Subject: Re: [Caml-list] Link errors with O'Caml 3.09 on MacOS
Hello again,
Actually, the patch to Camomile's Makefile is trivial. You can simply
add $(INCLUDES) to line 137:
$(OCAMLOPT) -pack -o camomile.cmx camomileconfig.cmx $(OPTOBJECTS)
(and also to line 134 for cosmetic reasons)
One could argue that OCaml should issue a proper error message when the
.cmi files are not available.
I put Camomile's developper in Cc: of this mail.
-- Alain
next reply other threads:[~2006-02-14 13:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 13:24 car [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-21 19:01 Link errors with O'Caml 3.09 and Camlidl 1.05 Kathleen Fisher
2005-11-22 11:45 ` [Caml-list] " Damien Bobillot
2005-11-23 15:17 ` [Caml-list] Link errors with O'Caml 3.09 on MacOS Mary Fernandez
2005-11-23 15:34 ` Alain Frisch
2006-02-10 13:06 ` Mary Fernandez
2006-02-14 12:52 ` Alain Frisch
2006-02-14 13:00 ` Alain Frisch
2006-02-14 14:00 ` Yoriyuki Yamagata
2006-02-14 14:25 ` Mary Fernandez
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=77E42FE8D777074488824B5D4056A2FE0167BD35@NJFPSRVEXG2KCL.research.att.com \
--to=car@research.att.com \
--cc=Alain.Frisch@inria.fr \
--cc=caml-list@inria.fr \
--cc=mff@research.att.com \
--cc=pdragosh@research.att.com \
--cc=simeon@us.ibm.com \
--cc=yori@users.sourceforge.net \
/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).