linux-kernel - Re: [DOCS] make headers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200706221618.58455.rob@landley.net>
Date:	Fri, 22 Jun 2007 16:18:58 -0400
From:	Rob Landley <rob@...dley.net>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [DOCS] make headers_install

On Friday 22 June 2007 01:14:50 David Woodhouse wrote:
> On Fri, 2007-06-22 at 00:04 -0400, Rob Landley wrote:
> > Here's a really quick stab at documentation for make headers_install.
> >
> > Comments?
> >
> > --------------------
> >
> > Exporting kernel headers for use by userspace (/usr/include/linux)
>
> Also /usr/include/asm (and asm-* on biarch 64-bit architectures), along
> with a few other directories. See $linux/include/Kbuild.
>
> Other than that it looks relatively sane; thanks.

For some reason I was thinking that the asm directory was under include/linux 
even though I know that's not the case.  Brain glitch.

This clear things up?

--- headers.bak 2007-06-22 16:13:42.000000000 -0400
+++ headers.txt 2007-06-22 16:16:22.000000000 -0400
@@ -9,8 +9,9 @@
 system calls, as well as constants and structures to be used with these
 system calls.  The C library's header files include the kernel header files
 from the "linux" subdirectory.  The system's libc headers are usually
-installed at the default location /usr/include and the kernel headers at
-/usr/include/linux.
+installed at the default location /usr/include and the kernel headers in
+subdirectories under that (most notably /usr/include/linux and
+/usr/include/asm).

 Kernel headers are backwards compatible, but not forwards compatible.  This
 means that a program built against a C library using older kernel headers

New version attached.

Rob
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.

View attachment "headers_install.txt" of type "text/plain" (2188 bytes)