caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Pixel <pixel@mandrakesoft.com>
To: Sven Luther <sven.luther@wanadoo.fr>
Cc: stef@payrard.net, Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] dependancy problems?
Date: 06 Feb 2005 17:06:37 +0100	[thread overview]
Message-ID: <lyy8e1hdv6.fsf@leia.mandrakesoft.com> (raw)
In-Reply-To: <20050118122712.GA28131@pegasos>

Sven Luther <sven.luther@wanadoo.fr> writes:

> On Tue, Jan 18, 2005 at 09:25:22AM +0100, Stéphane Payrard wrote:

[...]

> > > > 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.
> 
> Probably yes. Or maybe just the binary compatibility problem with 3.08.1 ro
> 3.08.2 migration, so it did not hit only debian.

right, i've rebuilt LablGtk and now it works.

(sorry for the answer time)


      reply	other threads:[~2005-02-06 16:06 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   ` dependancy problems? Stéphane Payrard
2005-01-18 12:27     ` [Caml-list] " Sven Luther
2005-02-06 16:06       ` Pixel [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=lyy8e1hdv6.fsf@leia.mandrakesoft.com \
    --to=pixel@mandrakesoft.com \
    --cc=caml-list@inria.fr \
    --cc=stef@payrard.net \
    --cc=sven.luther@wanadoo.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).