From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Conflicting types for getline
Date: Sat, 03 Oct 2009 19:02:32 +0200 [thread overview]
Message-ID: <87ljjs5s2f.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <7085C89ACBD47E4B947F91A84B9EA9240C1CF914C4@EXCHANGE31.staff.main.ntu.edu.sg> (Teng Chee Wan Philip's message of "Sat\, 3 Oct 2009 21\:48\:02 +0800")
>>>>> "Teng" == Teng Chee Wan Philip <tcheewan@ntu.edu.sg> writes:
Teng> Hi,
Teng> I encountered an error running make for buildroot. Any ideas? Thanks in advance.
That's a known problem when you try to use older Linux kernels on new
distributions. Select a newer version (>2.6.28) for the Linux kernel
headers and it should work.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-10-03 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7085C89ACBD47E4B947F91A84B9EA9240C1CF914C3@EXCHANGE31.staff.main.ntu.edu.sg>
2009-10-03 13:48 ` [Buildroot] Conflicting types for getline Teng Chee Wan Philip
2009-10-03 17:02 ` Peter Korsgaard [this message]
2010-05-16 10:24 ` [Buildroot] FYI: " Jochen+busybox at Hayek.name
2010-05-16 11:45 ` Michael S. Zick
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=87ljjs5s2f.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox