From: Andreas Ruprecht <andreas.ruprecht@fau.de>
To: Ulf Magnusson <ulfalizer.lkml@gmail.com>
Cc: Paul Bolle <pebolle@tiscali.nl>,
Valentin Rothberg <valentinrothberg@gmail.com>,
rafael.j.wysocki@intel.com, linux-kbuild@vger.kernel.org,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
hengelein Stefan <stefan.hengelein@fau.de>,
linux@dominikbrodowski.net
Subject: Re: Kconfig: '+config' valid syntax?
Date: Fri, 03 Jul 2015 13:33:51 +0200 [thread overview]
Message-ID: <5596731F.20309@fau.de> (raw)
In-Reply-To: <CAEMqcmoTHxOGRdRFMrY=kkG4HzD7vNUHVwZCsGDabGUOxhsvOQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
On 07/03/2015 12:46, Ulf Magnusson wrote:
>
> Except for scattered accidents like in the original message, which are
> hopefully pretty rare and easy to fix, the only documented thing that depends
> on that lexer sloppiness is the ---help--- "token".
>
> I'd just add "---help---" as another T_HELP alias (or get rid of it altogether,
> but that's probably more work than it's worth). Tightening things up should be
> safe after that.
>
> /Ulf
>
So we might want to do something like the attached patch, right?
Unfortunately, when I generate the zconf.{hash,lex,tab}.c files on my
machine, they have some notable differences to the _shipped versions:
ruprecht@box:linux-next$ diff -u zconf.tab.c zconf.tab.c_shipped
- return yyresult;
+ /* Make sure YYID is used. */
+ return YYID (yyresult);
and I can't find any Documentation on how to properly rebuild the
_shipped files... Does anybody have a hint on that?
Regards,
Andreas
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: zconf.l.patch --]
[-- Type: text/x-patch; name="zconf.l.patch", Size: 814 bytes --]
diff --git a/scripts/kconfig/zconf.l b/scripts/kconfig/zconf.l
index 200a3fe..84a5d05 100644
--- a/scripts/kconfig/zconf.l
+++ b/scripts/kconfig/zconf.l
@@ -106,7 +106,15 @@ n [A-Za-z0-9_]
zconflval.string = text;
return T_WORD;
}
- .
+ "---help---" {
+ /* Support old syntax for help statement */
+ return T_HELP;
+ }
+ . {
+ fprintf(stderr,
+ "%s:%d:warning: ignoring unsupported character '%c'\n",
+ zconf_curname(), zconf_lineno(), *yytext);
+ }
\n {
BEGIN(INITIAL);
current_file->lineno++;
@@ -132,7 +140,6 @@ n [A-Za-z0-9_]
BEGIN(STRING);
}
\n BEGIN(INITIAL); current_file->lineno++; return T_EOL;
- --- /* ignore */
({n}|[-/.])+ {
const struct kconf_id *id = kconf_id_lookup(yytext, yyleng);
if (id && id->flags & TF_PARAM) {
next prev parent reply other threads:[~2015-07-03 11:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 8:08 Kconfig: '+config' valid syntax? Valentin Rothberg
2015-07-02 9:01 ` Paul Bolle
2015-07-02 9:25 ` Paul Bolle
2015-07-02 11:57 ` Andreas Ruprecht
2015-07-02 12:10 ` Paul Bolle
2015-07-03 7:33 ` Andreas Ruprecht
2015-07-03 8:59 ` Paul Bolle
2015-07-03 9:29 ` Andreas Ruprecht
2015-07-03 10:46 ` Ulf Magnusson
2015-07-03 10:51 ` Valentin Rothberg
2015-07-03 10:56 ` Stefan Hengelein
2015-07-03 11:11 ` Stefan Hengelein
2015-07-03 11:34 ` Ulf Magnusson
2015-07-03 11:00 ` Paul Bolle
2015-07-03 11:33 ` Andreas Ruprecht [this message]
2015-07-03 11:40 ` Ulf Magnusson
2015-07-03 12:39 ` Ulf Magnusson
2015-07-03 12:48 ` Ulf Magnusson
2015-07-03 11:58 ` Paul Bolle
2015-07-03 10:52 ` Paul Bolle
2015-07-02 19:59 ` Rafael J. Wysocki
2015-07-03 10:16 ` Ulf Magnusson
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=5596731F.20309@fau.de \
--to=andreas.ruprecht@fau.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=pebolle@tiscali.nl \
--cc=rafael.j.wysocki@intel.com \
--cc=stefan.hengelein@fau.de \
--cc=ulfalizer.lkml@gmail.com \
--cc=valentinrothberg@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.