From: jacmet at uclibc.org <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target
Date: Tue, 4 Nov 2008 11:58:49 -0800 (PST) [thread overview]
Message-ID: <20081104195849.373663C822@busybox.net> (raw)
Author: jacmet
Date: 2008-11-04 11:58:48 -0800 (Tue, 04 Nov 2008)
New Revision: 23924
Log:
Kernel build fix related to external toolchain use
This patch prevents the user from select "linux (Same version as linux
headers)" as a choice for building the kernel when an external binary
toolchain is used, since "same version as linux headers" doesn't make
sense when an external toolchain is used.
It fixes the issue encountered by Hartley <hartleys@visionengravers.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Modified:
trunk/buildroot/target/Config.in
Changeset:
Modified: trunk/buildroot/target/Config.in
===================================================================
--- trunk/buildroot/target/Config.in 2008-11-04 12:50:38 UTC (rev 23923)
+++ trunk/buildroot/target/Config.in 2008-11-04 19:58:48 UTC (rev 23924)
@@ -45,6 +45,11 @@
kernel headers are just that (headers) and not full
kernels. This is a feature.
+# The kernel with the same version as linux headers cannot be compiled
+# when using an external toolchain, because the linux headers are not
+# handled by Buildroot in this case.
+if BR2_TOOLCHAIN_SOURCE
+
config BR2_KERNEL_LINUX
bool "linux (Same version as linux headers)"
select BR2_PACKAGE_LINUX
@@ -56,6 +61,8 @@
kernel headers are just that (headers) and not full
kernels. This is a feature.
+endif
+
config BR2_KERNEL_HURD
bool "hurd"
help
next reply other threads:[~2008-11-04 19:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 19:58 jacmet at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-30 11:35 [Buildroot] svn commit: trunk/buildroot/target jacmet at uclibc.org
2009-01-13 15:14 jacmet at uclibc.org
2009-01-12 20:58 jacmet at uclibc.org
2009-01-01 17:48 nkukard at uclibc.org
2008-12-17 9:28 ulf at uclibc.org
2008-05-12 12:43 jacmet at uclibc.org
2008-04-04 7:24 jacmet at uclibc.org
2008-03-11 19:28 ninevoltz at uclibc.org
2008-03-11 8:49 jacmet at uclibc.org
2008-03-06 19:00 ninevoltz at uclibc.org
2007-10-05 11:03 aldot at uclibc.org
2007-09-30 12:42 aldot at uclibc.org
2007-09-29 19:47 aldot at uclibc.org
2007-09-23 22:08 ulf at uclibc.org
2007-07-20 12:03 ulf at uclibc.org
2007-07-08 19:23 aldot at uclibc.org
2007-06-26 16:36 aldot at uclibc.org
2007-06-06 19:59 aldot at uclibc.org
2007-04-17 17:30 aldot at uclibc.org
2007-03-22 18:14 aldot at uclibc.org
2007-03-19 10:49 aldot at uclibc.org
2007-02-04 16:30 aldot at uclibc.org
2007-01-30 17:38 aldot at uclibc.org
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=20081104195849.373663C822@busybox.net \
--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