All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Dwiastika Peppy <dwiastikapeppy@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux Kernel
Date: Tue, 23 Oct 2012 07:34:51 -0700	[thread overview]
Message-ID: <5086AB0B.7070402@gmail.com> (raw)
In-Reply-To: <CABTsxV5OCX=P8u-p6K4eoaAyWo-SGNcD0VxHkkFXOQu7r+Vs1g@mail.gmail.com>

On 10/23/2012 04:32 AM, Dwiastika Peppy wrote:
> Hai Justin. My name is Peppy
> I wanna ask you about installing Linux Kernel 2.6.27
> I'm a newbie in Linux user
> I got problem when installed Linux Kernel and this is the problem :
> *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*
>
> what should i do to solve this problem?
> maybe you can help me..
> Thank you before Justin
>
> Best Regards,
>
>
> Peppy


from what I remember libc made the change then everything else had to be 
fixed. this commit is the commit which fixes it:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=d15bd1067b1fcb2b7250d22bc0c7c7fea0b759f7

but after thinking this over we probably should have done a
get_line || getline();
so old and new can always be working for people using older kernels and 
in the event of bisecting. but then again we might have more of a 
bloated kernel if we did this approach to _every_ function definition 
rename in the kernel.

anyway hope this helps with your build experience of the kernel.

Justin P. Mattock

       reply	other threads:[~2012-10-23 14:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABTsxV5OCX=P8u-p6K4eoaAyWo-SGNcD0VxHkkFXOQu7r+Vs1g@mail.gmail.com>
2012-10-23 14:34 ` Justin P. Mattock [this message]
2013-02-19  5:20 Linux Kernel kapil agrawal
2013-02-19  5:39 ` Valdis.Kletnieks at vt.edu
2013-02-19  5:53 ` Sengottuvelan S
2013-02-19  6:31   ` kapil agrawal
2013-02-19  7:25     ` Valdis.Kletnieks at vt.edu
  -- strict thread matches above, loose matches on Subject: below --
2005-04-22  2:43 Marcondes Monteiro de Arau
2005-04-22  5:06 ` Matan Peled

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=5086AB0B.7070402@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=dwiastikapeppy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.