From: mstefani@redhat.com (Michael Stefaniuc)
To: cocci@systeme.lip6.fr
Subject: [Cocci] version missmatch
Date: Fri, 29 Nov 2013 13:33:47 +0100 [thread overview]
Message-ID: <529889AB.5000304@redhat.com> (raw)
In-Reply-To: <CANrVCd1UyZdJWxPc1Oahw6hNH=YL9ipLKfw39z1xXiiuiXBgHg@mail.gmail.com>
On 11/29/2013 01:07 PM, Arie Middelkoop wrote:
> What is written in the "version" file in your coccinelle dir?
> The tarball on the coccinelle website does have version rc18, so if you
> have that one, it cannot have invented rc17 out of thin air...
spatch --version returns that and it looks like it even misses a \n
sibiu:~$ spatch --version
spatch version 1.0.0-rc17 with Python support and with PCRE supportsibiu:~$
sibiu:~$ rpm -q coccinelle
coccinelle-1.0.0-0.rc18.1.fc19.x86_64
This is a common problem that spatch --version is not correct; I had
reported it this year too, afair in summer.
bye
michael
>
> Also, check the output of configure and also configure.log and scan for
> lines about python, as this gives an indication what it found.
>
> Also, Debian "jessie" has rc18 together with python 2.6.
>
> Arie
>
>
> 2013/11/29 Nicholas Mc Guire <der.herr at hofr.at <mailto:der.herr@hofr.at>>
>
>
> Hi !
>
> minor glitch in the rc18 release (or should it be rc17 ?)
> after downloading coccinelle-1.0.0-rc18.tgz unpacking and
> compile/installing it on Debian wheezy it shows up as rc17
>
> root at Xil:~# tar -xzf coccinelle-1.0.0-rc18.tgz
> root at Xil:~# cd coccinelle-1.0.0-rc18/
> root at Xil:~/coccinelle-1.0.0-rc18# ./configure --with-python
> --with-menhir
> root at Xil:~/coccinelle-1.0.0-rc18# make all
> root at Xil:~/coccinelle-1.0.0-rc18# make install
> root at Xil:~/coccinelle-1.0.0-rc18# export PATH=/usr/local/bin:$PATH
> root at Xil:~/coccinelle-1.0.0-rc18# patch --version
> root at Xilinx:/usr/src/janitor/tools/coccinelle-1.0.0-rc18#
> /usr/local/bin/spatch --version
> spatch version 1.0.0-rc17 without Python support and with Str regexp
> support roo
>
> since I never had rc17 installed I guess something went wrong with
> packaging ?
>
> also not sure why it says without python - it reported no errors
> config or
> build ?
> a make coccicheck in the kernel then complains about
> ..
> Fatal error: exception Failure("no python")
>
> any idea what is wrong with the install procedure ? (python2.6-dev and
> python3.1-dev as well as menhir is installed)
next prev parent reply other threads:[~2013-11-29 12:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 10:25 [Cocci] version missmatch Nicholas Mc Guire
2013-11-29 11:05 ` Julia Lawall
2013-11-29 12:41 ` Nicholas Mc Guire
2013-11-29 12:07 ` Arie Middelkoop
2013-11-29 12:10 ` Julia Lawall
2013-11-29 12:47 ` Nicholas Mc Guire
2013-11-29 13:21 ` Peter Senna
2013-11-29 13:55 ` Nicholas Mc Guire
2013-11-29 13:27 ` Julia Lawall
2013-11-29 12:33 ` Michael Stefaniuc [this message]
2013-11-29 12:36 ` Julia Lawall
2013-11-29 15:30 ` [Cocci] version mismatch 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=529889AB.5000304@redhat.com \
--to=mstefani@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox