diff options
| author | maximilian attems <max@stro.at> | 2013-08-21 17:31:25 +0200 |
|---|---|---|
| committer | maximilian attems <max@stro.at> | 2013-08-21 17:32:16 +0200 |
| commit | 25a66fa8d8623fae267f6807b56438cd7c40e034 (patch) | |
| tree | b13672ec27b6fab7639ab1a1a7591c9e9d733580 | |
| parent | 686f1931b7dc102c32b59db638a3082d5c2251e5 (diff) | |
| download | klibc-25a66fa8d8623fae267f6807b56438cd7c40e034.tar.gz | |
README.klibc: update build information
It seems this file was still conveying the old way to build klibc
and hence confusing the users, simplify and reword build instructions.
Signed-off-by: maximilian attems <max@stro.at>
| -rw-r--r-- | usr/klibc/README.klibc | 17 |
1 files changed, 7 insertions, 10 deletions
diff --git a/usr/klibc/README.klibc b/usr/klibc/README.klibc index 47618ec7c5c606..7de5fea52fce10 100644 --- a/usr/klibc/README.klibc +++ b/usr/klibc/README.klibc @@ -7,13 +7,12 @@ work in progress, and a lot of things are still missing. 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 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. +a) Extract a recent Linux kernel into a directory and run + "make headers_install". + Now enter the klibc dir and point KLIBCKERNELSRC to the + path of the configured linux tree + "make KLIBCKERNELSRC=`pwd`/../linux/usr/". + b) If you're cross-compiling, you need to set KLIBCARCH to the appropriate architecture, and set CROSS_COMPILE to your toolchain @@ -66,9 +65,7 @@ b) If you're cross-compiling, you need to set KLIBCARCH to the Note that even the "working" ones likely have bugs. Please report them if you run into them. -c) Type "make" and pray... - -d) Try the test programs in the tests/ directory. They should run... +c) Try the test programs in the tests/ directory. They should run... Contact the klibc mailing list: |