All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vaishali Thakkar <vthakkar1994@gmail.com>
To: Varsha Rao <rvarsha016@gmail.com>
Cc: outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] Re: Problem with coccinelle.
Date: Tue, 28 Feb 2017 17:58:42 +0530	[thread overview]
Message-ID: <CAK-LDbKHYUe_Hs79ie52FHtLFZG4rGb8kbds5EaQb2kMUEMqKA@mail.gmail.com> (raw)
In-Reply-To: <68311bc4-09a6-4baf-ab04-b0ce5916c4c9@googlegroups.com>

On Tue, Feb 28, 2017 at 4:08 PM, Varsha Rao <rvarsha016@gmail.com> wrote:
>
>> This seems likely fine.  How did you get to this situation?  Did you
>> install it from your package manager or did you compile it on your
>> machine.  When you run spatch, does it work?
>>
>    I have installed using package manager.
>    when I run spatch, it gives following errors:
>
>    spatch --sp-file ret.cocci --no-includes
> ~/git/kernels/staging/drivers/staging/most/hdm-dim2/dim2_sysfs.c  > ret.out
>
>   init_defs_builtins: /usr/lib64/coccinelle/standard.h
>   minus: parse error:
>   File "ret.cocci", line 10, column 0, charpos = 80
>   around = '',
>   whole content =

The file[ret.cocci] sent by you works perfectly fine for me without any parsing
error. Are you sure there is nothing else in the same file [ret.cocci]?

Parsing error is shown at the line 10 and file has 9 lines. Also, in your
first mail you seemed to have something else as an error. [Exception
failure]

>  [varsha@varsha coccinelle]$ spatch --sp-file ret.cocci --no-includes
> ~/git/kernels/staging/drivers/staging/most/hdm-dim2/dim2_sysfs.c  > ret.out
>  init_defs_builtins: /usr/lib64/coccinelle/standard.h
>  HANDLING:
> /home/varsha/git/kernels/staging/drivers/staging/most/hdm-dim2/dim2_sysfs.c

If you have installed coccinelle from package manager then what is under
coccinelle directory? Have you cloned coccinelle code and have tried to
install it manually as well?

>  Thanks,
>  Varsha
>
> --
> You received this message because you are subscribed to the Google Groups
> "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/outreachy-kernel/68311bc4-09a6-4baf-ab04-b0ce5916c4c9%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Vaishali
http://vaishalithakkar.in/


  reply	other threads:[~2017-02-28 12:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28  2:43 Problem with coccinelle Varsha Rao
2017-02-28  2:50 ` Varsha Rao
2017-02-28  6:48   ` [Outreachy kernel] " Julia Lawall
2017-02-28 10:38     ` Varsha Rao
2017-02-28 12:28       ` Vaishali Thakkar [this message]
2017-02-28 13:14         ` Julia Lawall
2017-02-28 13:37         ` Varsha Rao
2017-02-28  6:51 ` [Outreachy kernel] " Julia Lawall
2017-02-28 10:41   ` Varsha Rao
2017-02-28 13:53 ` Varsha Rao
2017-02-28 13:56   ` [Outreachy kernel] " Julia Lawall
2017-02-28 14:17     ` Varsha Rao
2017-02-28 14:38       ` Varsha Rao
2017-02-28 14:40         ` Julia Lawall
2017-02-28 14:39       ` Julia Lawall
2017-02-28 13:59   ` Vaishali Thakkar

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=CAK-LDbKHYUe_Hs79ie52FHtLFZG4rGb8kbds5EaQb2kMUEMqKA@mail.gmail.com \
    --to=vthakkar1994@gmail.com \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=rvarsha016@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 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.