public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Jan Beulich <JBeulich@suse.com>
Cc: linux-kbuild@vger.kernel.org, yann.morin.1998@free.fr
Subject: Re: [PATCH 1/2] kconfig: don't silently ignore unhandled characters
Date: Tue, 04 Nov 2014 15:06:46 +0100	[thread overview]
Message-ID: <1415110006.20372.165.camel@x220> (raw)
In-Reply-To: <5458A4FC0200007800044AC1@mail.emea.novell.com>

On Tue, 2014-11-04 at 09:05 +0000, Jan Beulich wrote:
> At the very least we should tell people that waht they wrote is not
> what the utility understands.

Yes, we should change this. I'm inclined to think the should die with an
error on invalid syntax. Would that be too strict?  

Anyhow, seems to work as advertised:
    $ make ARCH=arm menuconfig
    [...]
    sound/soc/intel/Kconfig:40:warning: ignoring unsupported character '\'
    sound/soc/intel/Kconfig:70:warning: ignoring unsupported character '\'
    arch/arm/Kconfig.debug:1268:warning: ignoring unsupported character '>'

The soc/intel warnings are for doubled line continuations! You've earned
a Reported-by:, I guess.

> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> ---
>  scripts/kconfig/zconf.l             |    6 -
>  scripts/kconfig/zconf.lex.c_shipped |  194 +++++++++++++++++++-----------------
>  2 files changed, 111 insertions(+), 89 deletions(-)
> 
> --- 3.18-rc3-kconfig.orig/scripts/kconfig/zconf.l
> +++ 3.18-rc3-kconfig/scripts/kconfig/zconf.l
> @@ -141,7 +141,11 @@ n	[A-Za-z0-9_]
>  	}
>  	#.*	/* comment */
>  	\\\n	current_file->lineno++;
> -	.
> +	[[:blank:]]+
> +	.	{
> +		printf("%s:%d:warning: ignoring unsupported character '%c'\n",

                 fprintf(stderr, [...]?

> +		       zconf_curname(), zconf_lineno(), *yytext);
> +	}
>  	<<EOF>> {
>  		BEGIN(INITIAL);
>  	}
> --- 3.18-rc3-kconfig.orig/scripts/kconfig/zconf.lex.c_shipped
> +++ 3.18-rc3-kconfig/scripts/kconfig/zconf.lex.c_shipped
> @@ -414,14 +414,14 @@ static yyconst flex_int16_t yy_nxt[][17]
>      },
>  
>      {
> -       11,   26,   26,   27,   28,   29,   30,   31,   29,   32,
> -       33,   34,   35,   35,   36,   37,   38
> +       11,   26,   27,   28,   29,   30,   31,   32,   30,   33,
> +       34,   35,   36,   36,   37,   38,   39
>  
>      },
>  
>      {
> -       11,   26,   26,   27,   28,   29,   30,   31,   29,   32,
> -       33,   34,   35,   35,   36,   37,   38
> +       11,   26,   27,   28,   29,   30,   31,   32,   30,   33,
> +       34,   35,   36,   36,   37,   38,   39
>      },
>  
>      {

I guess we must trust that you manually edited this _shipped file
correctly.

>[...]
> @@ -920,7 +931,7 @@ static int input (void );
>  /* This used to be an fputs(), but since the string might contain NUL's,
>   * we now use fwrite().
>   */
> -#define ECHO do { if (fwrite( zconftext, zconfleng, 1, zconfout )) {} } while (0)
> +#define ECHO fwrite( zconftext, zconfleng, 1, zconfout )
>  #endif
>  
>  /* Gets input and stuffs it into "buf".  number of characters read, or YY_NULL,

But this hunk looks unrelated. Is this needed?


Paul Bolle


  reply	other threads:[~2014-11-04 14:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04  9:05 [PATCH 1/2] kconfig: don't silently ignore unhandled characters Jan Beulich
2014-11-04 14:06 ` Paul Bolle [this message]
2014-11-04 14:14   ` Jan Beulich
2014-11-05 10:36     ` Paul Bolle
2014-11-06 10:19       ` Jan Beulich
2014-11-06 10:28         ` Paul Bolle
2014-12-09 10:16     ` Paul Bolle
2014-12-19 16:31       ` Jan Beulich

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=1415110006.20372.165.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=JBeulich@suse.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=yann.morin.1998@free.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