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

[Randy Dunlap <randy.dunlap@oracle.com>]

Justin Mattock wrote:
> On Tue, Mar 3, 2009 at 12:49 PM, Randy Dunlap <randy.dunlap@oracle.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.

> 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).


-- 
~Randy