Changeset fae9234
- Timestamp:
- 01/23/2005 11:20:57 AM (19 years ago)
- Children:
- bcadcfe
- Parents:
- f5e6d97
- Location:
- chapter05
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/linux-libc-headers-alpha.xml
rf5e6d97 rfae9234 12 12 <secondary>tools, headers</secondary></indexterm> 13 13 14 <sect2 role="package"><title/>15 14 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" 16 href="../chapter06/linux-libc-headers.xml" 17 xpointer="xpointer(/sect1/sect2[1]/para[1])"/> 18 19 <segmentedlist> 20 <segtitle>&buildtime;</segtitle> 21 <segtitle>&diskspace;</segtitle> 22 <seglistitem><seg>0.1 SBU</seg><seg>22 MB</seg></seglistitem> 23 </segmentedlist> 24 25 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" 26 href="../chapter06/linux-libc-headers-alpha.xml" 27 xpointer="xpointer(/sect1/sect2[1]/segmentedlist[2])"/> 28 29 30 </sect2> 15 href="../chapter05/linux-libc-headers.xml" 16 xpointer="xpointer(/sect1/sect2[@role='package'])"/> 31 17 32 18 <sect2 role="installation"> 33 19 <title>Installation of Linux-Libc-Headers</title> 34 20 35 <para>For years it has been common practice to use <quote>raw</quote> kernel 36 headers (straight from a kernel tarball) in <filename 37 class="directory">/usr/include</filename>, but over the 38 last few years, the kernel developers have taken a strong stance that 39 this should not be done. This gave birth to the Linux-Libc-Headers 40 Project, which was designed to maintain an Application Programming 41 Interface (API) stable version of the Linux headers.</para> 21 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" 22 href="../chapter05/linux-libc-headers.xml" 23 xpointer="xpointer(/sect1/sect2[@role='installation']/para[1])"/> 42 24 43 25 <para>Install the header files:</para> … … 48 30 </sect2> 49 31 50 <sect2 role="content"><title/> 51 <para>Details on this package are located in <xref 52 linkend="contents-linux-libc-headers" role="."/></para> 53 </sect2> 32 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" 33 href="../chapter05/linux-libc-headers.xml" 34 xpointer="xpointer(/sect1/sect2[@role='content'])"/> 54 35 55 36 </sect1> -
chapter05/linux-libc-headers-ppc.xml
rf5e6d97 rfae9234 12 12 <secondary>tools, headers</secondary></indexterm> 13 13 14 <sect2 role="package"><title/>15 14 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" 16 href="../chapter06/linux-libc-headers.xml" 17 xpointer="xpointer(/sect1/sect2[1]/para[1])"/> 18 19 <segmentedlist> 20 <segtitle>&buildtime;</segtitle> 21 <segtitle>&diskspace;</segtitle> 22 <seglistitem><seg>0.1 SBU</seg><seg>22 MB</seg></seglistitem> 23 </segmentedlist> 24 25 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" 26 href="../chapter06/linux-libc-headers-ppc.xml" 27 xpointer="xpointer(/sect1/sect2[1]/segmentedlist[2])"/> 28 29 30 </sect2> 15 href="../chapter05/linux-libc-headers.xml" 16 xpointer="xpointer(/sect1/sect2[@role='package'])"/> 31 17 32 18 <sect2 role="installation"> 33 19 <title>Installation of Linux-Libc-Headers</title> 34 20 35 <para>For years it has been common practice to use <quote>raw</quote> kernel 36 headers (straight from a kernel tarball) in <filename 37 class="directory">/usr/include</filename>, but over the 38 last few years, the kernel developers have taken a strong stance that 39 this should not be done. This gave birth to the Linux-Libc-Headers 40 Project, which was designed to maintain an Application Programming 41 Interface (API) stable version of the Linux headers.</para> 21 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" 22 href="../chapter05/linux-libc-headers.xml" 23 xpointer="xpointer(/sect1/sect2[@role='installation']/para[1])"/> 42 24 43 25 <para>Install the header files:</para> … … 48 30 </sect2> 49 31 50 <sect2 role="content"><title/> 51 <para>Details on this package are located in <xref 52 linkend="contents-linux-libc-headers" role="."/></para> 53 </sect2> 32 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" 33 href="../chapter05/linux-libc-headers.xml" 34 xpointer="xpointer(/sect1/sect2[@role='content'])"/> 54 35 55 36 </sect1> -
chapter05/linux-libc-headers-raq2.xml
rf5e6d97 rfae9234 12 12 <secondary>tools, headers</secondary></indexterm> 13 13 14 <sect2 role="package"><title/>15 14 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" 16 href="../chapter06/linux-libc-headers.xml" 17 xpointer="xpointer(/sect1/sect2[1]/para[1])"/> 18 19 <segmentedlist> 20 <segtitle>&buildtime;</segtitle> 21 <segtitle>&diskspace;</segtitle> 22 <seglistitem><seg>0.1 SBU</seg><seg>22 MB</seg></seglistitem> 23 </segmentedlist> 24 25 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" 26 href="../chapter06/linux-libc-headers-raq2.xml" 27 xpointer="xpointer(/sect1/sect2[1]/segmentedlist[2])"/> 28 29 30 </sect2> 15 href="../chapter05/linux-libc-headers.xml" 16 xpointer="xpointer(/sect1/sect2[@role='package'])"/> 31 17 32 18 <sect2 role="installation"> 33 19 <title>Installation of Linux-Libc-Headers</title> 34 20 35 <para>For years it has been common practice to use <quote>raw</quote> kernel 36 headers (straight from a kernel tarball) in <filename 37 class="directory">/usr/include</filename>, but over the 38 last few years, the kernel developers have taken a strong stance that 39 this should not be done. This gave birth to the Linux-Libc-Headers 40 Project, which was designed to maintain an Application Programming 41 Interface (API) stable version of the Linux headers.</para> 21 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" 22 href="../chapter05/linux-libc-headers.xml" 23 xpointer="xpointer(/sect1/sect2[@role='installation']/para[1])"/> 42 24 43 25 <para>This patch fixes a compile issue with Glibc on a RaQ2 server.</para> … … 52 34 </sect2> 53 35 54 <sect2 role="content"><title/> 55 <para>Details on this package are located in <xref 56 linkend="contents-linux-libc-headers" role="."/></para> 57 </sect2> 36 <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" 37 href="../chapter05/linux-libc-headers.xml" 38 xpointer="xpointer(/sect1/sect2[@role='content'])"/> 58 39 59 40 </sect1> -
chapter05/linux-libc-headers.xml
rf5e6d97 rfae9234 43 43 <para>Install the header files:</para> 44 44 45 <screen arch="x86"><userinput>cp -R include/asm-i386 /usr/include/asm 46 cp -R include/linux /usr/include</userinput></screen> 47 48 <screen arch="ppc"><userinput>cp -R include/asm-ppc /usr/include/asm 45 <screen><userinput>cp -R include/asm-i386 /usr/include/asm 49 46 cp -R include/linux /usr/include</userinput></screen> 50 47
Note:
See TracChangeset
for help on using the changeset viewer.