linux-kernel - Re: [PATCH] scripts/unifdef.c: rename getline symbol to something else

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 13 Mar 2009 06:52:09 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Kyle McMartin <kyle@...radead.org>, linux-kernel@...r.kernel.org,
	jakub@...hat.com, linux-kbuild@...r.kernel.org
Subject: Re: [PATCH] scripts/unifdef.c: rename getline symbol to something else

On Wed, Mar 11, 2009 at 11:56:51PM -0700, Andrew Morton wrote:
> On Wed, 11 Mar 2009 14:59:42 -0400 Kyle McMartin <kyle@...radead.org> wrote:
> 
> > On Wed, Mar 11, 2009 at 07:37:35PM +0100, Sam Ravnborg wrote:
> > > > Rawhide builds are currently failing to build unifdef.c, as the next
> > > > version of glibc changes the default _POSIX_C_SOURCE level, which
> > > > exposes getline() from <stdio.h>
> > > > 
> > > > scripts/unifdef.c:209: error: conflicting types for 'getline'
> > > > /usr/include/stdio.h:653: note: previous declaration of 'getline' was
> > > > here
> > > > make[2]: *** [scripts/unifdef] Error 1
> > > > make[1]: *** [__headers] Error 2
> > > > make: *** [vmlinux] Error 2
> > > > 
> > > > Rename the symbol in unifdef.c to parseline to avoid this conflicting
> > > > declaration.
> > > 
> > > I have a similar patch queued in kbuild-fixes.git.
> > > 
> > 
> > Great, thanks. Is this going to go into the next -rc?
> > 
> 
> I was going to put it into 2.6.29 but Sam stole it :)
Bad boy.
The patch is included in -rc8 so everyone is happy again.

	Sam
--
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/