From: "Stéphane Payrard" <stef@payrard.net>
To: Ocaml <caml-list@inria.fr>
Cc: pixel@mandrakesoft.com
Subject: dependancy problems?
Date: Tue, 18 Jan 2005 09:25:22 +0100 [thread overview]
Message-ID: <20050118082522.GB8298@cachan-2-82-67-232-89.fbx.proxad.net> (raw)
In-Reply-To: <200501180809.15056.jon@jdh30.plus.com>
Hi,
note to pixel: you are in copy because you may be interested.
On Tue, Jan 18, 2005 at 08:09:14AM +0000, Jon Harrop wrote:
> On Tuesday 18 January 2005 07:33, Stéphane Payrard wrote:
> > Hi,
> >
> > I am an ocaml beginner and I try to compile the last snapshot of
> > cameleon. I am using mandrake with the following rpms:
> > ocaml-lablgtk-1.2.7-1mdk
> > ocaml-3.08.2-1mdk
> >
> > I get the following message when trying to compile:
> >
> > Files /usr/lib/ocaml/lablgtk/gtkThread.cmx
> > and /usr/lib/ocaml/threads/threads.cmxa
> > make inconsistent assumptions over implementation Thread
> >
> > Should I use different versiosn of either lablgtk or ocaml?
> > The INSTALL file suggest OCaml 3.07 and LablGtk 1.2.6 .
> > Or is there an easy way to tweak cameleon to get it to compile
> > with the ocaml and lablgtk versions I have.
>
> I think this problem is due to different ocaml versions being used to generate
> lablgtk and threads.
Does this mean that the mandrake people have not done a proper job
about dependancies? I have installed unison that also uses
lablgtk. There is no problem there. So I am puzzled.
>
> Interfaces between OCaml compilation units are *very* brittle. This is being
> discussed on the list at the moment, as even a minor version change of the
> compiler (e.g. 3.08.2 -> 3.08.3) breaks compatibility.
Naive question: is this due to some internal layout of compiled structures like
classe vtables in C++? Or is this just because modules are updated and
their signature change?
>
> The good news is that this binary incompatibility is because the compiler is
> very pedantic about interfaces and guarantees that everything will work.
>
> Your best bet is either to compile all of the packages yourself or to use
> someone else's packages. I find Debian to be excellent in this
> respect.
>
> Cheers,
> Jon.
>
> PS: 3.08 has some useful additions which you may well find that people use in
> their code now (e.g. immediate objects).
>
Thx for you help.
--
stef
next prev parent reply other threads:[~2005-01-18 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 7:33 Stéphane Payrard
2005-01-18 8:09 ` [Caml-list] (no subject) Jon Harrop
2005-01-18 8:25 ` Stéphane Payrard [this message]
2005-01-18 12:27 ` [Caml-list] dependancy problems? Sven Luther
2005-02-06 16:06 ` Pixel
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=20050118082522.GB8298@cachan-2-82-67-232-89.fbx.proxad.net \
--to=stef@payrard.net \
--cc=caml-list@inria.fr \
--cc=pixel@mandrakesoft.com \
/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).