linux-kernel - Re: scripts/unifdef.c:209: error: conflicting types for 'getline'

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <dd18b0c30903031640r6644e878pb1eb943fb34f9c59@mail.gmail.com>
Date:	Tue, 3 Mar 2009 16:40:04 -0800
From:	Justin Mattock <justinmattock@...il.com>
To:	Johannes Weiner <hannes@...xchg.org>
Cc:	Randy Dunlap <randy.dunlap@...cle.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: scripts/unifdef.c:209: error: conflicting types for 'getline'

On Tue, Mar 3, 2009 at 2:36 PM, Justin Mattock <justinmattock@...il.com> wrote:
> On Tue, Mar 3, 2009 at 1:20 PM, Johannes Weiner <hannes@...xchg.org> wrote:
>> On Tue, Mar 03, 2009 at 01:07:29PM -0800, Randy Dunlap wrote:
>>> Justin Mattock wrote:
>>> > On Tue, Mar 3, 2009 at 12:49 PM, Randy Dunlap <randy.dunlap@...cle.com> wrote:
>>> >> Justin Mattock wrote:
>>> >>> Hello;
>>> >>> I am unable to compile the kernel
>>> >>> (just did a git pull a few minuets ago);
>>> >>> here is what I see:
>>> >>>
>>> >>> WARNING: modpost: Found 1 section mismatch(es).
>>> >>> To see full details build your kernel with:
>>> >>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
>>> >>>   GEN     .version
>>> >>>   CHK     include/linux/compile.h
>>> >>>   UPD     include/linux/compile.h
>>> >>>   CC      init/version.o
>>> >>>   LD      init/built-in.o
>>> >>>   LD      .tmp_vmlinux1
>>> >>>   KSYM    .tmp_kallsyms1.S
>>> >>>    AS      .tmp_kallsyms1.o
>>> >>>   LD      .tmp_vmlinux2
>>> >>>   KSYM    .tmp_kallsyms2.S
>>> >>>   AS      .tmp_kallsyms2.o
>>> >>>   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[2]: *** [scripts/unifdef] Error 1
>>> >>> make[1]: *** [__headers] Error 2
>>> >>> make: *** [vmlinux] Error 2
>>> >>>
>>> >>> The only change to .config was:
>>> >>>
>>> >>> SYSFS_DEPRECATED_V2 [=y]
>>> >>> to
>>> >>> SYSFS_DEPRECATED_V2 [=n]
>>> >>> to see if I can make udev from:
>>> >>>
>>> >>> udev: starting version 137
>>> >>> [    7.557317] udev: deprecated sysfs layout; update the kernel or disable
>>> >>> CONFIG_SYSFS_DEPRECATED; some udev features will not work correctly
>>> >>>
>>> >>> giving me this message.
>>> >>>
>>> >>> also I did use a CFLAGS when compiling,
>>> >>> but never received this when doing so for:
>>> >>> 2.6.29-rc5-00289-g460c133
>>> >>>
>>> >>> any info would be appreciated.
>>> >> What CFLAGS?  I can't reproduce the problem.
>>> >>
>>> >>
>>> >> --
>>> >> ~Randy
>>> >>
>>> >
>>> > make CC=/usr/bin/i686-pc-linux-gnu-gcc-4.4.0 CFLAGS="-march=core2
>>> > -mtune=core2 -O2 -pipe -fomit-frame-pointer"
>>> > CXXFLAGS="${CFLAGS}" MAKEOPTS="-j3"
>>>
>>> I still can't reproduce the problem by using those CFLAGS/CXXFLAGS.
>>
>> chigurh:~/linux/linux-2.6/scripts$ make unifdef CFLAGS="-D_GNU_SOURCE"
>> cc -D_GNU_SOURCE    unifdef.c   -o unifdef
>> unifdef.c:209: error: conflicting types for `getline'
>> /usr/include/stdio.h:649: error: previous declaration of `getline' was here
>> make: *** [unifdef] Error 1
>> chigurh:~/linux/linux-2.6/scripts$ make unifdef
>> cc     unifdef.c   -o unifdef
>> chigurh:~/linux/linux-2.6/scripts$
>>
>>> > I also just loaded the latest libc
>>> > (not sure if this has anything to do);
>>>
>>> That probably updated /usr/include/stdio.h (?; I'm just guessing here).
>>
>> Perhaps getline() is now defined even without _GNU_SOURCE?  But I
>> doubt that...
>>
>>        Hannes
>>
>
> Well, maybe I need to just do a
> make clean
> before compiling.
>
>
> --
> Justin P. Mattock
>

Well, that didn't seem to be a simple solution.
I guess I'm stuck with what I have.

-- 
Justin P. Mattock
--
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/