caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Wojciech Meyer <wojciech.meyer@gmail.com>
To: Xavier Leroy <Xavier.Leroy@inria.fr>
Cc: Philip <feucht@uni-koblenz.de>,  caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Compile 4.01 on debian
Date: Sat, 14 Sep 2013 19:06:13 +0100	[thread overview]
Message-ID: <871u4r1dnu.fsf@gmail.com> (raw)
In-Reply-To: <52348FD2.4090702@inria.fr> (Xavier Leroy's message of "Sat, 14 Sep 2013 18:33:22 +0200")

Xavier Leroy <Xavier.Leroy@inria.fr> writes:

> On 14/09/13 17:59, Philip wrote:
>> Hi list, just pulled ocaml from git and made:
>>
>> ./configure make world.opt
>>
>> and got an error:
>>
>> Error: Files utils/ccomp.cmo and utils/misc.cmo make inconsistent
>> assumptions over interface List
>
> Sounds like you "git pull"-ed over an old working copy containing
> leftover compiled files from an earlier version of OCaml.
> "make clean" is strongly advised.
>
> (And, as others said, if you're tracking the OCaml trunk, it's at your
> own risks.)

What I do usually in such situations when "make clean" does not cleanup
everything, or some files clobber ocamlbuild hygiene conditions, is to
just use very useful git command to remember:

# git clean -dxf

this will give you a fresh repository pointing to git revision, but not
containing any intermediate files, which may affect the build.

Again, as others say, use it on your own risk, you can easily delete
some important files to you. More over the build takes significant time.
But in the end it will give you always clean repository, but you have to
reconfigure/rebuild it again yourself!

Thanks,
 Wojciech

      parent reply	other threads:[~2013-09-14 18:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-14 15:59 Philip
2013-09-14 16:23 ` Kakadu
2013-09-14 16:26 ` Adrien Nader
2013-09-14 16:35   ` Philip
2013-09-14 16:33 ` Xavier Leroy
2013-09-14 16:39   ` Philip
2013-09-14 18:06   ` Wojciech Meyer [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=871u4r1dnu.fsf@gmail.com \
    --to=wojciech.meyer@gmail.com \
    --cc=Xavier.Leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=feucht@uni-koblenz.de \
    /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).