caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Drup <drupyog+caml@zoho.com>
To: Ashish Agarwal <agarwal1975@gmail.com>,  Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] inconsistent assumptions over interface
Date: Mon, 27 Apr 2015 16:53:24 +0200	[thread overview]
Message-ID: <553E4D64.5030209@zoho.com> (raw)
In-Reply-To: <CAMu2m2LjDbvjCpn6Bo+mVATOuk=c9zfLuoMwByf0+gd3FYz92A@mail.gmail.com>

According to the message, my guess is that you are trying to link a 
server file with a client library while having compiled it with the 
server library.
Since client and server libraries don't have the same type, they 
disagree over the interface.

My wild guess would be that your build script is broken.

Le 27/04/2015 16:39, Ashish Agarwal a écrit :
> The error "inconsistent assumptions over interface" has always been 
> due to a build artifact not being updated after upgrading some 
> library. Rebuilding one's files from scratch always solves the 
> problem. However, I'm in a situation where I've recompiled everything 
> from scratch many times, but I reproducibly get the error below. Does 
> anyone know what else I should look for?
>
> It's Eliom related, though I don't know why that would matter.
>
> # Error: The files ~/.opam/4.02.1/lib/eliom/client/eliom_pervasives.cmi
> #        and ../_server/foo.cmi make inconsistent assumptions
> #        over interface Eliommod_parameters
> # *** omake: targets were not rebuilt because of errors:
> #    _build/lib/_client/foo.cmi
> #       depends on: _build/lib/foo.eliom
> #    _build/lib/_client/foo.cmo
> #       depends on: _build/lib/foo.eliom
>



  reply	other threads:[~2015-04-27 14:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27 14:39 Ashish Agarwal
2015-04-27 14:53 ` Drup [this message]
2015-04-27 15:02   ` Ashish Agarwal
2015-04-27 15:02 ` Daniel Bünzli
2015-04-27 15:07   ` Ashish Agarwal
2018-04-22 14:53 [Caml-list] Inconsistent " Yann Hamdaoui
2018-04-22 15:29 ` Nicolás Ojeda Bär
2018-04-23 14:14   ` Yann Hamdaoui
2018-06-02 20:02     ` Yawar Amin

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=553E4D64.5030209@zoho.com \
    --to=drupyog+caml@zoho.com \
    --cc=agarwal1975@gmail.com \
    --cc=caml-list@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).