All of lore.kernel.org
 help / color / mirror / Atom feed
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Spatch fail on v1.0.2
Date: Wed, 9 Sep 2015 22:51:04 +0200	[thread overview]
Message-ID: <55F09BB8.3010701@users.sourceforge.net> (raw)
In-Reply-To: <CAB3z_Rqaiz1f9TLbpwjU0kZ2yJKKAK-CBdkD8oOQAcLWyA0FRw@mail.gmail.com>

> Spatch available at: https://gist.github.com/kbingham/96477177dd20a72b1c2f
> 
> Run it on a linux kernel tree:
> 
> with spatch v.1.0.2 I get the following:
> 
> kbingham at CookieMonster:/opt/projects/linaro/hikey/kernel$ spatch
> --linux-spacing --sp-file patches/i2c-dt.cocci . --in-place
> init_defs_builtins: /home/kbingham/.opam/system/lib/coccinelle/standard.h
> 1115 1116
> Fatal error: exception Failure("plus: parse error:
>  = File "patches/i2c-dt.cocci", line 66, column 1,  charpos = 1115
>     around = ')', whole content =       )
> ")
> kbingham at CookieMonster:/opt/projects/linaro/hikey/kernel$ spatch --version
> spatch version 1.0.2 with Python support and with PCRE support
> 
> 
> However, re-installing v.1.0.0 executes fine:
> 
> kbingham at CookieMonster:/opt/projects/linaro/hikey/kernel$ spatch --version
> spatch version 1.0.0-rc22 with Python support and with PCRE support

You show another interesting version comparison.

I suggest to be a bit more careful when you try this tool out installed
in a few directories in parallel.
I would expect that the command calls should reference a directory explicitly
so that potential misunderstanding can be avoided.

Do you eventually use separate test systems for the development
of semantic patch scripts?

Regards,
Markus

  parent reply	other threads:[~2015-09-09 20:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-09 18:57 [Cocci] Spatch fail on v1.0.2 Kieran Bingham
2015-09-09 19:05 ` Julia Lawall
2015-09-09 19:11   ` Kieran Bingham
2015-09-09 19:14     ` Julia Lawall
2015-09-09 20:51 ` SF Markus Elfring [this message]
2015-09-11 10:47   ` Kieran Bingham
2015-09-11 10:56     ` 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=55F09BB8.3010701@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --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.