From: Guillaume Yziquel <guillaume.yziquel@bluebottle.com>
To: "Stéphane Glondu" <steph@glondu.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Compiling recursive modules into a .cma.
Date: Tue, 21 Oct 2008 06:54:21 +0200 [thread overview]
Message-ID: <200810210455.m9L4tbf5019872@mi0.bluebottle.com> (raw)
In-Reply-To: <48FC8CE1.6020401@glondu.net>
Stéphane Glondu a écrit :
>
> It seems that chain.cmo is linked before protection.cmo inside the .cma.
> The order of modules inside of a .cma file is important. The behaviour
> is the same as if they were #loaded in the same order in a toplevel. Try
> writing explicitly all .ml files of $(SOURCE) in topological order.
Yes. Indeed. This is the problem. I was misled by the fact that
compiling things manually and in order didn't work at first, and I
believed something else was wrong, but I was mistaken.
It now works. Thanks.
Guillaume.
prev parent reply other threads:[~2008-10-21 4:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-18 15:06 Guillaume Yziquel
2008-10-20 13:51 ` [Caml-list] " Stéphane Glondu
2008-10-21 4:54 ` Guillaume Yziquel [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=200810210455.m9L4tbf5019872@mi0.bluebottle.com \
--to=guillaume.yziquel@bluebottle.com \
--cc=caml-list@inria.fr \
--cc=steph@glondu.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).