| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566 | <?xml version="1.0" encoding="ISO-8859-1"?><!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [  <!ENTITY % general-entities SYSTEM "../general.ent">  %general-entities;]><sect1 id="ch-tools-linux-libc-headers" role="wrap">  <?dbhtml filename="linux-libc-headers.html"?>  <title>Linux-Libc-Headers-&linux-libc-headers-version;</title>  <indexterm zone="ch-tools-linux-libc-headers">    <primary sortas="a-Linux-Libc-Headers">Linux-Libc-Headers</primary>    <secondary>tools, headers</secondary>  </indexterm>  <sect2 role="package">    <title/>    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"    href="../chapter06/linux-libc-headers.xml"    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>    <segmentedlist>      <segtitle>&buildtime;</segtitle>      <segtitle>&diskspace;</segtitle>      <seglistitem>        <seg>&linux-libc-headers-ch5-sbu;</seg>        <seg>&linux-libc-headers-ch5-du;</seg>      </seglistitem>    </segmentedlist>  </sect2>  <sect2 role="installation">    <title>Installation of Linux-Libc-Headers</title>    <para>For years it has been common practice to use <quote>raw</quote>    kernel headers (straight from a kernel tarball) in <filename    class="directory">/usr/include</filename>, but over the last few years,    the kernel developers have taken a strong stance that this should not    be done. This gave birth to the Linux-Libc-Headers Project, which was    designed to maintain an Application Programming Interface (API) stable    version of the Linux headers.</para>    <para>Install the header files:</para><screen><userinput>cp -Rv include/asm-i386 /tools/include/asmcp -Rv include/linux /tools/include</userinput></screen>    <para>If your architecture is not i386 (compatible), adjust the first command    accordingly.</para>  </sect2>  <sect2 role="content">    <title/>    <para>Details on this package are located in    <xref linkend="contents-linux-libc-headers" role="."/></para>  </sect2></sect1>
 |