From: der.herr@hofr.at (Nicholas Mc Guire)
To: cocci@systeme.lip6.fr
Subject: [Cocci] version missmatch
Date: Fri, 29 Nov 2013 13:41:16 +0100 [thread overview]
Message-ID: <20131129124116.GA31818@opentech.at> (raw)
In-Reply-To: <alpine.DEB.2.10.1311291202080.2088@hadrien>
On Fri, 29 Nov 2013, Julia Lawall wrote:
> On Fri, 29 Nov 2013, Nicholas Mc Guire wrote:
>
> >
> > 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)
>
> Unfortunately, I understand almost nothing about the build system :(
>
well if a Debian specific requirements/download/compile/install/running
instruction would be usefull for the manual to fill in chapter 2 let me know
> I will try to be sure that for the next release the name that Coccinelle
> is given matches the name that it actually is...
>
> For python, I'm not sure. Where is python located on your machine? I see
> some mentions of python2.7 instead of python2.6. Maybe you need that
> version?
>
python 2.6 seems fine - the problem was that it depends on pkg-config and
for python2.6 there was no package config file in /usr/lib/pkgconfig/ - bute
force solution isntall python 3.1 (which comes with a valid .pc file)
copy python-3.1.pc to python-2.6.pc and fix it up manually (its only a
few lines) then rebuild coccinelle with
./configure --with-python --enable-python --enable-pycaml
and that gives me
root at Xil:~/tools/coccinelle-1.0.0-rc18# spatch --version
spatch version 1.0.0-rc17 with Python support and with Str regexp support root at X
since make coccicheck works again in the kernel I guess its fine.
thx!
hofrat
next prev parent reply other threads:[~2013-11-29 12:41 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 [this message]
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
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=20131129124116.GA31818@opentech.at \
--to=der.herr@hofr.at \
--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