From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] trying to use https://github.com/beagleboard/linux.git with buildroot
Date: Wed, 23 Dec 2015 23:52:53 +0100 [thread overview]
Message-ID: <20151223235253.0afe702e@free-electrons.com> (raw)
In-Reply-To: <1450910736.3752716.475291418.490BB3EA@webmail.messagingengine.com>
Dear Craig Swank,
On Wed, 23 Dec 2015 14:45:36 -0800, Craig Swank wrote:
> Is it strange to you that when I do the build the output/build directory
> has both of these dirs?
>
> ? buildroot git:(master) ? ls output/build/linux-*
> output/build/linux-4.1.4-ti-r9
> output/build/linux-headers-3.12.10
No, it is perfectly fine. linux-headers is used when building the
toolchain. linux is used to build the kernel itself.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-12-23 22:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 17:04 [Buildroot] trying to use https://github.com/beagleboard/linux.git with buildroot Craig Swank
2015-12-23 17:47 ` Thomas Petazzoni
[not found] ` <1450893821.3034067.475093450.34890777@webmail.messagingengine.com>
2015-12-23 18:15 ` Craig Swank
2015-12-23 18:39 ` Thomas Petazzoni
2015-12-23 18:59 ` Craig Swank
2015-12-23 22:45 ` Craig Swank
2015-12-23 22:52 ` Thomas Petazzoni [this message]
2015-12-24 0:42 ` Craig Swank
2015-12-24 12:44 ` Chris LaRocque
2015-12-24 19:35 ` Craig Swank
2015-12-26 16:00 ` Chris LaRocque
2015-12-26 16:31 ` Craig Swank
2015-12-26 18:34 ` Craig Swank
2015-12-26 23:02 ` Frank Hunleth
2015-12-26 23:44 ` Craig Swank
2015-12-27 0:09 ` Chris LaRocque
2015-12-27 10:08 ` Thomas Petazzoni
2015-12-27 13:34 ` Craig Swank
2015-12-27 13:35 ` Craig Swank
2015-12-27 16:28 ` Chris LaRocque
2015-12-27 17:01 ` Craig Swank
2015-12-27 18:36 ` Chris LaRocque
2015-12-27 18:48 ` Craig Swank
2015-12-27 19:27 ` Craig Swank
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=20151223235253.0afe702e@free-electrons.com \
--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 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.