From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] build without linux, busybox, - just buildroot internal toolchain
Date: Tue, 22 Mar 2011 07:51:54 +0200 [thread overview]
Message-ID: <20110322055154.GA1996@nataf.siach.name> (raw)
In-Reply-To: <4D882702.9000807@gmail.com>
Hi Steve,
On Mon, Mar 21, 2011 at 09:35:14PM -0700, Steve Calfee wrote:
> I am trying buildroot partitioned into systems. In my toolchain only
> tree, I disable both kernel, busybox, and all packages. This works,
> but for some reason the entire linux kernel is unpacked in the
> output/toolchain/linux-2.6.37.2. I am not clear on why the toolchain
> needs linux headers,
Any toolchain that generates binaries running under Linux needs header files
from the Linux kernel. These headers define the kernel ABI (Application Binary
Interface), such as system call numbers, structs, etc. Userspace programs
include these headers either directly (from the linux/ directory), or
indirectly via you libc of choice.
> but ok, why does it need the full source?
The Linux headers are not supplied in a separate package. You need to generate
them from the Linux source.
Hope this helps.
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
prev parent reply other threads:[~2011-03-22 5:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 22:25 [Buildroot] 2011.02, BeagleBoard-xM, linux-2.6.37 does not boot Torsten Mohr
2011-03-21 7:51 ` Bob Liu
2011-03-21 21:43 ` Torsten Mohr
2011-03-22 4:35 ` [Buildroot] build without linux, busybox, - just buildroot internal toolchain Steve Calfee
2011-03-22 5:51 ` Baruch Siach [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=20110322055154.GA1996@nataf.siach.name \
--to=baruch@tkos.co.il \
--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