Current BE-LFS (but w/ GCC 3.3.3) merged -> 6.0 branch

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3445 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

1 files changed, 43 insertions, 0 deletions

diff --git a/chapter06/linux-libc-headers.xml b/chapter06/linux-libc-headers.xml
new file mode 100644
index 000000000..03cf0ecaa
--- /dev/null
+++ b/chapter06/linux-libc-headers.xml
@@ -0,0 +1,43 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+  <!ENTITY % general-entities SYSTEM "../general.ent">
+  %general-entities;
+]>
+<sect1 id="ch-system-linux-libc-headers">
+<title>Linux-Libc-Headers-&linux-libc-headers-version;</title>
+<?dbhtml filename="linux-libc-headers.html"?>
+
+<indexterm zone="ch-system-linux-libc-headers">
+<primary sortas="a-Linux-Libc-Headers">Linux-Libc-Headers</primary>
+<secondary>system, headers</secondary></indexterm>
+
+<screen>&buildtime; 0.1 SBU
+&diskspace; 22 MB</screen>
+
+
+<sect2>
+<title>Installation of Linux-Libc-Headers</title>
+
+<para>For years it has been common practice to use so-called <quote>raw</quote>
+kernel headers (straight from a kernel tarball) in /usr/include, but over the
+last few years, the kernel developers have taken a strong stance that such
+things should not be done.  Thus was born the linux-libc-headers project,
+designed to maintain an API stable version of the Linux headers.</para>
+
+<para>Install the header files:</para>
+
+<screen><userinput>cp -R include/asm-i386 /usr/include/asm
+cp -R include/linux /usr/include</userinput></screen>
+
+<para>Assure that all the headers are owned by root:</para>
+
+<screen><userinput>chown -R root:root /usr/include/{asm,linux}</userinput></screen>
+
+<para>And make sure all the users can read the headers:</para>
+
+<screen><userinput>find /usr/include/{asm,linux} -type d -exec chmod 755 {} \;
+find /usr/include/{asm,linux} -type f -exec chmod 644 {} \;</userinput></screen>
+
+</sect2>
+
+</sect1>