All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Is there any chance to compile old buildroot on new distro
Date: Thu, 28 Oct 2010 14:14:45 +0200	[thread overview]
Message-ID: <87mxpycy4q.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <AANLkTi=j+qQ7Gq+pA1T4ANRLP_J7ZmEwytKCKx9-MF74@mail.gmail.com> (Sasha Yohananov's message of "Thu, 28 Oct 2010 10:00:41 +0200")

>>>>> "Sasha" == Sasha Yohananov <yohananov@gmail.com> writes:

 Sasha> Dear buildroot experts,

 Sasha> For about 2 years I work on some commercial project (access control) based on
 Sasha> buildroot-2008.11.

There's never been a 2008.11 release, I guess you mean 2009.11?

scripts/unifdef.c:209: error: conflicting types for 'getline'
/usr/include/stdio.h:673: note: previous declaration of 'getline' was here
make[2]: *** [scripts/unifdef] Error 1
make[1]: *** [__headers] Error 2
make[1]: Leaving directory `/home/sasha/work/3rdparty/buildroot/toolchain_build_arm/linux-2.6.27.7'

You'll need a fix for your kernel headers. The easiest is probably to
download 2010.02 and take the
toolchain/kernel-headers/linux-2.6.26.8-unifdef-getline.patch and copy
it to the same directory in your tree (but adjust the kernel version).

You might need the similar patch for uclibc as well.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2010-10-28 12:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTi=CA_91mHxqKye2wPsRVGkOe2Zm2W1LnMGdk_OA@mail.gmail.com>
2010-10-28  8:00 ` [Buildroot] Is there any chance to compile old buildroot on new distro Sasha Yohananov
2010-10-28  8:09   ` Paulius Zaleckas
2010-10-28 11:53     ` Sasha Yohananov
2010-10-28 12:07       ` Sasha Yohananov
2010-10-28 12:15       ` Paulius Zaleckas
2010-10-28 13:51         ` Sasha Yohananov
2010-10-28 12:14   ` Peter Korsgaard [this message]

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=87mxpycy4q.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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.