aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorH. Peter Anvin <hpa@linux.intel.com>2012-05-14 10:18:25 -0700
committerH. Peter Anvin <hpa@linux.intel.com>2012-05-14 10:18:25 -0700
commitf1905af7672c298d1694aa878d1a0485f81d59b7 (patch)
tree09b83e234d930ca3d69a8a4d3c611f28eb85ea5f
parent8c7394e34a74aeb35ef6563ebd66f43fba7673b0 (diff)
downloadklibc-f1905af7672c298d1694aa878d1a0485f81d59b7.tar.gz
[klibc] Update the documentation about how to get headers
We now rely on "make headers_install", so document that fact. It is actually a simpler procedure in many ways. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
-rw-r--r--usr/klibc/README.klibc13
1 files changed, 6 insertions, 7 deletions
diff --git a/usr/klibc/README.klibc b/usr/klibc/README.klibc
index b4135cb4753b1..8b6e92314b9b1 100644
--- a/usr/klibc/README.klibc
+++ b/usr/klibc/README.klibc
@@ -8,13 +8,12 @@ The build procedure is not very polished yet, but it should work like
this:
a) In the source root directory (the directory above the one in which
- this file is found) create a symlink called "linux" pointing to a
- reasonably recent Linux kernel tree (2.4 or 2.6 should be OK.)
- This tree must have the include/asm symlink set up for the
- architecture you're compiling for, and include/linux/autoconf.h
- must exist. The easiest way to make sure of all of these is to do
- a "make config" or any of its variants on the kernel tree is
- question, followed by a "make dep" (2.4) or "make prepare" (2.6).
+ this file is found) create a symlink called "linux" pointing to the
+ target of "make headers_install" from a recent Linux kernel tree.
+ This can be done by extracting the Linux kernel into a directory,
+ running "make headers_install" for the appropriate architecture,
+ and then making a symlink to the "usr" subdirectory of that directory
+ tree.
b) If you're cross-compiling, you need to set KLIBCARCH to the
appropriate architecture, and set CROSS_COMPILE to your toolchain