From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] 2009.11-rc1 build failure
Date: Fri, 27 Nov 2009 11:02:14 +0100 [thread overview]
Message-ID: <87eink70bd.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <op.u31nbqpqyqa4qb@jap-lappis.nevion.com> (Joachim Pihl's message of "Fri\, 27 Nov 2009 09\:03\:16 +0100")
>>>>> "Joachim" == Joachim Pihl <jpihl@nevion.com> writes:
Hi,
Joachim> This is what I extracted from the email that came back from
Joachim> this list, I think you made a mistake somewhere:
Joachim> # BR2_KERNEL_HEADERS_2_6_31 is not set
Joachim> BR2_KERNEL_HEADERS_VERSION=y
Joachim> # BR2_KERNEL_HEADERS_SNAP is not set
Joachim> BR2_DEFAULT_KERNEL_VERSION="2.6.27.10"
Joachim> BR2_DEFAULT_KERNEL_HEADERS="2.6.27.10"
Argh, sorry - I have too many /tmp/.config* files :/
Your fix is then to use the 2.6.27.x version instead of hardcoding
2.6.27.10 - That will make you use 2.6.27.39 which has the getline fix.
Notice that your kernel headers version doesn't need to be the same as
the kernel version you're using.
>> The getline problem is a known issue with old kernels and new
>> distributions (fixed in 2.6.29+ and later versions of 2.6.27.x).
Joachim> OK.
Joachim> Some time back, I remember hearing that 2.6.27 was the branch
Joachim> that was to be maintained for XScale PXA. Is this correct, or
Joachim> are all XScale oddities handled in later kernel versions?
I don't know about PXA in particular (but even if so, please use the
latest in the 2.6.27.x series). In general, the latest stable kernel
release (currently 2.6.31.6) is the most sensible choice.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-11-27 10:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 14:15 [Buildroot] 2009.11-rc1 build failure Joachim Pihl
2009-11-26 14:31 ` Peter Korsgaard
2009-11-27 8:03 ` Joachim Pihl
2009-11-27 10:02 ` Peter Korsgaard [this message]
2009-11-27 10:47 ` Michael S. Zick
2009-11-27 18:09 ` Joachim Pihl
[not found] ` <op.u32e97xjyqa4qb@jap-lappis>
2009-11-27 18:13 ` Peter Korsgaard
2009-11-27 18:26 ` Michael S. Zick
2009-11-27 18:41 ` Joachim Pihl
2009-11-27 18:51 ` Peter Korsgaard
2009-11-27 19:11 ` Joachim Pihl
2009-11-27 19:42 ` Peter Korsgaard
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=87eink70bd.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