From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 573] New: BR2_DEFAULT_KERNEL_HEADERS is undefined with external toolchain
Date: Wed, 19 Aug 2009 13:30:40 +0000 (UTC) [thread overview]
Message-ID: <bug-573-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=573
Summary: BR2_DEFAULT_KERNEL_HEADERS is undefined with external
toolchain
Product: buildroot
Version: unspecified
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: n0-1 at nwl.cc
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Hi,
I'm trying to compile using an external binary toolchain (installed via
crossdev in Gentoo), but when BR2_TOOLCHAIN_EXTERNAL is active,
toolchain/kernel-headers/Config.in is not being included. The later leads to an
undefined BR2_DEFAULT_KERNEL_HEADERS, which again makes buildroot try to
download http://www.kernel.org/pub//linux/kernel/v2.6/linux-..tar.bz2.
Greetings, Phil
--
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.
next reply other threads:[~2009-08-19 13:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 13:30 bugzilla at busybox.net [this message]
2009-08-19 13:46 ` [Buildroot] [Bug 573] BR2_DEFAULT_KERNEL_HEADERS is undefined with external toolchain bugzilla at busybox.net
2009-08-19 21:24 ` bugzilla at busybox.net
2009-08-19 21:32 ` bugzilla at busybox.net
2009-08-20 9:22 ` bugzilla at busybox.net
2009-08-20 9:23 ` bugzilla at busybox.net
2009-08-26 20:58 ` bugzilla at busybox.net
2009-08-26 22:12 ` bugzilla at busybox.net
2009-08-27 13:44 ` 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-573-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.