From: Joe Perches <joe@perches.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Dave Hansen <dave.hansen@linux.intel.com>
Cc: bruce.w.allan@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [checkpatch.pl] runtime error by version dependency.
Date: Mon, 09 Sep 2013 08:49:20 -0700 [thread overview]
Message-ID: <1378741760.15812.2.camel@joe-AO722> (raw)
In-Reply-To: <201309092116.GAG52609.LQJOHFFtOSOMFV@I-love.SAKURA.ne.jp>
On Mon, 2013-09-09 at 21:16 +0900, Tetsuo Handa wrote:
> Hello.
>
> Commit d1fe9c09 "checkpatch: add some --strict coding style checks"
> introduced dependency on perl >= 5.10.0 .
>
> While the comment says that "Any use must be runtime checked with $^V",
> it is not runtime checked when running with perl == v5.8.4 , failing with
>
> Nested quantifiers in regex; marked by <-- HERE in m/(\((?:[^\(\)]++ <-- HERE |(?-1))*\))/ at ./scripts/checkpatch.pl line 340.
>
> error.
Hello.
See Dave Hansen's commit fab4a18a0d2bb0b90e51a945886397f1de9cb6d4
("enforce sane perl version")
[PATCH] checkpatch: enforce sane perl version
I got a bug report from a couple of users who said checkpatch.pl was
broken for them. It was erroring out on fairly random lines most commonly
with messages like:
Nested quantifiers in regex; marked by <--HERE in m/(\((?:[^\(\)]++ <-- HERE |(?-1))*\))/ at ./checkpatch.pl line 340.
The bug reporter was running a version of perl 5.8 which was end-of-lifed
in 2008: http://www.cpan.org/src/. Versions of perl this old are at
_best_ quite untested. At worst, they are crusty and known to be
completely broken.
If folks have a system _that_ old, then we should have mercy on them and
give them a half-decent error message rather than fail with nutty error
messages.
This patch enforces that checkpatch.pl is run with perl 5.10, which was
end-of-lifed in 2009. The new --ignore-perl-version command-line switch
will let folks override this if they want.
prev parent reply other threads:[~2013-09-09 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 12:16 Tetsuo Handa
2013-09-09 15:49 ` Joe Perches [this message]
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=1378741760.15812.2.camel@joe-AO722 \
--to=joe@perches.com \
--cc=bruce.w.allan@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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
all inboxes | Powered by JetHome®