[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5596731F.20309@fau.de>
Date: Fri, 03 Jul 2015 13:33:51 +0200
From: Andreas Ruprecht <andreas.ruprecht@....de>
To: Ulf Magnusson <ulfalizer.lkml@...il.com>
CC: Paul Bolle <pebolle@...cali.nl>,
Valentin Rothberg <valentinrothberg@...il.com>,
rafael.j.wysocki@...el.com, linux-kbuild@...r.kernel.org,
Kernel Mailing List <linux-kernel@...r.kernel.org>,
hengelein Stefan <stefan.hengelein@....de>,
linux@...inikbrodowski.net
Subject: Re: Kconfig: '+config' valid syntax?
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
View attachment "zconf.l.patch" of type "text/x-patch" (786 bytes)
Powered by blists - more mailing lists