From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>,
cocci@systeme.lip6.fr, Julia Lawall <julia.lawall@lip6.fr>
Subject: Re: [Cocci] coccinelle issues
Date: Sun, 14 Jun 2020 08:23:23 +0200 [thread overview]
Message-ID: <1592115803.27290.33.camel@gmail.com> (raw)
In-Reply-To: <b14e6d1d-afa0-5c28-547a-9bb1a987f6fd@infradead.org>
On Sat, 2020-06-13 at 21:07 -0700, Randy Dunlap wrote:
> Hi,
>
> OK, I've not used Coccinelle and now I am trying to use it.
I've never used it either, or intend to really, but seeing that it
lives on github and more importantly, it's raining outside....
> 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 didn't download, rather pulled/built. I didn't have the same issue
you did, but make coccicheck was a bust here until I backed down to
version 1.0.6. Neither HEAD, 1.0.8 or 1.0.7 ran, and following its
MODE=blah suggestion helped not at all.
No idea if 1.0.6 will work for you, but it did for me, and doesn't take
long at all to build once you get the ocaml goop it wants installed.
Hohum, now to whack all that, and find something else to do ;-)
-Mike
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2020-06-14 7:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 4:07 [Cocci] coccinelle issues Randy Dunlap
2020-06-14 4:07 ` Randy Dunlap
2020-06-14 6:23 ` Mike Galbraith [this message]
2020-06-14 7:42 ` [Cocci] " Julia Lawall
2020-06-14 7:57 ` Mike Galbraith
2020-06-14 8:00 ` Mike Galbraith
2020-06-14 8:11 ` Mike Galbraith
2020-06-14 8:32 ` Mike Galbraith
2020-06-14 8:49 ` Julia Lawall
2020-06-14 8:47 ` Julia Lawall
2020-06-14 8:43 ` Julia Lawall
2020-06-14 8:44 ` Mike Galbraith
2020-06-14 8:51 ` Julia Lawall
2020-06-14 12:59 ` Julia Lawall
2020-06-14 18:21 ` Mike Galbraith
2020-06-14 19:37 ` Julia Lawall
2020-06-15 4:16 ` Mike Galbraith
2020-06-17 16:37 ` Randy Dunlap
2020-06-14 7:39 ` Julia Lawall
2020-06-14 7:39 ` Julia Lawall
2020-06-14 14:40 ` Randy Dunlap
2020-06-14 14:40 ` Randy Dunlap
2020-06-14 15:20 ` Julia Lawall
2020-06-14 15:20 ` Julia Lawall
-- strict thread matches above, loose matches on Subject: below --
2020-06-14 16:12 Markus Elfring
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=1592115803.27290.33.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@lip6.fr \
--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 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.