From: der.herr@hofr.at (Nicholas Mc Guire)
To: cocci@systeme.lip6.fr
Subject: [Cocci] version missmatch
Date: Fri, 29 Nov 2013 14:55:59 +0100 [thread overview]
Message-ID: <20131129135559.GA26401@opentech.at> (raw)
In-Reply-To: <CA+MoWDr-CcXJ=q+VN8FUnxdYqpd7FJmESo6BZ0RpJ4apV3FfaQ@mail.gmail.com>
On Fri, 29 Nov 2013, Peter Senna wrote:
> As a "workaround", I did before running ./configure:
>
> aclocal -I m4 --install
> autoconf
>
> then:
>
> ./configure
> make all
>
> then:
>
> ./spatch --version
> spatch version 1.0.0-rc18 with Python support and with PCRE support
>
> I've tested this on Fedora 19 and Debian Wheezy. It only worked in
> Fedora. I'm trying to fix the issue, so the workaround will not be
> needed for long.
>
...before it gets complicated use brute force :)
the simples work around is to edit
configure and manually set it to rc18
PACKAGE_VERSION='1.0.0-rc18'
PACKAGE_STRING='coccinelle 1.0.0-rc18'
the build seems ok (that is make coccicheck in linux-3.12.1 is happy).
thx!
hofrat
the missing \n is here:
--- coccinelle-1.0.0-rc18/main.ml 2013-11-29 08:42:35.000000000 -0500
+++ coccinelle-1.0.0-rc18.release/main.ml 2013-08-19 04:40:12.000000000 -0
400
@@ -349,7 +349,7 @@
if !Regexp.pcre_support then "with PCRE support"
else "with Str regexp support "
in
- Printf.printf "spatch version %s %s Python support and %s\n"
+ Printf.printf "spatch version %s %s Python support and %s"
Config.version withpython whichregexp;
exit 0;
),
next prev parent reply other threads:[~2013-11-29 13:55 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 [this message]
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=20131129135559.GA26401@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 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.