From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Patrick Doyle <wpdster@gmail.com>
Cc: cocci@systeme.lip6.fr, backports@vger.kernel.org
Subject: Re: [Cocci] Need help compiling coccinelle on Ubuntu 16.04
Date: Sat, 19 May 2018 08:41:00 +0200 [thread overview]
Message-ID: <5AFFC6FC.1070906@broadcom.com> (raw)
In-Reply-To: <CAF_dkJCyP-2Yc-fynAGWp5D7YZP5ybaLXrYK4EHc_Z7XSP9kiA@mail.gmail.com>
On 5/16/2018 3:48 PM, Patrick Doyle wrote:
> TherI just tried compiling coccinelle on a Ubuntu 16.04 system, having
> installed all the dependencies that seem to make sense, and it fails
> to compile.
>
> I need to use a version of spatch >= 1.0.6 for another project, and
> the version supplied with Ubuntu is 1.0.4.
>
> So I:
>
> $ git clone https://github.com/coccinelle/coccinelle.git
> $ cd coccinelle
> $ ./autogen
> $ ./configure --prefix=/home/wpd/local
> $ make
>
> and that fails with
>
> ...
> cp /usr/lib/ocaml/parmap/parmap.cmi ocaml/parmap.cmi
> cp /usr/lib/ocaml/parmap/parmap.cmx ocaml/parmap.cmx
> cp: cannot stat '/usr/lib/ocaml/parmap/parmap.cmx': No such file or directory
> Makefile:620: recipe for target 'ocaml/parmap.cmi' failed
> make: [ocaml/parmap.cmi] Error 1 (ignored)
> rm parsing_cocci/lexer_cli.ml parsing_cocci/parser_cocci_menhir.ml.d
> tools/spgen/source/spgen_lexer.ml
> parsing_cocci/parser_cocci_menhir.mli.d parsing_cocci/lexer_script.ml
> parsing_cocci/lexer_cocci.ml parsing_c/lexer_c.ml
>
> I have installed libparmap-ocaml-dev:
>
> $ apt search libparmap-ocaml-dev
> Sorting... Done
> Full Text Search... Done
> libparmap-ocaml-dev/xenial,now 1.0~rc7-1 amd64 [installed]
> small OCaml library allowing to exploit multicore architectures
>
> and /usr/lib/ocaml/parmp shows:
>
> $ ls -l /usr/lib/ocaml/parmap
> total 312
> -rw-r--r-- 1 root root 2379 Jan 18 2016 bytearray.cmi
> -rw-r--r-- 1 root root 1615 Jan 18 2016 bytearray.mli
> -rw-r--r-- 1 root root 5218 Jan 18 2016 libparmap_stubs.a
> -rw-r--r-- 1 root root 219 Jan 18 2016 META
> -rw-r--r-- 1 root root 117954 Jan 18 2016 parmap.a
> -rw-r--r-- 1 root root 27116 Jan 18 2016 parmap.cma
> -rw-r--r-- 1 root root 5814 Jan 18 2016 parmap.cmi
> -rw-r--r-- 1 root root 1898 Jan 18 2016 parmap.cmxa
> -rw-r--r-- 1 root root 106712 Jan 18 2016 parmap.cmxs
> -rw-r--r-- 1 root root 10472 Jan 18 2016 parmap.mli
> -rw-r--r-- 1 root root 906 Jan 18 2016 parmap_utils.cmi
> -rw-r--r-- 1 root root 270 Jan 18 2016 parmap_utils.mli
> -rw-r--r-- 1 root root 363 Jan 18 2016 setcore.cmi
> -rw-r--r-- 1 root root 207 Jan 18 2016 setcore.mli
>
> There are parmap.cmxa and parmap.cmxs files, but no parmap.cmx file.
>
> I am stuck here (and clearly ignorant of what I am doing). Any help
> would be appreciated.
>
> Thank you.
I found compiling it required too many stuff I did not really want on my
system. So I generally pick up recent version from launchpad:
https://launchpad.net/~npalix/+archive/ubuntu/coccinelle
Regards,
Arend
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next parent reply other threads:[~2018-05-19 6:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAF_dkJCyP-2Yc-fynAGWp5D7YZP5ybaLXrYK4EHc_Z7XSP9kiA@mail.gmail.com>
2018-05-19 6:41 ` Arend van Spriel [this message]
2018-05-19 6:47 ` [Cocci] Need help compiling coccinelle on Ubuntu 16.04 Julia Lawall
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=5AFFC6FC.1070906@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=backports@vger.kernel.org \
--cc=cocci@systeme.lip6.fr \
--cc=wpdster@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).