From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Q. How to use a custom kernel tree?
Date: Fri, 8 Mar 2013 17:07:03 +0100 [thread overview]
Message-ID: <20130308170703.66d093d7@skate> (raw)
In-Reply-To: <625541783.243878.1362758451151.JavaMail.root@openwide.fr>
Dear Jeremy Rosen,
Please don't top-post, this is annoying.
On Fri, 8 Mar 2013 17:00:51 +0100 (CET), Jeremy Rosen wrote:
> simplest is to set a local.mk containing
>
> LINUX_OVERRIDE_SRCDIR=<path to your uncompressed source>
>
> this will use your directory as the sources.
>
> there is also an option to specify the config file.
>
> with those two you should be good
This doesn't really answers Chris question. The LINUX_OVERRIDE_SRCDIR
mechanism is usually meant to be useful during development, when you're
actively modifying your kernel tree.
Apparently, Chris is in a situation where he has some kernel sources
that don't change, and therefore he creates a tarball from them, and
expect Buildroot to be able to use this tarball. This can normally be
achieved using the BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION option,
which Chris rightly tried to use.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-03-08 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 15:47 [Buildroot] Q. How to use a custom kernel tree? Chris Wilkinson
2013-03-08 16:00 ` Jeremy Rosen
2013-03-08 16:07 ` Thomas Petazzoni [this message]
2013-03-08 16:09 ` Jeremy Rosen
2013-03-08 16:12 ` Thomas Petazzoni
2013-03-08 19:21 ` Chris Wilkinson
2013-03-08 16:05 ` Thomas Petazzoni
2013-03-11 15:49 ` Chris Wilkinson
2013-03-11 17:30 ` Thomas Petazzoni
2013-03-08 16:07 ` Stephan Hoffmann
2013-03-11 14:34 ` Chris Wilkinson
2013-03-12 11:17 ` Rafał Fabich
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=20130308170703.66d093d7@skate \
--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