From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel headers from an externally built kernel
Date: Thu, 6 May 2010 19:08:21 +0200 [thread overview]
Message-ID: <20100506190821.3cb51919@surf> (raw)
In-Reply-To: <C5029C549AA03148AF1B73C0F27DC86D016F1B7C@mse2003.vanteonrdc.vanteon.com>
On Thu, 6 May 2010 12:52:13 -0400
"Wagner, Scott" <swagner@vanteon.com> wrote:
> I would like to use buildroot to create a root file system only - I have
> an external toolchain and an external cross-built kernel made with that
> toolchain.
>
> How do I configure buildroot to reference the external kernel's headers?
> In poking through the makefiles, it looks like this is possible, but I
> have not yet found a way to specify it through menuconfig or by feeding
> environment variables to make. I'm currently building with
> BR2_KERNEL_none=y.
>
> I think that as a result buildroot is trying to use the host platform's
> kernel headers, because the busybox build fails looking for an mtd
> header file, which is not present in the host's kernel headers - but
> this is just a guess.
In external toolchain mode, Buildroot simply uses the kernel headers as
available in the external toolchain. There is no option to use other
kernel headers, as it wouldn't make sense: kernel headers *are* part of
the external toolchain.
Concerning the MTD build problem, you may want to apply the patch
http://git.buildroot.net/~tpetazzoni/git/buildroot/patch/?id=93abe41eefbc1cea9b9a457011f66037772f4265.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2010-05-06 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 16:52 [Buildroot] Kernel headers from an externally built kernel Wagner, Scott
2010-05-06 17:08 ` Thomas Petazzoni [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=20100506190821.3cb51919@surf \
--to=thomas.petazzoni@free-electrons.com \
--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