From: "Massimiliano Brocchini" <ebrocchini@virgilio.it>
To: "Caml mailing list" <caml-list@yquem.inria.fr>
Subject: ocamlmktop 3.10 fails to link cmo files?
Date: Fri, 21 Sep 2007 16:31:54 +0200 [thread overview]
Message-ID: <89aa9c440709210731r7ff74b1as761929797ec71f5d@mail.gmail.com> (raw)
Hi all,
I tried to make a custom top level using ocamlmktop (ocaml 3.10). I
tried several approaches but I wasn't able to correctly link cmo files
not belonging to the standard library.
e.g. ocamlmktop -I /home/massimiliano/ocaml_code/sequence/
sequence.cmo -o mytop
gives no error and build mytop
but in mytop open Sequence fails reporting an unbound module
while
ocaml -I /home/massimiliano/ocaml_code/sequence/ sequence.cmo
works as expected and allows me to open the module.
Am I doing something wrong or is it a bug?
Ciao, Massimiliano Brocchini
next reply other threads:[~2007-09-21 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 14:31 Massimiliano Brocchini [this message]
2007-09-21 15:18 ` [Caml-list] " Julien Moutinho
2007-09-21 15:37 ` Massimiliano Brocchini
2007-09-21 15:38 ` Massimiliano Brocchini
2007-09-21 15:56 ` Julien Moutinho
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=89aa9c440709210731r7ff74b1as761929797ec71f5d@mail.gmail.com \
--to=ebrocchini@virgilio.it \
--cc=caml-list@yquem.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).