From: Johannes Kanig <johannes.kanig@lri.fr>
To: Pietro Abate <Pietro.Abate@pps.jussieu.fr>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Circular dependencies
Date: Mon, 6 Jul 2009 12:25:58 +0200 [thread overview]
Message-ID: <926565e50907060325o37bf41bfqb8bd6cc819af4f77@mail.gmail.com> (raw)
In-Reply-To: <20090706092704.GA20957@uranium.pps.jussieu.fr>
On Mon, Jul 6, 2009 at 11:27 AM, Pietro
Abate<Pietro.Abate@pps.jussieu.fr> wrote:
> #cat algo.mlpack
> Pub1
> Pub2
> Out
It's a bit confusing, but the mlpack has to contain all the modules of
the pack, and not only the public modules. So you should add "Private"
here. The circular dependency message is ocamlbuild's way of telling
you.
Johannes
--
Johannes Kanig
johannes.kanig@lri.fr
next prev parent reply other threads:[~2009-07-06 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 9:27 Pietro Abate
2009-07-06 10:25 ` Johannes Kanig [this message]
2009-07-06 10:56 ` [Caml-list] " Pietro Abate
2009-07-06 11:19 ` Johannes Kanig
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=926565e50907060325o37bf41bfqb8bd6cc819af4f77@mail.gmail.com \
--to=johannes.kanig@lri.fr \
--cc=Pietro.Abate@pps.jussieu.fr \
--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).