From: Julia Lawall <julia.lawall@inria.fr>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>, cocci@systeme.lip6.fr
Subject: Re: [Cocci] coccinelle issues
Date: Sun, 14 Jun 2020 09:39:31 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2006140932490.2849@hadrien> (raw)
In-Reply-To: <b14e6d1d-afa0-5c28-547a-9bb1a987f6fd@infradead.org>
On Sat, 13 Jun 2020, Randy Dunlap wrote:
> Hi,
>
> OK, I've not used Coccinelle and now I am trying to use it.
> It seems that I am having a few issues.
> The primary one is when I run spatch (via 'make coccicheck' in
> the kernel source tree), it tells me:
>
> Python error: No module named coccilib.elems
>
> I do see "elems.py" in /usr/local/lib64/coccinelle/python/coccilib.
>
> I am using coccinelle-master downloaded from github on
> Friday June 12, 2020.
>
>
> I have also made the following notes while building/installing it.
>
>
> Note1: The latest coccinelle tarball is not actually available
> at the coccinelle home page although the kernel documentation says it is.
Yes, I'm aware of this problem. We're not able to update the home page at
the moment. This problem is being worked on.
>
> Note2: https://github.com/coccinelle/coccinelle/blob/master/install.txt
> says that 'spatch' is a script, but it seems to be a binary executable
> file.
Actually, it is a script, and the fact that you say it is a binary may be
the reason for your python problem. Normally there is a script
(scripts/spatch) that make install puts in place that refers back to where
your Coccinelle is installed.
> Note3: https://github.com/coccinelle/coccinelle/blob/master/install.txt
> probably should say to use 'sudo make install' instead of just
> 'make install', just like 'coccinelle.rst' file in the kernel tree says.
OK. A lot of documentation for a lot of projects seems to omit the sudo,
but I have indeed never understood why.
Maybe try again with make distclean, ./autogen, ./configure, sudo make
install?
julia
>
> thanks for any help that you can provide.
>
> --
> ~Randy
>
> _______________________________________________
> Cocci mailing list
> Cocci@systeme.lip6.fr
> https://systeme.lip6.fr/mailman/listinfo/cocci
>
next prev parent reply other threads:[~2020-06-14 7:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 4:07 Randy Dunlap
2020-06-14 7:39 ` Julia Lawall [this message]
2020-06-14 14:40 ` [Cocci] " Randy Dunlap
2020-06-14 15:20 ` Julia Lawall
2020-06-14 16:12 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.22.394.2006140932490.2849@hadrien \
--to=julia.lawall@inria.fr \
--cc=cocci@systeme.lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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
all inboxes | Powered by JetHome®