Documentation in kbuild/headers_install.txt is not
up to date regarding:
- way to list the various architectures;
- path where the headers are installed.

This patch try to fix these issues.

Cc: Kirill A. Shutemov <kir...@shutemov.name>
Cc: Michal Marek <mma...@suse.cz>
Cc: David Woodhouse <dw...@infradead.org>
Cc: Rob Landley <r...@landley.net>
Cc: Sam Ravnborg <s...@ravnborg.org>
Signed-off-by: Yann Droneaud <ydrone...@opteya.com>
---
 Documentation/kbuild/headers_install.txt | 15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/Documentation/kbuild/headers_install.txt 
b/Documentation/kbuild/headers_install.txt
index 951eb9f1e040..8b6751f10dd3 100644
--- a/Documentation/kbuild/headers_install.txt
+++ b/Documentation/kbuild/headers_install.txt
@@ -24,23 +24,24 @@ The "make headers_install" command can be run in the top 
level directory of the
 kernel source code (or using a standard out-of-tree build).  It takes two
 optional arguments:
 
-  make headers_install ARCH=i386 INSTALL_HDR_PATH=/usr/include
+  make headers_install ARCH=i386 INSTALL_HDR_PATH=/usr
 
 ARCH indicates which architecture to produce headers for, and defaults to the
-current architecture.  The linux/asm directory of the exported kernel headers
-is platform-specific, to see a complete list of supported architectures use
+current architecture.  The asm/ directory of the exported kernel headers
+is platform-specific, to see a list of supported architectures use
 the command:
 
-  ls -d include/asm-* | sed 's/.*-//'
+  /bin/ls -1 arch/*/include/asm/Kbuild | sed -e 's,^arch/,,' \
+                                             -e 's,/include/asm/Kbuild$,,'
 
-INSTALL_HDR_PATH indicates where to install the headers.  It defaults to
-"./usr/include".
+INSTALL_HDR_PATH indicates where to create include/ directory to install the
+headers. It defaults to "./usr/".
 
 The command "make headers_install_all" exports headers for all architectures
 simultaneously.  (This is mostly of interest to distribution maintainers,
 who create an architecture-independent tarball from the resulting include
 directory.)  You also can use HDR_ARCH_LIST to specify list of architectures.
-Remember to provide the appropriate linux/asm directory via "mv" or "ln -s"
+Remember to provide the appropriate asm/ directory via "mv" or "ln -s"
 before building a C library with headers exported this way.
 
 The kernel header export infrastructure is maintained by David Woodhouse
-- 
1.9.3

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to