From: Justin Mattock <justinmattock@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: scripts/unifdef.c:209: error: conflicting types for 'getline'
Date: Tue, 3 Mar 2009 12:36:48 -0800 [thread overview]
Message-ID: <dd18b0c30903031236t6ed1adaen64507b0ab4be34a4@mail.gmail.com> (raw)
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.
regards;
--
Justin P. Mattock
next reply other threads:[~2009-03-03 20:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 20:36 Justin Mattock [this message]
2009-03-03 20:49 ` Randy Dunlap
2009-03-03 21:00 ` Justin Mattock
2009-03-03 21:07 ` Randy Dunlap
2009-03-03 21:17 ` Justin Mattock
2009-03-03 21:20 ` Johannes Weiner
2009-03-03 22:36 ` Justin Mattock
2009-03-04 0:40 ` Justin Mattock
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=dd18b0c30903031236t6ed1adaen64507b0ab4be34a4@mail.gmail.com \
--to=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®