All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 1261] New: The getline() in output/build/linux-2.6.28/scripts/unifdef.c in buildroot is buggy
Date: Thu, 11 Mar 2010 05:47:27 +0000 (UTC)	[thread overview]
Message-ID: <bug-1261-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=1261

           Summary: The getline() in output/build/linux-
                    2.6.28/scripts/unifdef.c in buildroot is buggy
           Product: buildroot
           Version: unspecified
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Keywords: link-failure
          Severity: enhancement
          Priority: P3
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: vikki.km at gmail.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Hi,

Yesterday i was trying to buildroot for my ARM920t and i think this is the bug.

Target: ARM920t
OS: Fedora 12 ( 2.6.31 using)
Kernel Headers: 2.6.32
Kernel used: 2.6.28

output/build/linux-2.6.28/scripts/unifdef.c

the getline() function in unidef.c contradicts with the already present getline
function in stdio.h and gives this error

error:
/usr/include/stdio.h:653: note: previous declaration of ?getline? was here

How i fixed the error?

i changed the getline function in unidef.c to get_line ie. other than getline
and it works fine.


-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2010-03-11  5:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11  5:47 bugzilla at busybox.net [this message]
2010-03-14  7:26 ` [Buildroot] [Bug 1261] The getline() in output/build/linux-2.6.28/scripts/unifdef.c in buildroot is buggy bugzilla at busybox.net
2010-07-18 17:00 ` bugzilla at busybox.net

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=bug-1261-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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.