[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49AFF0D7.8080007@oracle.com>
Date: Thu, 05 Mar 2009 07:33:43 -0800
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Justin Mattock <justinmattock@...il.com>
CC: Frederic Weisbecker <fweisbec@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 1/1] unifdef.c change "getline" to "get_line" to avoid
C library confusion.
> From: Justin P. Mattock <justinmattock@...il.com>
> Signed-off-by: Justin P. Mattock <justinmattock@...il.com>
>
> This fixes an error when compiling the kernel.
Did you determine why you need this now and other people don't
need it (yet)? Maybe the rest of us will need it in the future...
> CHK include/linux/version.h
> HOSTCC scripts/unifdef
> scripts/unifdef.c:209: error: conflicting types for 'getline'
> /usr/include/stdio.h:651: note: previous declaration of 'getline' was here
> make[1]: *** [scripts/unifdef] Error 1
> make: *** [__headers] Error 2
>
> --
> scripts/unifdef.c | 3 +++
> 1 files changed, 3 insertions(+),0 deletions(-)
>
> ---a/scripts/unifdef.c 2009-03-05 00:07:28.000000000 -0800
> +++b/scripts/unifdef.c 2009-03-05 00:04:56.000000000 -0800
> @@ -206,7 +206,7 @@ static void done(void);
> static void error(const char *);
> static int findsym(const char *);
> static void flushline(bool);
> -static Linetype getline(void);
> +static Linetype get_line(void);
> static Linetype ifeval(const char **);
> static void ignoreoff(void);
> static void ignoreon(void);
> @@ -512,7 +512,7 @@ process(void)
>
> for (;;) {
> linenum++;
> - lineval = getline();
> + lineval = get_line();
> trans_table[ifstate[depth]][lineval]();
> debug("process %s -> %s depth %d",
> linetype_name[lineval],
> @@ -526,7 +526,7 @@ process(void)
> * help from skipcomment().
> */
> static Linetype
> -getline(void)
> +get_line(void)
> {
> const char *cp;
> int cursym;
>
>
--
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists