All of lore.kernel.org
 help / color / mirror / Atom feed
From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Compiling latest coccinelle with opensuse
Date: Tue, 13 Oct 2015 22:44:47 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1510132240590.2189@localhost6.localdomain6> (raw)
In-Reply-To: <CAB=NE6V1K8-dq7A8PNY95+hSDGOFGdL8N=kjed5CF=ABLFqWLA@mail.gmail.com>



On Tue, 13 Oct 2015, Luis R. Rodriguez wrote:

> On Tue, Oct 13, 2015 at 1:26 PM, Julia Lawall <julia.lawall@lip6.fr> wrote:
> > On Tue, 13 Oct 2015, Luis R. Rodriguez wrote:
> >
> >> I'm trying to build coccinelle to use on opensuse for a cocci file
> >> with iteration support. I'm using the latest and greatest (inria git).
> >>
> >> After ./autogen and and then configuring with --enable-release:
> >>
> >> configure flags:  --enable-release
> >> findlib:          /usr/bin/ocamlfind (an actual version is strongly recommended)
> >> menhir:           /usr/local/bin//menhir (should be an optional tool)
> >> menhirLib module: yes (for local package use --disable-menhirLib)
> >>
> >> ocaml scripting:  yes (overridable with --enable-ocaml)
> >> python scripting: yes (overridable with --enable-python)
> >> pycaml module:    local (for local package use --disable-pycaml)
> >>
> >> pcre regexes:     local (overridable with --enable-pcre-syntax)
> >> pcre module:      local (for local package use --disable-pcre)
> >> pcre library:     yes (requires the dev version of libpcre)
> >>
> >> release config:   yes (strongly recommended to be 'yes', overridable
> >> with --enable-release)
> >> optimized spatch: yes (overridable with --disable-opt)
> >>
> >> My build fails with:
> >>
> >> /usr/bin/ocamlopt.opt -unsafe -I ../commons -I ../commons/ocamlextra
> >> -I ../globals -I /usr/lib64/ocaml/menhirLib -c parser_cocci_menhir.ml
> >> File "parser_cocci_menhir.ml", line 1:
> >> Error: The files /usr/lib64/ocaml/obj.cmi
> >>        and /usr/lib64/ocaml/menhirLib/menhirLib.cmi
> >>        make inconsistent assumptions over interface Obj
> >
> > Try make clean, or make distclean.  If you had a build without ocaml, you
> > may have some old code lying around.

Ah, OK sorry, it may have nothing to do with Coccinelle.  How did you 
install menhir?  And how did you install ocaml?  It looks like there may 
be files generated by different versions of ocaml in your lib64 directory.

Could you try the following:

file /usr/lib64/ocaml/obj.cmi
file /usr/lib64/ocaml/menhirLib/menhirLib.cmi

It should tell you what version of ocaml generated the files.

julia

> Instead of 'make clean' or 'make distclean' I do:
> 
> git clean -f -x -d
> 
> Its faster than 'make clean' but caution: this will delete *anything*
> from your tree that is *not* in a git record, so watch out. Only try
> this on a repo you don't care about.
> 
> Even if I try make distclean things still fail, as suspected. I've
> tried all combination all around with distclean, clean etc.
> 
> mcgrof at ergon ~/devel/coccinelle (git::master)$ rpm -qa | grep ocaml
> ocaml-ocamldoc-4.02.3-1.1.x86_64
> ocaml-runtime-4.02.3-1.1.x86_64
> ocaml-camlp4-devel-4.02.1-1.5.x86_64
> ocaml-facile-1.1-193.6.x86_64
> ocaml-4.02.3-1.1.x86_64
> ocaml-camlp4-4.02.1-1.5.x86_64
> ocaml-findlib-1.5.5-1.6.x86_64
> ocaml-compiler-libs-4.02.3-1.1.x86_64
> 
> All these seem to be up to date.
> 
>  Luis
> 

  reply	other threads:[~2015-10-13 20:44 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13 20:19 [Cocci] Compiling latest coccinelle with opensuse Luis R. Rodriguez
2015-10-13 20:26 ` Julia Lawall
2015-10-13 20:37   ` Luis R. Rodriguez
2015-10-13 20:44     ` Julia Lawall [this message]
2015-10-13 20:49       ` Luis R. Rodriguez
2015-10-13 20:58     ` Julia Lawall
2015-10-13 21:14       ` Luis R. Rodriguez
2015-10-13 21:18         ` Julia Lawall
2015-10-13 22:05           ` Luis R. Rodriguez
2015-10-14  5:26             ` Julia Lawall
2015-10-14  7:11               ` Sébastien Hinderer
2015-10-14  7:59                 ` Julia Lawall
2015-10-14  8:53                   ` Sébastien Hinderer
2015-10-14 20:59                     ` Luis R. Rodriguez
2015-10-14 21:04                       ` Julia Lawall
2015-10-14 21:23                         ` [Cocci] Common.union_setError (was: Compiling latest coccinelle with opensuse) Luis R. Rodriguez
2015-10-14 21:32                           ` Julia Lawall
2015-10-14 21:39                             ` Luis R. Rodriguez
2015-10-14 21:47                               ` Julia Lawall
2015-10-14 21:53                                 ` Sébastien Hinderer
2015-10-14 21:44                       ` [Cocci] Compiling latest coccinelle with opensuse Sébastien Hinderer
2015-10-14 21:48                         ` Julia Lawall
2015-10-14 21:58                           ` Sébastien Hinderer
2015-10-14 10:54                 ` [Cocci] Compiling latest Coccinelle with openSUSE SF Markus Elfring
2015-10-14 14:47             ` [Cocci] Compiling latest coccinelle with opensuse Sébastien Hinderer
2015-10-14 15:22     ` [Cocci] Compiling latest Coccinelle with openSUSE SF Markus Elfring
2015-10-14 10:32 ` [Cocci] Compiling Coccinelle with specific OCaml versions on openSUSE SF Markus Elfring
2015-10-14 14:44   ` Sébastien Hinderer
2015-10-14 14:49     ` Julia Lawall
2015-10-14 14:57       ` Sébastien Hinderer
2015-10-14 15:43         ` SF Markus Elfring

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=alpine.DEB.2.02.1510132240590.2189@localhost6.localdomain6 \
    --to=julia.lawall@lip6.fr \
    --cc=cocci@systeme.lip6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.