diff -Naur BOOK/chapter05/.svn/entries BOOKfr/chapter05/.svn/entries
--- BOOK/chapter05/.svn/entries	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/.svn/entries	1970-01-01 01:00:00.000000000 +0100
@@ -1,460 +0,0 @@
-8
-
-dir
-8551
-svn://svn.linuxfromscratch.org/LFS/trunk/BOOK/chapter05
-svn://svn.linuxfromscratch.org/LFS
-
-
-
-2008-04-23T18:33:53.240733Z
-8541
-jhuntwork
-
-
-svn:special svn:externals svn:needs-lock
-
-
-
-
-
-
-
-
-
-
-
-4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
-
-introduction.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-2b23ff19786b196fb8dd17befad5f486
-2007-03-21T18:42:58.810750Z
-7970
-manuel
-
-tcl.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-59611850f560d8993a943e49a0e4ecba
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-gettext.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-df3e8d25362957e3767419daa901643a
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-tar.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-7aecb2949a3243d33db33476aa12fbee
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-bzip2.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-c7c580681d3b5e3945711212165365a4
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-adjusting.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-1944b450b030173d20f5d3423ad9d147
-2007-10-29T21:41:18.520922Z
-8420
-matthew
-
-changingowner.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-a63dd7ef4c0b32ef430c0c8153175f25
-2007-03-21T18:42:58.810750Z
-7970
-manuel
-
-diffutils.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-45168eab0d2afd73fc947c9d88207a2b
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-gawk.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-354d9dd10a679f46ce90858e3d140656
-2007-12-08T23:42:31.051514Z
-8432
-matthew
-
-chapter05.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-18ed44208fffa0d25b60a2041834c82a
-2008-01-22T07:59:22.828693Z
-8458
-matthew
-
-grep.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-0b3967c22bc726eedb237e7be7197479
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-findutils.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-aac80731b494f49d7302cd87c605f51a
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-perl.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-58553f54fe93feaee25cb869bbae7c01
-2008-02-07T19:47:39.793882Z
-8470
-matthew
-
-linux-headers.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-cf999df5e12f3f6d31c51ed71d77957f
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-gzip.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-8506bcddeb44de7c5514568c38154973
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-texinfo.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-2ca6dab77dd249c201355911efb78268
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-bash.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-6d6204dd8c4a338938c26b99ce248b25
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-stripping.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-33914164daa727e7804ae0c40bcf7287
-2007-03-21T18:42:58.810750Z
-7970
-manuel
-
-glibc.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-ef457f55d15c0bec5efe805aef91e95e
-2008-04-23T18:33:53.240733Z
-8541
-jhuntwork
-
-m4.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-cf97c2499af5236484dffa7b5e425591
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-gcc-pass1.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-f474b237baa9264603b0f545edacffa3
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-gcc-pass2.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-15378dfb2ae379e34f2bd5f75e8ebb7d
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-ncurses.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-144cedea00c677ab9980013878f1a446
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-expect.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-68b0cb8b84b2140a7d8ca187dc1375cd
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-toolchaintechnotes.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-b7e2f8ead3b976a98b5c06f743245f11
-2007-03-21T18:42:58.810750Z
-7970
-manuel
-
-flex.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-c2a9f142453da14490e79a31894ab50a
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-patch.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-6ab046287e2dba4110528a87440bac07
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-coreutils.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-87df0310bfbcfbbb3a9f43367595cdf6
-2008-02-07T19:47:39.793882Z
-8470
-matthew
-
-e2fsprogs.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-048bed5af299b616c60f5c3066358354
-2008-04-22T15:27:23.405895Z
-8527
-jhuntwork
-
-bison.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-2d1189a094c7e813b2997e85807ef524
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-sed.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-a1032afa78dc042d288a89dc0990933b
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-util-linux-ng.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-8265205e4c51630a70fc16260fcd756a
-2008-04-22T15:27:23.405895Z
-8527
-jhuntwork
-
-make.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-33ec175d6f0a50de67c80010134c4f1a
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-dejagnu.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-68ae50d2b9db6874ecaf51b466aca902
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-binutils-pass1.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-cda4770762693a97efc733d5cd5c5192
-2007-12-08T23:46:45.638991Z
-8439
-matthew
-
-binutils-pass2.xml
-file
-
-
-
-
-2008-07-14T23:49:36.000000Z
-e1b24c9c7fbf33fb0e7d5487301edda0
-2007-12-08T23:46:45.638991Z
-8439
-matthew
-
diff -Naur BOOK/chapter05/.svn/format BOOKfr/chapter05/.svn/format
--- BOOK/chapter05/.svn/format	2008-07-15 00:49:34.000000000 +0100
+++ BOOKfr/chapter05/.svn/format	1970-01-01 01:00:00.000000000 +0100
@@ -1 +0,0 @@
-8
diff -Naur BOOK/chapter05/.svn/text-base/adjusting.xml.svn-base BOOKfr/chapter05/.svn/text-base/adjusting.xml.svn-base
--- BOOK/chapter05/.svn/text-base/adjusting.xml.svn-base	2008-07-15 00:49:35.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/adjusting.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,120 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-adjusting">
-  <?dbhtml filename="adjusting.html"?>
-
-  <title>Adjusting the Toolchain</title>
-
-  <para>Now that the temporary C libraries have been installed, all
-  tools compiled in the rest of this chapter should be linked against
-  these libraries. In order to accomplish this, the linker and the
-  compiler's specs file need to be adjusted.</para>
-
-  <para>The linker, adjusted at the end of the first pass of Binutils, needs
-  to be renamed so that it can be properly found and used. First, backup the
-  original linker, then replace it with the adjusted linker. We'll also
-  create a link to its counterpart in <filename class="directory">
-  /tools/$(gcc -dumpmachine)/bin</filename>:</para>
-
-<screen><userinput>mv -v /tools/bin/{ld,ld-old}
-mv -v /tools/$(gcc -dumpmachine)/bin/{ld,ld-old}
-mv -v /tools/bin/{ld-new,ld}
-ln -sv /tools/bin/ld /tools/$(gcc -dumpmachine)/bin/ld</userinput></screen>
-
-  <para>From this point onwards, everything will link only against the
-  libraries in <filename class="directory">/tools/lib</filename>.</para>
-
-  <para>The next task is to point GCC to the new dynamic linker. This is done by
-  dumping GCC's <quote>specs</quote> file to a location where GCC will look for it
-  by default. A simple <command>sed</command> substitution then alters the
-  dynamic linker that GCC will use.</para>
-
-  <para>For the sake of accuracy, it is recommended to use a copy-and-paste
-  method when issuing the following command. Be sure to visually inspect the
-  specs file and verify that all occurrences of <quote>/lib/ld-linux.so.2</quote>
-  have been replaced with <quote>/tools/lib/ld-linux.so.2</quote>:</para>
-
-  <important>
-    <para>If working on a platform where the name of the dynamic linker is
-    something other than <filename class="libraryfile">ld-linux.so.2</filename>,
-    replace <quote>ld-linux.so.2</quote> with the name of the platform's
-    dynamic linker in the following commands. Refer to <xref
-    linkend="ch-tools-toolchaintechnotes" role=","/> if necessary.</para>
-  </important>
-
-<!-- Ampersands are needed to allow copy and paste -->
-<screen><userinput>gcc -dumpspecs | sed 's@/lib/ld-linux.so.2@/tools&amp;@g' \
-  > `dirname $(gcc -print-libgcc-file-name)`/specs</userinput></screen>
-
-  <para>During the build process, GCC runs a script
-  (<command>fixincludes</command>) that scans the system for header files
-  that may need to be fixed (they might contain syntax errors, for example),
-  and installs the fixed versions in a private include directory. There is a
-  possibility that, as a result of this process, some header files from the
-  host system have found their way into GCC's private include directory. As
-  the rest of this chapter only requires the headers from GCC and Glibc,
-  which have both been installed at this point, any <quote>fixed</quote>
-  headers can safely be removed. This helps to avoid any host headers
-  polluting the build environment. Run the following commands to remove the
-  header files in GCC's private include directory (you may find it easier to
-  copy and paste these commands, rather than typing them by hand, due to
-  their length):</para>
-
-<!-- && used to ease copy and pasting -->
-<screen><userinput>GCC_INCLUDEDIR=`dirname $(gcc -print-libgcc-file-name)`/include &amp;&amp;
-find ${GCC_INCLUDEDIR}/* -maxdepth 0 -xtype d -exec rm -rvf '{}' \; &amp;&amp;
-rm -vf `grep -l "DO NOT EDIT THIS FILE" ${GCC_INCLUDEDIR}/*` &amp;&amp;
-unset GCC_INCLUDEDIR</userinput></screen>
-
-  <caution>
-    <para>At this point, it is imperative to stop and ensure that the basic
-    functions (compiling and linking) of the new toolchain are working as
-    expected. To perform a sanity check, run the following commands:</para>
-
-<screen><userinput>echo 'main(){}' &gt; dummy.c
-cc dummy.c
-readelf -l a.out | grep ': /tools'</userinput></screen>
-
-    <para>If everything is working correctly, there should be no errors,
-    and the output of the last command will be of the form:</para>
-
-<screen><computeroutput>[Requesting program interpreter:
-    /tools/lib/ld-linux.so.2]</computeroutput></screen>
-
-    <para>Note that <filename class="directory">/tools/lib</filename>
-    appears as the prefix of the dynamic linker.</para>
-
-    <para>If the output is not shown as above or there was no output at all,
-    then something is wrong. Investigate and retrace the steps to find out
-    where the problem is and correct it. This issue must be resolved before
-    continuing on. First, perform the sanity check again, using
-    <command>gcc</command> instead of <command>cc</command>. If this works,
-    then the <filename class="symlink">/tools/bin/cc</filename> symlink is
-    missing. Revisit <xref linkend="ch-tools-gcc-pass1" role=","/> and install
-    the symlink. Next, ensure that the <envar>PATH</envar> is correct. This
-    can be checked by running <command>echo $PATH</command> and verifying that
-    <filename class="directory">/tools/bin</filename> is at the head of the
-    list. If the <envar>PATH</envar> is wrong it could mean that you are not
-    logged in as user <systemitem class="username">lfs</systemitem> or that
-    something went wrong back in <xref linkend="ch-tools-settingenviron"
-    role="."/> Another option is that something may have gone wrong with the
-    specs file amendment above. In this case, redo the specs file amendment,
-    being careful to copy-and-paste the commands.</para>
-
-    <para>Once all is well, clean up the test files:</para>
-
-<screen><userinput>rm -v dummy.c a.out</userinput></screen>
-
-  </caution>
-
-  <note><para>Building Tcl in the next section will serve as an additional check that
-  the toolchain has been built properly.  If Tcl fails to build, it is an
-  indication that something has gone wrong with the Binutils, GCC, or Glibc
-  installation, but not with Tcl itself.</para></note>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/bash.xml.svn-base BOOKfr/chapter05/.svn/text-base/bash.xml.svn-base
--- BOOK/chapter05/.svn/text-base/bash.xml.svn-base	2008-07-15 00:49:35.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/bash.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,98 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-bash" role="wrap">
-  <?dbhtml filename="bash.html"?>
-
-  <sect1info condition="script">
-    <productname>bash</productname>
-    <productnumber>&bash-version;</productnumber>
-    <address>&bash-url;</address>
-  </sect1info>
-
-  <title>Bash-&bash-version;</title>
-
-  <indexterm zone="ch-tools-bash">
-    <primary sortas="a-Bash">Bash</primary>
-    <secondary>tools</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/bash.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&bash-ch5-sbu;</seg>
-        <seg>&bash-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Bash</title>
-
-    <para>Apply fixes for several bugs discovered since the initial release of
-    Bash-&bash-version;:</para>
-
-<screen><userinput remap="pre">patch -Np1 -i ../&bash-fixes-patch;</userinput></screen>
-
-    <para>Prepare Bash for compilation:</para>
-
-<screen><userinput remap="configure">./configure --prefix=/tools --without-bash-malloc</userinput></screen>
-
-    <variablelist>
-      <title>The meaning of the configure option:</title>
-
-      <varlistentry>
-        <term><parameter>--without-bash-malloc</parameter></term>
-        <listitem>
-          <para>This option turns off the use of Bash's memory allocation
-          (<function>malloc</function>) function which is known to cause
-          segmentation faults. By turning this option off, Bash will use
-          the <function>malloc</function> functions from Glibc which are
-          more stable.</para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-    <para>Compile the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>To test the results, issue:</para>
-
-<screen><userinput remap="test">make tests</userinput></screen>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-    <para>Make a link for the programs that use <command>sh</command> for
-    a shell:</para>
-
-<screen><userinput remap="install">ln -vs bash /tools/bin/sh</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-bash" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/binutils-pass1.xml.svn-base BOOKfr/chapter05/.svn/text-base/binutils-pass1.xml.svn-base
--- BOOK/chapter05/.svn/text-base/binutils-pass1.xml.svn-base	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/binutils-pass1.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,175 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-binutils-pass1" role="wrap">
-  <?dbhtml filename="binutils-pass1.html"?>
-
-  <sect1info condition="script">
-    <productname>binutils</productname>
-    <productnumber>&binutils-version;</productnumber>
-    <address>&binutils-url;</address>
-  </sect1info>
-
-  <title>Binutils-&binutils-version; - Pass 1</title>
-
-  <indexterm zone="ch-tools-binutils-pass1">
-    <primary sortas="a-Binutils">Binutils</primary>
-    <secondary>tools, pass 1</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/binutils.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&binutils-ch5p1-sbu;</seg>
-        <seg>&binutils-ch5p1-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Binutils</title>
-
-    <para>It is important that Binutils be the first package compiled
-    because both Glibc and GCC perform various tests on the available
-    linker and assembler to determine which of their own features to
-    enable.</para>
-
-    <para>Binutils does not recognize versions of Texinfo newer than 4.9.  Fix
-    this issue by applying the following patch:</para>
-
-<screen><userinput remap="pre">patch -Np1 -i ../&binutils-configure-patch;</userinput></screen>
-
-    <para>The Binutils documentation recommends building Binutils outside of the
-    source directory in a dedicated build directory:</para>
-
-<screen><userinput remap="pre">mkdir -v ../binutils-build
-cd ../binutils-build</userinput></screen>
-
-    <note>
-      <para>In order for the SBU values listed in the rest of the book
-      to be of any use, measure the time it takes to build this package from
-      the configuration, up to and including the first install. To achieve
-      this easily, wrap the three commands in a <command>time</command>
-      command like this: <userinput>time { ./configure ... &amp;&amp; make
-      &amp;&amp; make install; }</userinput>.</para>
-    </note>
-
-    <para>Now prepare Binutils for compilation:</para>
-
-<screen><userinput remap="configure">CC="gcc -B/usr/bin/" ../binutils-&binutils-version;/configure \
-    --prefix=/tools --disable-nls --disable-werror</userinput></screen>
-
-    <variablelist>
-      <title>The meaning of the configure options:</title>
-
-      <varlistentry>
-        <term><envar>CC="gcc -B/usr/bin/"</envar></term>
-        <listitem>
-          <para>This forces <command>gcc</command> to prefer the linker from
-          the host in <filename class="directory">/usr/bin</filename>. This
-          is necessary on some hosts where the new <command>ld</command>
-          built here is not compatible with the host's <command>gcc</command>.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><parameter>--prefix=/tools</parameter></term>
-        <listitem>
-          <para>This tells the configure script to prepare to install the
-          Binutils programs in the <filename class="directory">/tools</filename>
-          directory.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><parameter>--disable-nls</parameter></term>
-        <listitem>
-          <para>This disables internationalization as i18n is not needed for the
-          temporary tools.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><parameter>--disable-werror</parameter></term>
-        <listitem>
-          <para>This prevents the build from stopping in the event that there
-          are warnings from the host's compiler.</para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-    <para>Continue with compiling the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>Compilation is now complete. Ordinarily we would now run the
-    test suite, but at this early stage the test suite framework (Tcl,
-    Expect, and DejaGNU) is not yet in place. The benefits of running the
-    tests at this point are minimal since the programs from this
-    first pass will soon be replaced by those from the second.</para>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-    <para>Next, prepare the linker for the <quote>Adjusting</quote> phase
-    later on:</para>
-
-<screen><userinput remap="adjust">make -C ld clean
-make -C ld LIB_PATH=/tools/lib
-cp -v ld/ld-new /tools/bin</userinput></screen>
-
-    <variablelist>
-      <title>The meaning of the make parameters:</title>
-
-      <varlistentry>
-        <term><parameter>-C ld clean</parameter></term>
-        <listitem>
-          <para>This tells the make program to remove all compiled
-          files in the <filename class="directory">ld</filename>
-          subdirectory.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><parameter>-C ld LIB_PATH=/tools/lib</parameter></term>
-        <listitem>
-          <para>This option rebuilds everything in the <filename
-          class="directory">ld</filename> subdirectory. Specifying the
-          <envar>LIB_PATH</envar> Makefile variable on the command line
-          allows us to override the default value and point it to the
-          temporary tools location. The value of this variable specifies
-          the linker's default library search path. This preparation is
-          used later in the chapter.</para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-binutils" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/binutils-pass2.xml.svn-base BOOKfr/chapter05/.svn/text-base/binutils-pass2.xml.svn-base
--- BOOK/chapter05/.svn/text-base/binutils-pass2.xml.svn-base	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/binutils-pass2.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,109 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-binutils-pass2" role="wrap">
-  <?dbhtml filename="binutils-pass2.html"?>
-
-  <sect1info condition="script">
-    <productname>binutils</productname>
-    <productnumber>&binutils-version;</productnumber>
-    <address>&binutils-url;</address>
-  </sect1info>
-
-  <title>Binutils-&binutils-version; - Pass 2</title>
-
-  <indexterm zone="ch-tools-binutils-pass2">
-    <primary sortas="a-Binutils">Binutils</primary>
-    <secondary>tools, pass 2</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/binutils.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&binutils-ch5p2-sbu;</seg>
-        <seg>&binutils-ch5p2-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Re-installation of Binutils</title>
-
-    <para>Binutils does not recognize versions of Texinfo newer than 4.9.  Fix
-    this issue by applying the following patch:</para>
-
-<screen><userinput remap="pre">patch -Np1 -i ../&binutils-configure-patch;</userinput></screen>
-
-    <para>Create a separate build directory again:</para>
-
-<screen><userinput remap="pre">mkdir -v ../binutils-build
-cd ../binutils-build</userinput></screen>
-
-    <para>Prepare Binutils for compilation:</para>
-
-<screen><userinput remap="configure">../binutils-&binutils-version;/configure --prefix=/tools \
-    --disable-nls --with-lib-path=/tools/lib</userinput></screen>
-
-    <variablelist>
-      <title>The meaning of the new configure options:</title>
-
-      <varlistentry>
-        <term><parameter>--with-lib-path=/tools/lib</parameter></term>
-        <listitem>
-          <para>This tells the configure script to specify the library
-          search path during the compilation of Binutils, resulting in
-          <filename class="directory">/tools/lib</filename> being passed
-          to the linker. This prevents the linker from searching through
-          library directories on the host.</para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-    <para>Compile the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>Compilation is now complete. As discussed earlier, running the
-    test suite is not mandatory for the temporary tools here in this
-    chapter. To run the Binutils test suite anyway, issue the following
-    command:</para>
-
-<screen><userinput remap="test">make check</userinput></screen>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-    <para>Now prepare the linker for the <quote>Re-adjusting</quote> phase in
-    the next chapter:</para>
-
-<screen><userinput remap="adjust">make -C ld clean
-make -C ld LIB_PATH=/usr/lib:/lib
-cp -v ld/ld-new /tools/bin</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-binutils" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/bison.xml.svn-base BOOKfr/chapter05/.svn/text-base/bison.xml.svn-base
--- BOOK/chapter05/.svn/text-base/bison.xml.svn-base	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/bison.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,72 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-bison" role="wrap">
-  <?dbhtml filename="bison.html"?>
-
-  <sect1info condition="script">
-    <productname>bison</productname>
-    <productnumber>&bison-version;</productnumber>
-    <address>&bison-url;</address>
-  </sect1info>
-
-  <title>Bison-&bison-version;</title>
-
-  <indexterm zone="ch-tools-bison">
-    <primary sortas="a-Bison">Bison</primary>
-    <secondary>tools</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/bison.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&bison-ch5-sbu;</seg>
-        <seg>&bison-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Bison</title>
-
-    <para>Prepare Bison for compilation:</para>
-
-<screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
-
-    <para>Compile the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>To test the results, issue:</para>
-
-<screen><userinput remap="test">make check</userinput></screen>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-bison" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/bzip2.xml.svn-base BOOKfr/chapter05/.svn/text-base/bzip2.xml.svn-base
--- BOOK/chapter05/.svn/text-base/bzip2.xml.svn-base	2008-07-15 00:49:35.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/bzip2.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,65 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-bzip2" role="wrap">
-  <?dbhtml filename="bzip2.html"?>
-
-  <sect1info condition="script">
-    <productname>bzip2</productname>
-    <productnumber>&bzip2-version;</productnumber>
-    <address>&bzip2-url;</address>
-  </sect1info>
-
-  <title>Bzip2-&bzip2-version;</title>
-
-  <indexterm zone="ch-tools-bzip2">
-    <primary sortas="a-Bzip2">Bzip2</primary>
-    <secondary>tools</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/bzip2.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&bzip2-ch5-sbu;</seg>
-        <seg>&bzip2-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Bzip2</title>
-
-    <para>The Bzip2 package does not contain a <command>configure</command>
-    script. Compile and test it with:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make PREFIX=/tools install</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-bzip2" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/changingowner.xml.svn-base BOOKfr/chapter05/.svn/text-base/changingowner.xml.svn-base
--- BOOK/chapter05/.svn/text-base/changingowner.xml.svn-base	2008-07-15 00:49:35.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/changingowner.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,53 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-changingowner">
-  <?dbhtml filename="changingowner.html"?>
-
-  <title>Changing Ownership</title>
-
-  <note>
-    <para>The commands in the remainder of this book must be performed while
-    logged in as user <systemitem class="username">root</systemitem> and no
-    longer as user <systemitem class="username">lfs</systemitem>. Also, double
-    check that <envar>$LFS</envar> is set in <systemitem
-    class="username">root</systemitem>'s environment.</para>
-  </note>
-
-  <para>Currently, the <filename class="directory">$LFS/tools</filename> directory
-  is owned by the user <systemitem class="username">lfs</systemitem>, a user
-  that exists only on the host system. If the <filename
-  class="directory">$LFS/tools</filename> directory is kept as is, the files are
-  owned by a user ID without a corresponding account. This is dangerous because
-  a user account created later could get this same user ID and would own the
-  <filename class="directory">$LFS/tools</filename> directory and all the files
-  therein, thus exposing these files to possible malicious manipulation.</para>
-
-  <para>To avoid this issue, you could add the <systemitem
-  class="username">lfs</systemitem> user to the new LFS system later when
-  creating the <filename>/etc/passwd</filename> file, taking care to assign it
-  the same user and group IDs as on the host system. Better yet, change the
-  ownership of the <filename class="directory">$LFS/tools</filename> directory to
-  user <systemitem class="username">root</systemitem> by running the following
-  command:</para>
-
-<screen><userinput>chown -R root:root $LFS/tools</userinput></screen>
-
-  <para>Although the <filename class="directory">$LFS/tools</filename> directory
-  can be deleted once the LFS system has been finished, it can be retained to build
-  additional LFS systems <emphasis>of the same book version</emphasis>. How best
-  to backup <filename class="directory">$LFS/tools</filename> is a matter of
-  personal preference and is left as an exercise for the reader.</para>
-
-  <caution>
-    <para>If you intend to keep the temporary tools for use in building future LFS
-    systems, <emphasis>now</emphasis> is the time to back them up. Subsequent
-    commands in chapter 6 will alter the tools currently in place, rendering them
-    useless for future builds.</para>
-  </caution>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/chapter05.xml.svn-base BOOKfr/chapter05/.svn/text-base/chapter05.xml.svn-base
--- BOOK/chapter05/.svn/text-base/chapter05.xml.svn-base	2008-07-15 00:49:35.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/chapter05.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,48 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<chapter id="chapter-temporary-tools" xreflabel="Chapter 5">
-  <?dbhtml dir="chapter05"?>
-  <?dbhtml filename="chapter05.html"?>
-
-  <title>Constructing a Temporary System</title>
-
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="introduction.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="toolchaintechnotes.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="binutils-pass1.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="gcc-pass1.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="linux-headers.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="glibc.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="adjusting.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="tcl.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="expect.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="dejagnu.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="gcc-pass2.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="binutils-pass2.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="ncurses.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="bash.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="bzip2.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="coreutils.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="diffutils.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="e2fsprogs.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="findutils.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="gawk.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="gettext.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="grep.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="gzip.xml"/>
-  <!--<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="m4.xml"/>-->
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="make.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="patch.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="perl.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="sed.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="tar.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="texinfo.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="util-linux-ng.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="stripping.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="changingowner.xml"/>
-
-</chapter>
diff -Naur BOOK/chapter05/.svn/text-base/coreutils.xml.svn-base BOOKfr/chapter05/.svn/text-base/coreutils.xml.svn-base
--- BOOK/chapter05/.svn/text-base/coreutils.xml.svn-base	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/coreutils.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,99 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-coreutils" role="wrap">
-  <?dbhtml filename="coreutils.html"?>
-
-  <sect1info condition="script">
-    <productname>coreutils</productname>
-    <productnumber>&coreutils-version;</productnumber>
-    <address>&coreutils-url;</address>
-  </sect1info>
-
-  <title>Coreutils-&coreutils-version;</title>
-
-  <indexterm zone="ch-tools-coreutils">
-    <primary sortas="a-Coreutils">Coreutils</primary>
-    <secondary>tools</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/coreutils.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&coreutils-ch5-sbu;</seg>
-        <seg>&coreutils-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Coreutils</title>
-
-    <para>Prepare Coreutils for compilation:</para>
-
-<screen><userinput remap="configure">./configure --prefix=/tools --enable-install-program=hostname</userinput></screen>
-
-    <variablelist>
-      <title>The meaning of the configure options:</title>
-
-      <varlistentry>
-        <term><envar>--enable-install-program=hostname</envar></term>
-        <listitem>
-          <para>This enables the <command>hostname</command> binary to be built
-          and installed &ndash; it is disabled by default but is required by the
-          Perl test suite.</para>
-        </listitem>
-      </varlistentry>
-    </variablelist>
-
-    <para>Compile the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>To test the results, issue:</para>
-
-<screen><userinput remap="test">make RUN_EXPENSIVE_TESTS=yes check</userinput></screen>
-
-    <para>The <parameter>RUN_EXPENSIVE_TESTS=yes</parameter> parameter tells the
-    test suite to run several additional tests that are considered
-    relatively expensive (in terms of CPU power and memory usage) on some
-    platforms, but generally are not a problem on Linux.</para>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-    <para>The above command refuses to install <filename>su</filename>
-    because it cannot install it setuid root as a non-privileged user. By
-    manually installing it with a different name, we can use it for running
-    tests in the final system as a non-privileged user and we keep a possibly
-    useful <command>su</command> from our host first place in our PATH. Install
-    it with:</para>
-
-<screen><userinput remap="install">cp -v src/su /tools/bin/su-tools</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-coreutils" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/dejagnu.xml.svn-base BOOKfr/chapter05/.svn/text-base/dejagnu.xml.svn-base
--- BOOK/chapter05/.svn/text-base/dejagnu.xml.svn-base	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/dejagnu.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,90 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-dejagnu" role="wrap">
-  <?dbhtml filename="dejagnu.html"?>
-
-  <sect1info condition="script">
-    <productname>dejagnu</productname>
-    <productnumber>&dejagnu-version;</productnumber>
-    <address>&dejagnu-url;</address>
-  </sect1info>
-
-  <title>DejaGNU-&dejagnu-version;</title>
-
-  <indexterm zone="ch-tools-dejagnu">
-    <primary sortas="a-DejaGNU">DejaGNU</primary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <para>The DejaGNU package contains a framework for testing other
-    programs.</para>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&dejagnu-ch5-sbu;</seg>
-        <seg>&dejagnu-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of DejaGNU</title>
-
-    <para>Prepare DejaGNU for compilation:</para>
-
-<screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
-
-    <para>Build and install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-    <para>To test the results, issue:</para>
-
-<screen><userinput remap="test">make check</userinput></screen>
-
-  </sect2>
-
-
-  <sect2 id="contents-dejagnu" role="content">
-    <title>Contents of DejaGNU</title>
-
-    <segmentedlist>
-      <segtitle>Installed program</segtitle>
-
-      <seglistitem>
-        <seg>runtest</seg>
-      </seglistitem>
-    </segmentedlist>
-
-    <variablelist>
-      <bridgehead renderas="sect3">Short Descriptions</bridgehead>
-      <?dbfo list-presentation="list"?>
-      <?dbhtml list-presentation="table"?>
-
-      <varlistentry id="runtest">
-        <term><command>runtest</command></term>
-        <listitem>
-          <para>A wrapper script that locates the proper
-          <command>expect</command> shell and then runs DejaGNU</para>
-          <indexterm zone="ch-tools-dejagnu runtest">
-            <primary sortas="b-runtest">runtest</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/diffutils.xml.svn-base BOOKfr/chapter05/.svn/text-base/diffutils.xml.svn-base
--- BOOK/chapter05/.svn/text-base/diffutils.xml.svn-base	2008-07-15 00:49:35.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/diffutils.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,70 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-diffutils" role="wrap">
-  <?dbhtml filename="diffutils.html"?>
-
-  <sect1info condition="script">
-    <productname>diffutils</productname>
-    <productnumber>&diffutils-version;</productnumber>
-    <address>&diffutils-url;</address>
-  </sect1info>
-
-  <title>Diffutils-&diffutils-version;</title>
-
-  <indexterm zone="ch-tools-diffutils">
-    <primary sortas="a-Diffutils">Diffutils</primary>
-    <secondary>tools</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/diffutils.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&diffutils-ch5-sbu;</seg>
-        <seg>&diffutils-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Diffutils</title>
-
-    <para>Prepare Diffutils for compilation:</para>
-
-<screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
-
-    <para>Compile the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>This package does not come with a test suite.</para>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-diffutils" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/e2fsprogs.xml.svn-base BOOKfr/chapter05/.svn/text-base/e2fsprogs.xml.svn-base
--- BOOK/chapter05/.svn/text-base/e2fsprogs.xml.svn-base	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/e2fsprogs.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,72 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-e2fsprogs" role="wrap">
-  <?dbhtml filename="e2fsprogs.html"?>
-
-  <sect1info condition="script">
-    <productname>e2fsprogs</productname>
-    <productnumber>&e2fsprogs-version;</productnumber>
-    <address>&e2fsprogs-url;</address>
-  </sect1info>
-
-  <title>E2fsprogs-&e2fsprogs-version;</title>
-
-  <indexterm zone="ch-tools-e2fsprogs">
-    <primary sortas="a-E2fsprogs">E2fsprogs</primary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/e2fsprogs.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&e2fsprogs-ch5-sbu;</seg>
-        <seg>&e2fsprogs-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of E2fsprogs</title>
-
-    <para>The E2fsprogs documentation recommends that the package be built in
-    a subdirectory of the source tree: </para>
-
-<screen><userinput remap="pre">mkdir -v build
-cd build</userinput></screen>
-
-    <para>Prepare E2fsprogs for compilation:</para>
-
-<screen><userinput remap="configure">../configure --prefix=/tools</userinput></screen>
-
-    <para>Compile the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>Install the static libraries and headers required by Util-linux-ng:</para>
-
-<screen><userinput remap="install">make install-libs</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-e2fsprogs" role="."/></para>
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/expect.xml.svn-base BOOKfr/chapter05/.svn/text-base/expect.xml.svn-base
--- BOOK/chapter05/.svn/text-base/expect.xml.svn-base	2008-07-15 00:49:35.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/expect.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,172 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-expect" role="wrap">
-  <?dbhtml filename="expect.html"?>
-
-  <sect1info condition="script">
-    <productname>expect</productname>
-    <productnumber>&expect-version;</productnumber>
-    <address>&expect-url;</address>
-  </sect1info>
-
-  <title>Expect-&expect-version;</title>
-
-  <indexterm zone="ch-tools-expect">
-    <primary sortas="a-Expect">Expect</primary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <para>The Expect package contains a program for carrying out scripted
-    dialogues with other interactive programs.</para>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&expect-ch5-sbu;</seg>
-        <seg>&expect-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Expect</title>
-
-    <para>First, fix a bug that can result in false failures during the GCC test
-    suite run:</para>
-
-<screen><userinput remap="pre">patch -Np1 -i ../&expect-spawn-patch;</userinput></screen>
-
-    <para>Next, force Expect's configure script to use <filename>/bin/stty</filename>
-    instead of a <filename>/usr/local/bin/stty</filename> it may find on the host system.
-    This will ensure that our testsuite tools remain sane for the final builds of our
-    toolchain:</para>
-
-<screen><userinput remap="pre">cp configure{,.bak}
-sed 's:/usr/local/bin:/bin:' configure.bak &gt; configure</userinput></screen>
-
-    <para>Now prepare Expect for compilation:</para>
-
-<screen><userinput remap="configure">./configure --prefix=/tools --with-tcl=/tools/lib \
-  --with-tclinclude=/tools/include --with-x=no</userinput></screen>
-
-    <variablelist>
-      <title>The meaning of the configure options:</title>
-
-      <varlistentry>
-        <term><parameter>--with-tcl=/tools/lib</parameter></term>
-        <listitem>
-          <para>This ensures that the configure script finds the Tcl
-          installation in the temporary tools location instead of possibly
-          locating an existing one on the host system.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><parameter>--with-tclinclude=/tools/include</parameter></term>
-        <listitem>
-          <para>This explicitly tells Expect where to find Tcl's internal
-          headers. Using this option avoids conditions where
-          <command>configure</command> fails because it cannot automatically
-          discover the location of Tcl's headers.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><parameter>--with-x=no</parameter></term>
-        <listitem>
-          <para>This tells the configure script not to search for Tk (the
-          Tcl GUI component) or the X Window System libraries, both of which
-          may reside on the host system but will not exist in the temporary
-          environment.</para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-    <para>Build the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>To test the results, issue:</para>
-
-<screen><userinput remap="test">make test</userinput></screen>
-
-    <para>Note that the Expect test suite is known to experience failures under
-    certain host conditions that are not within our control. Therefore,
-    test suite failures here are not surprising and are not considered
-    critical.</para>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make SCRIPTS="" install</userinput></screen>
-
-    <variablelist>
-      <title>The meaning of the make parameter:</title>
-
-      <varlistentry>
-        <term><parameter>SCRIPTS=""</parameter></term>
-        <listitem>
-          <para>This prevents installation of the supplementary Expect
-          scripts, which are not needed.</para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-  </sect2>
-
-  <sect2 id="contents-expect" role="content">
-    <title>Contents of Expect</title>
-
-    <segmentedlist>
-      <segtitle>Installed program</segtitle>
-      <segtitle>Installed library</segtitle>
-
-      <seglistitem>
-        <seg>expect</seg>
-        <seg>libexpect-&expect-lib-version;.a</seg>
-      </seglistitem>
-    </segmentedlist>
-
-    <variablelist>
-      <bridgehead renderas="sect3">Short Descriptions</bridgehead>
-      <?dbfo list-presentation="list"?>
-      <?dbhtml list-presentation="table"?>
-
-      <varlistentry id="expect">
-        <term><command>expect</command></term>
-        <listitem>
-          <para>Communicates with other interactive programs according
-          to a script</para>
-          <indexterm zone="ch-tools-expect expect">
-            <primary sortas="b-expect">expect</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="libexpect">
-        <term><filename class="libraryfile">libexpect-&expect-lib-version;.a</filename></term>
-        <listitem>
-          <para>Contains functions that allow Expect to be used as a Tcl
-          extension or to be used directly from C or C++ (without Tcl)</para>
-          <indexterm zone="ch-tools-expect libexpect">
-            <primary sortas="c-libexpect-&expect-lib-version;">libexpect-&expect-lib-version;</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/findutils.xml.svn-base BOOKfr/chapter05/.svn/text-base/findutils.xml.svn-base
--- BOOK/chapter05/.svn/text-base/findutils.xml.svn-base	2008-07-15 00:49:35.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/findutils.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,72 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-findutils" role="wrap">
-  <?dbhtml filename="findutils.html"?>
-
-  <sect1info condition="script">
-    <productname>findutils</productname>
-    <productnumber>&findutils-version;</productnumber>
-    <address>&findutils-url;</address>
-  </sect1info>
-
-  <title>Findutils-&findutils-version;</title>
-
-  <indexterm zone="ch-tools-findutils">
-    <primary sortas="a-Findutils">Findutils</primary>
-    <secondary>tools</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/findutils.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&findutils-ch5-sbu;</seg>
-        <seg>&findutils-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Findutils</title>
-
-    <para>Prepare Findutils for compilation:</para>
-
-<screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
-
-    <para>Compile the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>To test the results, issue:</para>
-
-<screen><userinput remap="test">make check</userinput></screen>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-findutils" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/flex.xml.svn-base BOOKfr/chapter05/.svn/text-base/flex.xml.svn-base
--- BOOK/chapter05/.svn/text-base/flex.xml.svn-base	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/flex.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,84 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-flex" role="wrap">
-  <?dbhtml filename="flex.html"?>
-
-  <sect1info condition="script">
-    <productname>flex</productname>
-    <productnumber>&flex-version;</productnumber>
-    <address>&flex-url;</address>
-  </sect1info>
-
-  <title>Flex-&flex-version;</title>
-
-  <indexterm zone="ch-tools-flex">
-    <primary sortas="a-Flex">Flex</primary>
-    <secondary>tools</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/flex.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&flex-ch5-sbu;</seg>
-        <seg>&flex-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Flex</title>
-
-    <para>Flex contains several known bugs. These can be fixed with the
-    following patch:</para>
-
-<screen><userinput remap="pre">patch -Np1 -i ../&flex-fixes-patch;</userinput></screen>
-
-    <para>The GNU autotools will detect that the Flex source code has been
-    modified by the previous patch and tries to update the man page
-    accordingly.  This does not work on many systems, and the default page is
-    fine, so make sure it does not get regenerated:</para>
-
-<screen><userinput remap="pre">touch doc/flex.1</userinput></screen>
-
-    <para>Now prepare Flex for compilation:</para>
-
-<screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
-
-    <para>Compile the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>To test the results, issue:</para>
-
-<screen><userinput remap="test">make check</userinput></screen>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-flex" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/gawk.xml.svn-base BOOKfr/chapter05/.svn/text-base/gawk.xml.svn-base
--- BOOK/chapter05/.svn/text-base/gawk.xml.svn-base	2008-07-15 00:49:35.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/gawk.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,72 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-gawk" role="wrap">
-  <?dbhtml filename="gawk.html"?>
-
-  <sect1info condition="script">
-    <productname>gawk</productname>
-    <productnumber>&gawk-version;</productnumber>
-    <address>&gawk-url;</address>
-  </sect1info>
-
-  <title>Gawk-&gawk-version;</title>
-
-  <indexterm zone="ch-tools-gawk">
-    <primary sortas="a-Gawk">Gawk</primary>
-    <secondary>tools</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/gawk.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&gawk-ch5-sbu;</seg>
-        <seg>&gawk-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Gawk</title>
-
-    <para>Prepare Gawk for compilation:</para>
-
-<screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
-
-    <para>Compile the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>To test the results, issue:</para>
-
-<screen><userinput remap="test">make check</userinput></screen>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-gawk" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/gcc-pass1.xml.svn-base BOOKfr/chapter05/.svn/text-base/gcc-pass1.xml.svn-base
--- BOOK/chapter05/.svn/text-base/gcc-pass1.xml.svn-base	2008-07-15 00:49:35.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/gcc-pass1.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,143 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-gcc-pass1" role="wrap">
-  <?dbhtml filename="gcc-pass1.html"?>
-
-  <sect1info condition="script">
-    <productname>gcc</productname>
-    <productnumber>&gcc-version;</productnumber>
-    <address>&gcc-url;</address>
-  </sect1info>
-
-  <title>GCC-&gcc-version; - Pass 1</title>
-
-  <indexterm zone="ch-tools-gcc-pass1">
-    <primary sortas="a-GCC">GCC</primary>
-    <secondary>tools, pass 1</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/gcc.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&gcc-ch5p1-sbu;</seg>
-        <seg>&gcc-ch5p1-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of GCC</title>
-
-    <para>The GCC documentation recommends building GCC outside of the
-    source directory in a dedicated build directory:</para>
-
-<screen><userinput remap="pre">mkdir -v ../gcc-build
-cd ../gcc-build</userinput></screen>
-
-    <para>Prepare GCC for compilation:</para>
-
-<screen><userinput remap="configure">CC="gcc -B/usr/bin/" ../gcc-&gcc-version;/configure --prefix=/tools \
-    --with-local-prefix=/tools --disable-nls --enable-shared \
-    --enable-languages=c</userinput></screen>
-
-    <variablelist>
-      <title>The meaning of the configure options:</title>
-
-      <varlistentry>
-        <term><envar>CC="gcc -B/usr/bin/"</envar></term>
-        <listitem>
-          <para>This forces <command>gcc</command> to prefer the linker from
-          the host in <filename class="directory">/usr/bin</filename>. This
-          is necessary on some hosts where the new <command>ld</command>
-          built in the previous section is not compatible with the host's
-          <command>gcc</command>.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><parameter>--with-local-prefix=/tools</parameter></term>
-        <listitem>
-          <para>The purpose of this switch is to remove <filename
-          class="directory">/usr/local/include</filename> from
-          <command>gcc</command>'s include search path. This is not
-          absolutely essential, however, it helps to minimize the
-          influence of the host system.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><parameter>--enable-shared</parameter></term>
-        <listitem>
-          <para>This switch allows the building of <filename
-          class="libraryfile">libgcc_s.so.1</filename> and
-          <filename class="libraryfile">libgcc_eh.a</filename>.
-          Having <filename class="libraryfile">libgcc_eh.a</filename>
-          available ensures that the configure script for Glibc (the
-          next package we compile) produces the proper results.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><parameter>--enable-languages=c</parameter></term>
-        <listitem>
-          <para>This option ensures that only the C compiler is built.</para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-    <para>The following command will compile GCC not once, but several times. It
-    uses the programs compiled in a first round to compile itself a second time,
-    and then again a third time. It then compares these second and third compiles
-    to make sure it can reproduce itself flawlessly. This is called
-    <quote>bootstrapping</quote>. Building GCC in this way ensures that it was
-    compiled correctly and is now the default configuration for the released
-    package. Continue with compiling by running:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>Compilation is now complete. At this point, the test suite would
-    normally be run, but, as mentioned before, the test suite framework is
-    not in place yet. The benefits of running the tests at this point
-    are minimal since the programs from this first pass will soon be
-    replaced.</para>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-    <para>As a finishing touch, create a symlink. Many programs and scripts
-    run <command>cc</command> instead of <command>gcc</command>, which is
-    used to keep programs generic and therefore usable on all kinds of UNIX
-    systems where the GNU C compiler is not always installed. Running
-    <command>cc</command> leaves the system administrator free to decide
-    which C compiler to install:</para>
-
-<screen><userinput remap="install">ln -vs gcc /tools/bin/cc</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-gcc" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/gcc-pass2.xml.svn-base BOOKfr/chapter05/.svn/text-base/gcc-pass2.xml.svn-base
--- BOOK/chapter05/.svn/text-base/gcc-pass2.xml.svn-base	2008-07-15 00:49:35.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/gcc-pass2.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,247 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-gcc-pass2" role="wrap">
-  <?dbhtml filename="gcc-pass2.html"?>
-
-  <sect1info condition="script">
-    <productname>gcc</productname>
-    <productnumber>&gcc-version;</productnumber>
-    <address>&gcc-url;</address>
-  </sect1info>
-
-  <title>GCC-&gcc-version; - Pass 2</title>
-
-  <indexterm zone="ch-tools-gcc-pass2">
-    <primary sortas="a-GCC">GCC</primary>
-    <secondary>tools, pass 2</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/gcc.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&gcc-ch5p2-sbu;</seg>
-        <seg>&gcc-ch5p2-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Re-installation of GCC</title>
-
-    <para>The tools required to test GCC and Binutils&mdash;Tcl, Expect
-    and DejaGNU&mdash;are installed now. GCC and Binutils can now be
-    rebuilt, linking them against the new Glibc and testing them properly
-    (if running the test suites in this chapter). Please note that these
-    test suites are highly dependent on properly functioning PTYs which
-    are provided by the host. PTYs are most commonly implemented via the
-    <systemitem class="filesystem">devpts</systemitem> file system. Check
-    to see if the host system is set up correctly in this regard by
-    performing a quick test:</para>
-
-<screen><userinput remap="test">expect -c "spawn ls"</userinput></screen>
-
-    <para>The response might be:</para>
-
-<screen><computeroutput>The system has no more ptys.
-Ask your system administrator to create more.</computeroutput></screen>
-
-    <para>If the above message is received, the host does not have its PTYs
-    set up properly. In this case, there is no point in running the test
-    suites for GCC and Binutils until this issue is resolved. Please consult
-    the LFS FAQ at <ulink url="&lfs-root;/lfs/faq.html#no-ptys"/> for more
-    information on how to get PTYs working.</para>
-
-    <para>As previously explained in <xref linkend="ch-tools-adjusting"/>,
-    under normal circumstances the GCC <command>fixincludes</command> script
-    is run in order to fix potentially broken header files. As GCC-&gcc-version;
-    and Glibc-&glibc-version; have already been installed at this point, and
-    their respective header files are known to not require fixing, the
-    <command>fixincludes</command> script is not required. As mentioned
-    previously, the script may in fact pollute the build environment by
-    installing fixed headers from the host system into GCC's private include
-    directory. The running of the <command>fixincludes</command> script can
-    be suppressed by issuing the following commands:</para>
-
-<screen><userinput remap="pre">cp -v gcc/Makefile.in{,.orig}
-sed 's@\./fixinc\.sh@-c true@' gcc/Makefile.in.orig &gt; gcc/Makefile.in</userinput></screen>
-
-    <para>The bootstrap build performed in <xref linkend="ch-tools-gcc-pass1"/>
-    built GCC with the <option>-fomit-frame-pointer</option> compiler flag.
-    Non-bootstrap builds omit this flag by default, so apply the following
-    <command>sed</command> to use it in order to ensure consistent compiler
-    builds:</para>
-
-<screen><userinput remap="pre">cp -v gcc/Makefile.in{,.tmp}
-sed 's/^XCFLAGS =$/&amp; -fomit-frame-pointer/' gcc/Makefile.in.tmp \
-  &gt; gcc/Makefile.in</userinput></screen>
-
-    <para>The following command will change the location of GCC's default
-    dynamic linker to use the one we installed in
-    <filename class="directory">/tools</filename>. It also removes <filename
-    class="directory">/usr/include</filename> from GCC's include search path.
-    Doing this now rather than adjusting the specs file after installation
-    ensures that the new dynamic linker is used during the actual build of
-    GCC. That is, all of the binaries created during the build will link
-    against the new Glibc. Issue:</para>
-
-<screen><userinput remap="pre">for file in $(find gcc/config -name linux64.h -o -name linux.h)
-do
-  cp -uv $file{,.orig}
-  sed -e 's@/lib\(64\)\?\(32\)\?/ld@/tools&amp;@g' \
-  -e 's@/usr@/tools@g' $file.orig &gt; $file
-  echo "
-#undef STANDARD_INCLUDE_DIR
-#define STANDARD_INCLUDE_DIR 0" &gt;&gt; $file
-  touch $file.orig
-done</userinput></screen>
-
-    <para>In case the above seems hard to follow, let's break it down a bit.
-    First we find all the files under the gcc/config directory that are named
-    either <filename>linux.h</filename> or <filename>linux64.h</filename>.
-    For each file found, we copy it to a file of the same name but with an added
-    suffix of <quote>.orig</quote>. Then the first sed expression prepends
-    <quote>/tools</quote> to every instance of <quote>/lib/ld</quote>,
-    <quote>/lib64/ld</quote> or <quote>/lib32/ld</quote>, while the second one
-    replaces hard-coded instances of <quote>/usr</quote>. Then we add our define
-    statements which alter the include search path to the end of the file. Finally,
-    we use <command>touch</command> to update the timestamp on the copied files.
-    When used in conjunction with <command>cp -u</command>, this prevents unexpected
-    changes to the original files in case the command is inadvertently run twice.
-    </para>
-
-    <para>Create a separate build directory again:</para>
-
-<screen><userinput remap="pre">mkdir -v ../gcc-build
-cd ../gcc-build</userinput></screen>
-
-    <para>Before starting to build GCC, remember to unset any environment
-    variables that override the default optimization flags.</para>
-
-    <para>Now prepare GCC for compilation:</para>
-
-<screen><userinput remap="configure">../gcc-&gcc-version;/configure --prefix=/tools \
-    --with-local-prefix=/tools --enable-clocale=gnu \
-    --enable-shared --enable-threads=posix \
-    --enable-__cxa_atexit --enable-languages=c,c++ \
-    --disable-libstdcxx-pch --disable-bootstrap</userinput></screen>
-
-    <variablelist>
-      <title>The meaning of the new configure options:</title>
-
-      <varlistentry>
-        <term><parameter>--enable-clocale=gnu</parameter></term>
-        <listitem>
-          <para>This option ensures the correct locale model is selected
-          for the C++ libraries under all circumstances. If the configure
-          script finds the <emphasis>de_DE</emphasis> locale installed,
-          it will select the correct gnu locale model. However, if the
-          <emphasis>de_DE</emphasis> locale is not installed, there is the
-          risk of building Application Binary Interface (ABI)-incompatible
-          C++ libraries because the incorrect generic locale model may be
-          selected.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><parameter>--enable-threads=posix</parameter></term>
-        <listitem>
-          <para>This enables C++ exception handling for multi-threaded code.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><parameter>--enable-__cxa_atexit</parameter></term>
-        <listitem>
-          <para>This option allows use of <function>__cxa_atexit</function>,
-          rather than <function>atexit</function>, to register C++ destructors
-          for local statics and global objects. This option is essential for
-          fully standards-compliant handling of destructors. It also affects
-          the C++ ABI, and therefore results in C++ shared libraries and C++
-          programs that are interoperable with other Linux distributions.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><parameter>--enable-languages=c,c++</parameter></term>
-        <listitem>
-          <para>This option ensures that both the C and C++ compilers are
-          built.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><parameter>--disable-libstdcxx-pch</parameter></term>
-        <listitem>
-          <para>Do not build the pre-compiled header (PCH) for
-          <filename class="libraryfile">libstdc++</filename>. It takes up a
-          lot of space, and we have no use for it.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><parameter>--disable-bootstrap</parameter></term>
-        <listitem>
-          <para>Bootstrapping the compiler is now the default for GCC. However,
-	  our build method should provide us with a solid compiler without the
-	  need to bootstrap each time.</para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-    <para>Compile the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>There is no need to use the <parameter>bootstrap</parameter> target
-    now because the compiler being used to compile this GCC was built from
-    the exact same version of the GCC sources used earlier.</para>
-
-    <para>Compilation is now complete. As previously mentioned, running the test
-    suites for the temporary tools compiled in this chapter is not mandatory.
-    To run the GCC test suite anyway, use the following command:</para>
-
-<screen><userinput remap="test">make -k check</userinput></screen>
-
-    <para>The <parameter>-k</parameter> flag is used to make the test suite run
-    through to completion and not stop at the first failure. The GCC test
-    suite is very comprehensive and is almost guaranteed to generate a few
-    failures.</para>
-
-    <para>For a discussion of test failures that are of particular
-    importance, please see <xref linkend="ch-system-gcc" role="."/></para>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="adjusting.xml"
-    xpointer="xpointer(/sect1/caution[1])"/>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-gcc" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/gettext.xml.svn-base BOOKfr/chapter05/.svn/text-base/gettext.xml.svn-base
--- BOOK/chapter05/.svn/text-base/gettext.xml.svn-base	2008-07-15 00:49:34.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/gettext.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,91 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-gettext" role="wrap">
-  <?dbhtml filename="gettext.html"?>
-
-  <sect1info condition="script">
-    <productname>gettext</productname>
-    <productnumber>&gettext-version;</productnumber>
-    <address>&gettext-url;</address>
-  </sect1info>
-
-  <title>Gettext-&gettext-version;</title>
-
-  <indexterm zone="ch-tools-gettext">
-    <primary sortas="a-Gettext">Gettext</primary>
-    <secondary>tools</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/gettext.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&gettext-ch5-sbu;</seg>
-        <seg>&gettext-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Gettext</title>
-
-    <para>For our temporary set of tools, we only need to build and install
-    one binary from Gettext.</para>
-
-    <para>Prepare Gettext for compilation:</para>
-
-<screen><userinput remap="configure">cd gettext-tools
-./configure --prefix=/tools --disable-shared</userinput></screen>
-
-    <variablelist>
-      <title>The meaning of the configure option:</title>
-
-      <varlistentry>
-        <term><parameter>--disable-shared</parameter></term>
-        <listitem>
-          <para>We do not need to install any of the shared Gettext libraries at
-          this time, therefore there is no need to build them.</para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-    <para>Compile the package:</para>
-
-<screen><userinput remap="make">make -C gnulib-lib
-make -C src msgfmt</userinput></screen>
-
-    <para>As only one binary has been compiled, it is not possible to run the
-    testsuite without compiling additional support libraries from the Gettext
-    package. It is therefore not recommended to attempt to run the testsuite at
-    this stage.</para>
-
-    <para>Install the <command>msgfmt</command> binary:</para>
-
-<screen><userinput remap="install">cp -v src/msgfmt /tools/bin</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-gettext" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/glibc.xml.svn-base BOOKfr/chapter05/.svn/text-base/glibc.xml.svn-base
--- BOOK/chapter05/.svn/text-base/glibc.xml.svn-base	2008-07-15 00:49:35.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/glibc.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,220 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-glibc" role="wrap">
-  <?dbhtml filename="glibc.html"?>
-
-  <sect1info condition="script">
-    <productname>glibc</productname>
-    <productnumber>&glibc-version;</productnumber>
-    <address>&glibc-url;</address>
-  </sect1info>
-
-  <title>Glibc-&glibc-version;</title>
-
-  <indexterm zone="ch-tools-glibc">
-    <primary sortas="a-Glibc">Glibc</primary>
-    <secondary>tools</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/glibc.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&glibc-ch5-sbu;</seg>
-        <seg>&glibc-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Glibc</title>
-
-    <para>The Glibc documentation recommends building Glibc outside of the source
-    directory in a dedicated build directory:</para>
-
-<screen><userinput remap="pre">mkdir -v ../glibc-build
-cd ../glibc-build</userinput></screen>
-
-    <para>Because Glibc no longer supports i386, its developers say to use the
-    compiler flag <parameter>-march=i486</parameter> when building it for x86
-    machines. There are several ways to accomplish that, but testing shows that
-    the flag is best placed inside the build variable <quote>CFLAGS</quote>.
-    Instead of overriding completely what Glibc's internal build system uses
-    for CFLAGS, append the new flag to the existing contents of CFLAGS by
-    making use of the special file <filename>configparms</filename>. The
-    -mtune=native flag is also necessary to reset a reasonable value for -mtune
-    that is changed when setting -march.</para>
-
-<screen><userinput remap="configure">echo "CFLAGS += -march=i486 -mtune=native" &gt; configparms</userinput></screen>
-
-    <para>Next, prepare Glibc for compilation:</para>
-
-<screen><userinput remap="configure">../glibc-&glibc-version;/configure --prefix=/tools \
-    --disable-profile --enable-add-ons \
-    --enable-kernel=2.6.0 --with-binutils=/tools/bin \
-    --without-gd --with-headers=/tools/include \
-    --without-selinux</userinput></screen>
-
-    <variablelist>
-      <title>The meaning of the configure options:</title>
-
-      <varlistentry>
-        <term><parameter>--disable-profile</parameter></term>
-        <listitem>
-          <para>This builds the libraries without profiling information. Omit
-          this option if profiling on the temporary tools is necessary.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><parameter>--enable-add-ons</parameter></term>
-        <listitem>
-          <para>This tells Glibc to use the NPTL add-on as its threading
-          library.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><parameter>--enable-kernel=2.6.0</parameter></term>
-        <listitem>
-          <para>This tells Glibc to compile the library with support
-          for 2.6.x Linux kernels.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><parameter>--with-binutils=/tools/bin</parameter></term>
-        <listitem>
-          <para>While not required, this switch ensures that there are
-          no errors pertaining to which Binutils programs get used during the
-          Glibc build.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><parameter>--without-gd</parameter></term>
-        <listitem>
-          <para>This prevents the build of the <command>memusagestat</command>
-          program, which insists on linking against the host's libraries
-          (libgd, libpng, libz, etc.).</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><parameter>--with-headers=/tools/include</parameter></term>
-        <listitem>
-          <para>This tells Glibc to compile itself against the headers recently
-          installed to the tools directory, so that it knows exactly what
-          features the kernel has and can optimize itself accordingly.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><parameter>--without-selinux</parameter></term>
-        <listitem>
-          <para>When building from hosts that include SELinux functionality
-          (e.g., Fedora Core 3), Glibc will build with support for SELinux.
-          As the LFS tools environment does not contain support for SELinux, a
-          Glibc compiled with such support will fail to operate correctly.</para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-    <para>During this stage the following warning might appear:</para>
-
-    <blockquote>
-<screen><computeroutput>configure: WARNING:
-*** These auxiliary programs are missing or
-*** incompatible versions: msgfmt
-*** some features will be disabled.
-*** Check the INSTALL file for required versions.</computeroutput></screen>
-    </blockquote>
-
-    <para>The missing or incompatible <command>msgfmt</command> program is
-    generally harmless, but it can sometimes cause issues when running the
-    test suite. This <command>msgfmt</command> program is part of the
-    Gettext package which the host distribution should provide. If
-    <command>msgfmt</command> is present but deemed incompatible, upgrade
-    the host system's Gettext package or continue without it and see if
-    the test suite runs without problems regardless.</para>
-
-    <para>Compile the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>Compilation is now complete. As mentioned earlier, running the
-    test suites for the temporary tools installed in this chapter is not
-    mandatory. To run the Glibc test suite (if desired), the following
-    command will do so:</para>
-
-<screen><userinput remap="test">make check</userinput></screen>
-
-    <para>For a discussion of test failures that are of particular
-    importance, please see <xref linkend="ch-system-glibc" role="."/></para>
-
-    <para>In this chapter, some tests can be adversely affected by
-    existing tools or environmental issues on the host system. Glibc test
-    suite failures in this chapter are typically not worrisome. The Glibc
-    installed in <xref linkend="chapter-building-system"/> is the one that
-    will ultimately end up being used, so that is the one that needs to pass
-    most tests (even in <xref linkend="chapter-building-system"/>, some
-    failures could still occur, for example, with the math tests).</para>
-
-    <para>When experiencing a failure, make a note of it, then continue by
-    reissuing the <command>make check</command> command. The test suite
-    should pick up where it left off and continue. This stop-start sequence
-    can be circumvented by issuing a <command>make -k check</command> command.
-    If using this option, be sure to log the output so that the log file can
-    be examined for failures later.</para>
-
-    <para>The install stage of Glibc will issue a harmless warning at the
-    end about the absence of <filename>/tools/etc/ld.so.conf</filename>.
-    Prevent this warning with:</para>
-
-<screen><userinput remap="install">mkdir -v /tools/etc
-touch /tools/etc/ld.so.conf</userinput></screen>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-    <para>Different countries and cultures have varying conventions for
-    how to communicate. These conventions range from the format for
-    representing dates and times to more complex issues, such as the
-    language spoken. The <quote>internationalization</quote> of GNU
-    programs works by locale.</para>
-
-    <note>
-      <para>If the test suites are not being run in this chapter (as per
-      the recommendation), there is no need to install the locales now.
-      The appropriate locales will be installed in the next chapter.
-      To install the Glibc locales anyway, use instructions from
-      <xref linkend="ch-system-glibc" role="."/></para>
-    </note>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-glibc" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/grep.xml.svn-base BOOKfr/chapter05/.svn/text-base/grep.xml.svn-base
--- BOOK/chapter05/.svn/text-base/grep.xml.svn-base	2008-07-15 00:49:35.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/grep.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,88 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-grep" role="wrap">
-  <?dbhtml filename="grep.html"?>
-
-  <sect1info condition="script">
-    <productname>grep</productname>
-    <productnumber>&grep-version;</productnumber>
-    <address>&grep-url;</address>
-  </sect1info>
-
-  <title>Grep-&grep-version;</title>
-
-  <indexterm zone="ch-tools-grep">
-    <primary sortas="a-Grep">Grep</primary>
-    <secondary>tools</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/grep.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&grep-ch5-sbu;</seg>
-        <seg>&grep-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Grep</title>
-
-    <para>Prepare Grep for compilation:</para>
-
-<screen><userinput remap="configure">./configure --prefix=/tools \
-    --disable-perl-regexp</userinput></screen>
-
-    <variablelist>
-      <title>The meaning of the configure option:</title>
-
-      <varlistentry>
-        <term><parameter>--disable-perl-regexp</parameter></term>
-        <listitem>
-          <para>This ensures that the <command>grep</command> program does
-          not get linked against a Perl Compatible Regular Expression (PCRE)
-          library that may be present on the host but will not be available
-          once we enter the <command>chroot</command> environment.</para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-    <para>Compile the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>To test the results, issue:</para>
-
-<screen><userinput remap="test">make check</userinput></screen>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-grep" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/gzip.xml.svn-base BOOKfr/chapter05/.svn/text-base/gzip.xml.svn-base
--- BOOK/chapter05/.svn/text-base/gzip.xml.svn-base	2008-07-15 00:49:35.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/gzip.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,81 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-gzip" role="wrap">
-  <?dbhtml filename="gzip.html"?>
-
-  <sect1info condition="script">
-    <productname>gzip</productname>
-    <productnumber>&gzip-version;</productnumber>
-    <address>&gzip-url;</address>
-  </sect1info>
-
-  <title>Gzip-&gzip-version;</title>
-
-  <indexterm zone="ch-tools-gzip">
-    <primary sortas="a-Gzip">Gzip</primary>
-    <secondary>tools</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/gzip.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&gzip-ch5-sbu;</seg>
-        <seg>&gzip-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Gzip</title>
-
-    <para>The version of the function <quote>futimens</quote> used
-    by Gzip is incompatible with the version that current
-    Glibc provides, so we'll rename the function:</para>
-
-<screen><userinput remap="pre">for file in gzip.c lib/utimens.{c,h} ; do \
-   cp -v $file{,.orig}
-   sed 's/futimens/gl_&amp;/' $file.orig &gt; $file
-done</userinput></screen>
-
-    <para>Prepare Gzip for compilation:</para>
-
-<screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
-
-    <para>Compile the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>To test the results, issue:</para>
-
-<screen><userinput remap="test">make check</userinput></screen>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-gzip" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/introduction.xml.svn-base BOOKfr/chapter05/.svn/text-base/introduction.xml.svn-base
--- BOOK/chapter05/.svn/text-base/introduction.xml.svn-base	2008-07-15 00:49:34.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/introduction.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,67 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-introduction">
-  <?dbhtml filename="introduction.html"?>
-
-  <title>Introduction</title>
-
-  <para>This chapter shows how to compile and install a minimal Linux system.
-  This system will contain just enough tools to start constructing the final
-  LFS system in <xref linkend="chapter-building-system"/> and allow a working
-  environment with more user convenience than a minimum environment would.</para>
-
-  <para>There are two steps in building this minimal system. The first step
-  is to build a new and host-independent toolchain (compiler, assembler,
-  linker, libraries, and a few useful utilities).  The second step uses this
-  toolchain to build the other essential tools.</para>
-
-  <para>The files compiled in this chapter will be installed under the
-  <filename class="directory">$LFS/tools</filename> directory to keep them
-  separate from the files installed in the next chapter and the host
-  production directories. Since the packages compiled here are temporary,
-  we do not want them to pollute the soon-to-be LFS system.</para>
-
-  <important>
-    <para>Before issuing the build instructions for a package, the package
-    should be unpacked as user <systemitem class="username">lfs</systemitem>,
-    and a <command>cd</command> into the created directory should be performed.
-    The build instructions assume that the <command>bash</command> shell is
-    in use.</para>
-  </important>
-
-  <para>Several of the packages are patched before compilation, but only when
-  the patch is needed to circumvent a problem. A patch is often needed in both
-  this and the next chapter, but sometimes in only one or the other. Therefore,
-  do not be concerned if instructions for a downloaded patch seem to be missing.
-  Warning messages about <emphasis>offset</emphasis> or <emphasis>fuzz</emphasis>
-  may also be encountered when applying a patch. Do not worry about these
-  warnings, as the patch was still successfully applied.</para>
-
-  <para>During the compilation of most packages, there will be several warnings
-  that scroll by on the screen. These are normal and can safely be ignored.
-  These warnings are as they appear&mdash;warnings about deprecated, but not
-  invalid, use of the C or C++ syntax. C standards change fairly often, and
-  some packages still use the older standard. This is not a problem, but does
-  prompt the warning.</para>
-
-  <important>
-    <para>After installing each package, delete its source and build directories,
-    unless specifically instructed otherwise. Deleting the sources prevents
-    mis-configuration when the same package is reinstalled later.</para>
-  </important>
-
-  <para>Check one last time that the <envar>LFS</envar> environment
-  variable is set up properly:</para>
-
-<screen role="nodump"><userinput>echo $LFS</userinput></screen>
-
-  <para>Make sure the output shows the path to the LFS partition's mount
-  point, which is <filename class="directory">/mnt/lfs</filename>, using
-  our example.</para>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/linux-headers.xml.svn-base BOOKfr/chapter05/.svn/text-base/linux-headers.xml.svn-base
--- BOOK/chapter05/.svn/text-base/linux-headers.xml.svn-base	2008-07-15 00:49:35.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/linux-headers.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,68 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-linux-headers" role="wrap">
-  <?dbhtml filename="linux-headers.html"?>
-
-  <sect1info condition="script">
-    <productname>linux</productname>
-    <productnumber>&linux-version;</productnumber>
-    <address>&linux-url;</address>
-  </sect1info>
-
-  <title>Linux-&linux-version; API Headers</title>
-
-  <indexterm zone="ch-tools-linux-headers">
-    <primary sortas="a-Linux">Linux</primary>
-    <secondary>tools, API headers</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/linux-headers.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&linux-headers-ch5-sbu;</seg>
-        <seg>&linux-headers-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Linux API Headers</title>
-
-    <para>The Linux kernel needs to expose an Application Programming Interface
-    (API) for the system's C library (Glibc in LFS) to utilize.  This is done
-    by way of sanitizing various C header files that are shipped in the Linux
-    kernel source tarball.</para>
-
-    <para>Install the header files:</para>
-
-<screen><userinput remap="install">make mrproper
-make headers_check
-make INSTALL_HDR_PATH=dest headers_install
-cp -rv dest/include/* /tools/include</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-linux-headers" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/m4.xml.svn-base BOOKfr/chapter05/.svn/text-base/m4.xml.svn-base
--- BOOK/chapter05/.svn/text-base/m4.xml.svn-base	2008-07-15 00:49:35.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/m4.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,72 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-m4" role="wrap">
-  <?dbhtml filename="m4.html"?>
-
-  <sect1info condition="script">
-    <productname>m4</productname>
-    <productnumber>&m4-version;</productnumber>
-    <address>&m4-url;</address>
-  </sect1info>
-
-  <title>M4-&m4-version;</title>
-
-  <indexterm zone="ch-tools-m4">
-    <primary sortas="a-M4">M4</primary>
-    <secondary>tools</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/m4.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&m4-ch5-sbu;</seg>
-        <seg>&m4-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of M4</title>
-
-    <para>Prepare M4 for compilation:</para>
-
-<screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
-
-    <para>Compile the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>To test the results, issue:</para>
-
-<screen><userinput remap="test">make check</userinput></screen>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-m4" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/make.xml.svn-base BOOKfr/chapter05/.svn/text-base/make.xml.svn-base
--- BOOK/chapter05/.svn/text-base/make.xml.svn-base	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/make.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,71 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-<sect1 id="ch-tools-make" role="wrap">
-  <?dbhtml filename="make.html"?>
-
-  <sect1info condition="script">
-    <productname>make</productname>
-    <productnumber>&make-version;</productnumber>
-    <address>&make-url;</address>
-  </sect1info>
-
-  <title>Make-&make-version;</title>
-
-  <indexterm zone="ch-tools-make">
-    <primary sortas="a-Make">Make</primary>
-    <secondary>tools</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/make.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&make-ch5-sbu;</seg>
-        <seg>&make-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Make</title>
-
-    <para>Prepare Make for compilation:</para>
-
-<screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
-
-    <para>Compile the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>To test the results, issue:</para>
-
-<screen><userinput remap="test">make check</userinput></screen>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-make" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/ncurses.xml.svn-base BOOKfr/chapter05/.svn/text-base/ncurses.xml.svn-base
--- BOOK/chapter05/.svn/text-base/ncurses.xml.svn-base	2008-07-15 00:49:35.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/ncurses.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,96 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-ncurses" role="wrap">
-  <?dbhtml filename="ncurses.html"?>
-
-  <sect1info condition="script">
-    <productname>ncurses</productname>
-    <productnumber>&ncurses-version;</productnumber>
-    <address>&ncurses-url;</address>
-  </sect1info>
-
-  <title>Ncurses-&ncurses-version;</title>
-
-  <indexterm zone="ch-tools-ncurses">
-    <primary sortas="a-Ncurses">Ncurses</primary>
-    <secondary>tools</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/ncurses.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&ncurses-ch5-sbu;</seg>
-        <seg>&ncurses-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Ncurses</title>
-
-    <para>Prepare Ncurses for compilation:</para>
-
-<screen><userinput remap="configure">./configure --prefix=/tools --with-shared \
-    --without-debug --without-ada --enable-overwrite</userinput></screen>
-
-    <variablelist>
-      <title>The meaning of the configure options:</title>
-
-      <varlistentry>
-        <term><parameter>--without-ada</parameter></term>
-        <listitem>
-          <para>This ensures that Ncurses does not build support for the Ada
-          compiler which may be present on the host but will not be available
-          once we enter the <command>chroot</command> environment.</para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><parameter>--enable-overwrite</parameter></term>
-        <listitem>
-          <para>This tells Ncurses to install its header files into
-          <filename class="directory">/tools/include</filename>, instead of
-          <filename class="directory">/tools/include/ncurses</filename>, to
-          ensure that other packages can find the Ncurses headers
-          successfully.</para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-    <para>Compile the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>This package does not come with a test suite.</para>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-ncurses" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/patch.xml.svn-base BOOKfr/chapter05/.svn/text-base/patch.xml.svn-base
--- BOOK/chapter05/.svn/text-base/patch.xml.svn-base	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/patch.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,70 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-patch" role="wrap">
-  <?dbhtml filename="patch.html"?>
-
-  <sect1info condition="script">
-    <productname>patch</productname>
-    <productnumber>&patch-version;</productnumber>
-    <address>&patch-url;</address>
-  </sect1info>
-
-  <title>Patch-&patch-version;</title>
-
-  <indexterm zone="ch-tools-patch">
-    <primary sortas="a-Patch">Patch</primary>
-    <secondary>tools</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/patch.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&patch-ch5-sbu;</seg>
-        <seg>&patch-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Patch</title>
-
-    <para>Prepare Patch for compilation:</para>
-
-<screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
-
-    <para>Compile the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>This package does not come with a test suite.</para>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-patch" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/perl.xml.svn-base BOOKfr/chapter05/.svn/text-base/perl.xml.svn-base
--- BOOK/chapter05/.svn/text-base/perl.xml.svn-base	2008-07-15 00:49:35.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/perl.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,103 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-perl" role="wrap">
-  <?dbhtml filename="perl.html"?>
-
-  <sect1info condition="script">
-    <productname>perl</productname>
-    <productnumber>&perl-version;</productnumber>
-    <address>&perl-url;</address>
-  </sect1info>
-
-  <title>Perl-&perl-version;</title>
-
-  <indexterm zone="ch-tools-perl">
-    <primary sortas="a-Perl">Perl</primary>
-    <secondary>tools</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/perl.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&perl-ch5-sbu;</seg>
-        <seg>&perl-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Perl</title>
-
-    <para>First adapt some hard-wired paths to the C library by applying
-    the following patch:</para>
-
-<screen><userinput remap="pre">patch -Np1 -i ../&perl-libc-patch;</userinput></screen>
-
-    <para>Fix an incompatibility with gcc-&gcc-version;:</para>
-
-<screen><userinput remap="pre">mv -v makedepend.SH{,.orig}
-sed 's/command /command[ -]/' makedepend.SH.orig &gt; makedepend.SH</userinput></screen>
-
-    <para>Prepare Perl for compilation (make sure to get the
-    'Data/Dumper Fcntl IO POSIX' part of the command correct&mdash;they are all
-    letters):</para>
-
-<screen><userinput remap="configure">./configure.gnu --prefix=/tools -Dstatic_ext='Data/Dumper Fcntl IO POSIX'</userinput></screen>
-
-    <variablelist>
-      <title>The meaning of the configure options:</title>
-
-      <varlistentry>
-        <term><parameter>-Dstatic_ext='Data/Dumper Fcntl IO POSIX'</parameter></term>
-        <listitem>
-          <para>This tells Perl to build the minimum set of static extensions
-          needed for installing and testing the Coreutils and Glibc packages in the
-          next chapter.</para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-    <para>Only a few of the utilities contained in this package, and one of its
-    libraries need to be built:</para>
-
-<screen><userinput remap="make">make perl utilities ext/Errno/pm_to_blib</userinput></screen>
-
-    <para>Although Perl comes with a test suite, it is not recommended to
-    run it at this point. Only part of Perl was built and running
-    <command>make test</command> now will cause the rest of Perl to be
-    built as well, which is unnecessary at this point. The test suite can
-    be run in the next chapter if desired.</para>
-
-    <para>Install these tools and their libraries:</para>
-
-<screen><userinput remap="install">cp -v perl pod/pod2man /tools/bin
-mkdir -pv /tools/lib/perl5/&perl-version;
-cp -Rv lib/* /tools/lib/perl5/&perl-version;</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-perl" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/sed.xml.svn-base BOOKfr/chapter05/.svn/text-base/sed.xml.svn-base
--- BOOK/chapter05/.svn/text-base/sed.xml.svn-base	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/sed.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,72 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-sed" role="wrap">
-  <?dbhtml filename="sed.html"?>
-
-  <sect1info condition="script">
-    <productname>sed</productname>
-    <productnumber>&sed-version;</productnumber>
-    <address>&sed-url;</address>
-  </sect1info>
-
-  <title>Sed-&sed-version;</title>
-
-  <indexterm zone="ch-tools-sed">
-    <primary sortas="a-Sed">Sed</primary>
-    <secondary>tools</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/sed.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-    <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&sed-ch5-sbu;</seg>
-        <seg>&sed-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Sed</title>
-
-    <para>Prepare Sed for compilation:</para>
-
-<screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
-
-    <para>Compile the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>To test the results, issue:</para>
-
-<screen><userinput remap="test">make check</userinput></screen>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-sed" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/stripping.xml.svn-base BOOKfr/chapter05/.svn/text-base/stripping.xml.svn-base
--- BOOK/chapter05/.svn/text-base/stripping.xml.svn-base	2008-07-15 00:49:35.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/stripping.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,39 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-stripping">
-  <?dbhtml filename="stripping.html"?>
-
-  <title>Stripping</title>
-
-  <para>The steps in this section are optional, but if the LFS partition is
-  rather small, it is beneficial to learn that unnecessary items can be removed.
-  The executables and libraries built so far contain about 70 MB of unneeded
-  debugging symbols. Remove those symbols with:</para>
-
-<screen><userinput>strip --strip-debug /tools/lib/*
-strip --strip-unneeded /tools/{,s}bin/*</userinput></screen>
-
-  <para>The last of the above commands will skip some twenty files,
-  reporting that it does not recognize their file format. Most of these
-  are scripts instead of binaries.</para>
-
-  <para>Take care <emphasis>not</emphasis> to use
-  <parameter>--strip-unneeded</parameter> on the libraries. The static
-  ones would be destroyed and the toolchain packages would need to be
-  built all over again.</para>
-
-  <para>To save nearly 20 MB more, remove the documentation:</para>
-
-<screen><userinput>rm -rf /tools/{info,man}</userinput></screen>
-
-  <para>At this point, you should have at least 850 MB of free space in
-  <envar>$LFS</envar> that can be used to build and install Glibc in the
-  next phase. If you can build and install Glibc, you can build and install
-  the rest too.</para>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/tar.xml.svn-base BOOKfr/chapter05/.svn/text-base/tar.xml.svn-base
--- BOOK/chapter05/.svn/text-base/tar.xml.svn-base	2008-07-15 00:49:34.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/tar.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,72 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-tar" role="wrap">
-  <?dbhtml filename="tar.html"?>
-
-  <sect1info condition="script">
-    <productname>tar</productname>
-    <productnumber>&tar-version;</productnumber>
-    <address>&tar-url;</address>
-  </sect1info>
-
-  <title>Tar-&tar-version;</title>
-
-  <indexterm zone="ch-tools-tar">
-    <primary sortas="a-Tar">Tar</primary>
-    <secondary>tools</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/tar.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&tar-ch5-sbu;</seg>
-        <seg>&tar-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Tar</title>
-
-    <para>Prepare Tar for compilation:</para>
-
-<screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
-
-    <para>Compile the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>To test the results, issue:</para>
-
-<screen><userinput remap="test">make check</userinput></screen>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-tar" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/tcl.xml.svn-base BOOKfr/chapter05/.svn/text-base/tcl.xml.svn-base
--- BOOK/chapter05/.svn/text-base/tcl.xml.svn-base	2008-07-15 00:49:34.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/tcl.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,140 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-tcl" role="wrap">
-  <?dbhtml filename="tcl.html"?>
-
-  <sect1info condition="script">
-    <productname>tcl</productname>
-    <productnumber>&tcl-version;</productnumber>
-    <address>&tcl-url;</address>
-  </sect1info>
-
-  <title>Tcl-&tcl-version;</title>
-
-  <indexterm zone="ch-tools-tcl">
-    <primary sortas="a-Tcl">Tcl</primary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <para>The Tcl package contains the Tool Command Language.</para>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&tcl-ch5-sbu;</seg>
-        <seg>&tcl-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Tcl</title>
-
-    <para>This package and the next two (Expect and DejaGNU) are installed
-    to support running the test suites for GCC and Binutils. Installing
-    three packages for testing purposes may seem excessive, but it is very
-    reassuring, if not essential, to know that the most important tools are
-    working properly. Even if the test suites are not run in this chapter
-    (they are not mandatory), these packages are required to run the test
-    suites in <xref linkend="chapter-building-system"/>.</para>
-
-    <para>Prepare Tcl for compilation:</para>
-
-<screen><userinput remap="configure">cd unix
-./configure --prefix=/tools</userinput></screen>
-
-    <para>Build the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>To test the results, issue:</para>
-
-<screen><userinput remap="test">TZ=UTC make test</userinput></screen>
-
-    <para>The Tcl test suite is known to experience failures under certain host
-    conditions that are not fully understood. Therefore, test suite failures
-    here are not surprising, and are not considered critical. The
-    <parameter>TZ=UTC</parameter> parameter sets the time zone to Coordinated
-    Universal Time (UTC), also known as Greenwich Mean Time (GMT), but only
-    for the duration of the test suite run. This ensures that the clock tests
-    are exercised correctly. Details on the <envar>TZ</envar> environment
-    variable are provided in <xref linkend="chapter-bootscripts"/>.</para>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-    <para>Install Tcl's headers. The next package, Expect, requires them
-    to build.</para>
-
-<screen><userinput remap="install">make install-private-headers</userinput></screen>
-
-    <para>Now make a necessary symbolic link:</para>
-
-<screen><userinput remap="install">ln -sv tclsh8.4 /tools/bin/tclsh</userinput></screen>
-
-  </sect2>
-
-  <sect2 id="contents-tcl" role="content">
-    <title>Contents of Tcl</title>
-
-    <segmentedlist>
-      <segtitle>Installed programs</segtitle>
-      <segtitle>Installed library</segtitle>
-
-      <seglistitem>
-        <seg>tclsh (link to tclsh8.4) and tclsh8.4</seg>
-        <seg>libtcl8.4.so</seg>
-      </seglistitem>
-    </segmentedlist>
-
-    <variablelist>
-      <bridgehead renderas="sect3">Short Descriptions</bridgehead>
-      <?dbfo list-presentation="list"?>
-      <?dbhtml list-presentation="table"?>
-
-      <varlistentry id="tclsh8.4">
-        <term><command>tclsh8.4</command></term>
-        <listitem>
-          <para>The Tcl command shell</para>
-          <indexterm zone="ch-tools-tcl tclsh8.4">
-            <primary sortas="b-tclsh8.4">tclsh8.4</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="tclsh">
-        <term><command>tclsh</command></term>
-        <listitem>
-          <para>A link to tclsh8.4</para>
-          <indexterm zone="ch-tools-tcl tclsh">
-            <primary sortas="b-tclsh">tclsh</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="libtcl8.4.so">
-        <term><filename class="libraryfile">libtcl8.4.so</filename></term>
-        <listitem>
-          <para>The Tcl library</para>
-          <indexterm zone="ch-tools-tcl libtcl8.4.so">
-            <primary sortas="c-libtcl8.4.so">libtcl8.4.so</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/texinfo.xml.svn-base BOOKfr/chapter05/.svn/text-base/texinfo.xml.svn-base
--- BOOK/chapter05/.svn/text-base/texinfo.xml.svn-base	2008-07-15 00:49:35.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/texinfo.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,72 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-texinfo" role="wrap">
-  <?dbhtml filename="texinfo.html"?>
-
-  <sect1info condition="script">
-    <productname>texinfo</productname>
-    <productnumber>&texinfo-version;</productnumber>
-    <address>&texinfo-url;</address>
-  </sect1info>
-
-  <title>Texinfo-&texinfo-version;</title>
-
-  <indexterm zone="ch-tools-texinfo">
-    <primary sortas="a-Texinfo">Texinfo</primary>
-    <secondary>tools</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/texinfo.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&texinfo-ch5-sbu;</seg>
-        <seg>&texinfo-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Texinfo</title>
-
-    <para>Prepare Texinfo for compilation:</para>
-
-<screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
-
-    <para>Compile the package:</para>
-
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>To test the results, issue:</para>
-
-<screen><userinput remap="test">make check</userinput></screen>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-texinfo" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/toolchaintechnotes.xml.svn-base BOOKfr/chapter05/.svn/text-base/toolchaintechnotes.xml.svn-base
--- BOOK/chapter05/.svn/text-base/toolchaintechnotes.xml.svn-base	2008-07-15 00:49:35.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/toolchaintechnotes.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,218 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-toolchaintechnotes">
-  <?dbhtml filename="toolchaintechnotes.html"?>
-
-  <title>Toolchain Technical Notes</title>
-
-  <para>This section explains some of the rationale and technical details
-  behind the overall build method. It is not essential to immediately
-  understand everything in this section. Most of this information will be
-  clearer after performing an actual build. This section can be referred
-  back to at any time during the process.</para>
-
-  <para>The overall goal of <xref linkend="chapter-temporary-tools"/> is to
-  provide a temporary environment that can be chrooted into and from which can be
-  produced a clean, trouble-free build of the target LFS system in <xref
-  linkend="chapter-building-system"/>. Along the way, we separate the new system
-  from the host system as much as possible, and in doing so, build a
-  self-contained and self-hosted toolchain. It should be noted that the build
-  process has been designed to minimize the risks for new readers and provide
-  maximum educational value at the same time.</para>
-
-  <important>
-    <para>Before continuing, be aware of the name of the working platform,
-    often referred to as the target triplet. Many times, the target
-    triplet will probably be <emphasis>i686-pc-linux-gnu</emphasis>. A
-    simple way to determine the name of the target triplet is to run the
-    <command>config.guess</command> script that comes with the source for
-    many packages. Unpack the Binutils sources and run the script:
-    <userinput>./config.guess</userinput> and note the output.</para>
-
-    <para>Also be aware of the name of the platform's dynamic linker, often
-    referred to as the dynamic loader (not to be confused with the standard
-    linker <command>ld</command> that is part of Binutils). The dynamic linker
-    provided by Glibc finds and loads the shared libraries needed by a program,
-    prepares the program to run, and then runs it. The name of the dynamic
-    linker will usually be <filename class="libraryfile">ld-linux.so.2</filename>.
-    On platforms that are less prevalent, the name might be <filename
-    class="libraryfile">ld.so.1</filename>, and newer 64 bit platforms might
-    be named something else entirely. The name of the platform's dynamic linker
-    can be determined by looking in the <filename class="directory">/lib</filename>
-    directory on the host system. A sure-fire way to determine the name is to
-    inspect a random binary from the host system by running:
-    <userinput>readelf -l &lt;name of binary&gt; | grep interpreter</userinput>
-    and noting the output. The authoritative reference covering all platforms
-    is in the <filename>shlib-versions</filename> file in the root of the Glibc
-    source tree.</para>
-  </important>
-
-  <para>Some key technical points of how the <xref
-  linkend="chapter-temporary-tools"/> build method works:</para>
-
-  <itemizedlist>
-    <listitem>
-      <para>The process is similar in principle to cross-compiling, whereby
-      tools installed in the same prefix work in cooperation, and thus utilize
-      a little GNU <quote>magic</quote></para>
-    </listitem>
-    <listitem>
-      <para>Careful manipulation of the standard linker's library search path
-      ensures programs are linked only against chosen libraries</para>
-    </listitem>
-    <listitem>
-      <para>Careful manipulation of <command>gcc</command>'s
-      <filename>specs</filename> file tells the compiler which target dynamic
-      linker will be used</para>
-    </listitem>
-  </itemizedlist>
-
-  <para>Binutils is installed first because the <command>configure</command>
-  runs of both GCC and Glibc perform various feature tests on the assembler
-  and linker to determine which software features to enable or disable. This
-  is more important than one might first realize. An incorrectly configured
-  GCC or Glibc can result in a subtly broken toolchain, where the impact of
-  such breakage might not show up until near the end of the build of an
-  entire distribution. A test suite failure will usually highlight this error
-  before too much additional work is performed.</para>
-
-  <para>Binutils installs its assembler and linker in two locations,
-  <filename class="directory">/tools/bin</filename> and <filename
-  class="directory">/tools/$TARGET_TRIPLET/bin</filename>. The tools in one
-  location are hard linked to the other. An important facet of the linker is
-  its library search order. Detailed information can be obtained from
-  <command>ld</command> by passing it the <parameter>--verbose</parameter>
-  flag. For example, an <userinput>ld --verbose | grep SEARCH</userinput>
-  will illustrate the current search paths and their order. It shows which
-  files are linked by <command>ld</command> by compiling a dummy program and
-  passing the <parameter>--verbose</parameter> switch to the linker. For example,
-  <userinput>gcc dummy.c -Wl,--verbose 2&gt;&amp;1 | grep succeeded</userinput>
-  will show all the files successfully opened during the linking.</para>
-
-  <para>The next package installed is GCC. An example of what can be
-  seen during its run of <command>configure</command> is:</para>
-
-<screen><computeroutput>checking what assembler to use...
-        /tools/i686-pc-linux-gnu/bin/as
-checking what linker to use... /tools/i686-pc-linux-gnu/bin/ld</computeroutput></screen>
-
-  <para>This is important for the reasons mentioned above. It also demonstrates
-  that GCC's configure script does not search the PATH directories to find which
-  tools to use. However, during the actual operation of <command>gcc</command>
-  itself, the same search paths are not necessarily used. To find out which
-  standard linker <command>gcc</command> will use, run:
-  <userinput>gcc -print-prog-name=ld</userinput>.</para>
-
-  <para>Detailed information can be obtained from <command>gcc</command> by
-  passing it the <parameter>-v</parameter> command line option while compiling
-  a dummy program. For example, <userinput>gcc -v dummy.c</userinput> will show
-  detailed information about the preprocessor, compilation, and assembly stages,
-  including <command>gcc</command>'s included search paths and their order.</para>
-
-  <para>The next package installed is Glibc. The most important considerations
-  for building Glibc are the compiler, binary tools, and kernel headers. The
-  compiler is generally not an issue since Glibc will always use the
-  <command>gcc</command> found in a <envar>PATH</envar> directory. The binary
-  tools and kernel headers can be a bit more complicated. Therefore, take no
-  risks and use the available configure switches to enforce the correct
-  selections. After the run of <command>configure</command>, check the contents
-  of the <filename>config.make</filename> file in the <filename
-  class="directory">glibc-build</filename> directory for all important details.
-  Note the use of <parameter>CC="gcc -B/tools/bin/"</parameter> to control which
-  binary tools are used and the use of the <parameter>-nostdinc</parameter>
-  and <parameter>-isystem</parameter> flags to control the compiler's include
-  search path. These items highlight an important aspect of the Glibc
-  package&mdash;it is very self-sufficient in terms of its build machinery and
-  generally does not rely on toolchain defaults.</para>
-
-  <para>After the Glibc installation, make some adjustments to ensure that
-  searching and linking take place only within the <filename
-  class="directory">/tools</filename> prefix.  Install an adjusted
-  <command>ld</command>, which has a hard-wired search path limited to
-  <filename class="directory">/tools/lib</filename>. Then amend
-  <command>gcc</command>'s specs file to point to the new dynamic linker in
-  <filename class="directory">/tools/lib</filename>. This last step is vital
-  to the whole process. As mentioned above, a hard-wired path to a dynamic
-  linker is embedded into every Executable and Link Format (ELF)-shared
-  executable.  This can be inspected by running:
-  <userinput>readelf -l &lt;name of binary&gt; | grep interpreter</userinput>.
-  Amending gcc's specs file ensures that every program compiled from here
-  through the end of this chapter will use the new dynamic linker in
-  <filename class="directory">/tools/lib</filename>.</para>
-
-  <para>The need to use the new dynamic linker is also the reason why
-  the Specs patch is applied for the second pass of GCC. Failure to do
-  so will result in the GCC programs themselves having the name of the
-  dynamic linker from the host system's <filename
-  class="directory">/lib</filename> directory embedded into them, which
-  would defeat the goal of getting away from the host.</para>
-
-  <para>During the second pass of Binutils, we are able to utilize the
-  <parameter>--with-lib-path</parameter> configure switch to control
-  <command>ld</command>'s library search path.  From this point onwards,
-  the core toolchain is self-contained and self-hosted. The remainder of
-  the <xref linkend="chapter-temporary-tools"/> packages all build against
-  the new Glibc in <filename class="directory">/tools</filename>.</para>
-
-  <para>Upon entering the chroot environment in <xref
-  linkend="chapter-building-system"/>, the first major package to be
-  installed is Glibc, due to its self-sufficient nature mentioned above.
-  Once this Glibc is installed into <filename
-  class="directory">/usr</filename>, perform a quick changeover of the
-  toolchain defaults, then proceed in building the rest of the target
-  LFS system.</para>
-
-  <!-- FIXME: Removed as part of the fix for bug 1061 - we no longer build pass1
-      packages statically, therefore this explanation isn't required
-
-  <sect2>
-  <title>Notes on Static Linking</title>
-
-  <para>Besides their specific task, most programs have to perform many
-  common and sometimes trivial operations. These include allocating
-  memory, searching directories, reading and writing files, string
-  handling, pattern matching, arithmetic, and other tasks. Instead of
-  obliging each program to reinvent the wheel, the GNU system provides
-  all these basic functions in ready-made libraries. The major library
-  on any Linux system is Glibc.</para>
-
-  <para>There are two primary ways of linking the functions from a
-  library to a program that uses them&mdash;statically or dynamically. When
-  a program is linked statically, the code of the used functions is
-  included in the executable, resulting in a rather bulky program. When
-  a program is dynamically linked, it includes a reference to the
-  dynamic linker, the name of the library, and the name of the function,
-  resulting in a much smaller executable. A third option is to use the
-  programming interface of the dynamic linker (see <filename>dlopen(3)</filename>
-  for more information).</para>
-
-  <para>Dynamic linking is the default on Linux and has three major
-  advantages over static linking. First, only one copy of the executable
-  library code is needed on the hard disk, instead of having multiple
-  copies of the same code included in several programs, thus saving
-  disk space. Second, when several programs use the same library
-  function at the same time, only one copy of the function's code is
-  required in core, thus saving memory space. Third, when a library
-  function gets a bug fixed or is otherwise improved, only the one
-  library needs to be recompiled instead of recompiling all programs
-  that make use of the improved function.</para>
-
-  <para>If dynamic linking has several advantages, why then do we
-  statically link the first two packages in this chapter? The reasons
-  are threefold&mdash;historical, educational, and technical. The
-  historical reason is that earlier versions of LFS statically linked
-  every program in this chapter. Educationally, knowing the difference
-  between static and dynamic linking is useful. The technical benefit is
-  a gained element of independence from the host, meaning that those
-  programs can be used independently of the host system. However, it is
-  worth noting that an overall successful LFS build can still be
-  achieved when the first two packages are built dynamically.</para>
-
-  </sect2>-->
-
-</sect1>
diff -Naur BOOK/chapter05/.svn/text-base/util-linux-ng.xml.svn-base BOOKfr/chapter05/.svn/text-base/util-linux-ng.xml.svn-base
--- BOOK/chapter05/.svn/text-base/util-linux-ng.xml.svn-base	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/.svn/text-base/util-linux-ng.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,76 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-util-linux-ng" role="wrap">
-  <?dbhtml filename="util-linux-ng.html"?>
-
-  <sect1info condition="script">
-    <productname>util-linux-ng</productname>
-    <productnumber>&util-linux-ng-version;</productnumber>
-    <address>&util-linux-ng-url;</address>
-  </sect1info>
-
-  <title>Util-linux-ng-&util-linux-ng-version;</title>
-
-  <indexterm zone="ch-tools-util-linux-ng">
-    <primary sortas="a-Util-linux-ng">Util-linux-ng</primary>
-    <secondary>tools</secondary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
-    href="../chapter06/util-linux-ng.xml"
-    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&util-linux-ng-ch5-sbu;</seg>
-        <seg>&util-linux-ng-ch5-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of Util-linux-ng</title>
-
-    <para>Prepare Util-linux-ng for compilation:</para>
-
-<screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
-
-    <para>Only a few of the utilities contained in this package need to be
-    built:</para>
-
-<screen><userinput remap="make">make -C mount mount umount
-make -C text-utils more</userinput></screen>
-
-    <para>This package comes with a test suite, but running it will cause all of
-    the binaries to be built and tested.  If you still wish to run the tests,
-    issue:</para>
-
-<screen><userinput remap="test">make check</userinput></screen>
-
-    <para>Copy these programs to the temporary tools directory:</para>
-
-<screen><userinput remap="install">cp -v mount/{,u}mount text-utils/more /tools/bin</userinput></screen>
-
-  </sect2>
-
-  <sect2 role="content">
-    <title/>
-
-    <para>Details on this package are located in
-    <xref linkend="contents-utillinux" role="."/></para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter05/CVS/Entries BOOKfr/chapter05/CVS/Entries
--- BOOK/chapter05/CVS/Entries	1970-01-01 01:00:00.000000000 +0100
+++ BOOKfr/chapter05/CVS/Entries	2008-07-14 19:56:59.000000000 +0100
@@ -0,0 +1,41 @@
+/kernel-headers.xml/1.6/Wed Jun  6 14:27:04 2007//
+/linux-libc-headers.xml/1.4/Wed Jun  6 14:27:04 2007//
+/udev.xml/1.2/Wed Jun  6 14:27:04 2007//
+/util-linux.xml/1.6/Sat May 31 21:21:22 2008//
+/adjusting.xml/1.11/Mon Jun 23 22:04:09 2008//
+/bash.xml/1.14/Tue Jun 24 06:08:46 2008//
+/binutils-pass1.xml/1.13/Mon Jun 23 21:18:23 2008//
+/binutils-pass2.xml/1.14/Tue Jun 24 06:00:43 2008//
+/bison.xml/1.5/Tue Jun 24 08:12:42 2008//
+/bzip2.xml/1.11/Tue Jun 24 06:10:39 2008//
+/chapter05.xml/1.22/Mon Jun 23 20:52:55 2008//
+/coreutils.xml/1.14/Tue Jun 24 06:21:28 2008//
+/dejagnu.xml/1.12/Mon Jun 23 22:32:50 2008//
+/diffutils.xml/1.11/Tue Jun 24 06:24:29 2008//
+/expect.xml/1.12/Mon Jun 23 22:28:15 2008//
+/findutils.xml/1.11/Tue Jun 24 06:33:52 2008//
+/flex.xml/1.6/Tue Jun 24 08:15:44 2008//
+/gawk.xml/1.11/Tue Jun 24 06:37:16 2008//
+/gcc-pass1.xml/1.11/Mon Jun 23 21:38:47 2008//
+/gcc-pass2.xml/1.14/Mon Jun 23 23:15:31 2008//
+/gettext.xml/1.10/Tue Jun 24 06:39:37 2008//
+/glibc.xml/1.13/Mon Jun 23 21:57:30 2008//
+/grep.xml/1.13/Tue Jun 24 06:41:22 2008//
+/gzip.xml/1.12/Tue Jun 24 07:34:32 2008//
+/linux-headers.xml/1.2/Mon Jun 23 21:40:55 2008//
+/m4.xml/1.7/Tue Jun 24 07:36:34 2008//
+/make.xml/1.12/Tue Jun 24 07:43:58 2008//
+/ncurses.xml/1.9/Tue Jun 24 06:04:28 2008//
+/patch.xml/1.12/Tue Jun 24 07:46:44 2008//
+/perl.xml/1.12/Tue Jun 24 07:54:16 2008//
+/sed.xml/1.12/Tue Jun 24 07:57:32 2008//
+/tar.xml/1.12/Tue Jun 24 08:00:19 2008//
+/tcl.xml/1.14/Mon Jun 23 22:12:12 2008//
+/texinfo.xml/1.13/Tue Jun 24 08:02:47 2008//
+/toolchaintechnotes.xml/1.10/Mon Jun 23 21:13:03 2008//
+/changingowner.xml/1.1/Tue Jun 24 08:10:51 2008//
+/introduction.xml/1.21/Mon Jun 23 20:56:31 2008//
+/stripping.xml/1.7/Tue Jun 24 08:10:45 2008//
+/e2fsprogs.xml/1.1/Tue Jun 24 06:31:22 2008//
+/util-linux-ng.xml/1.1/Tue Jun 24 08:08:50 2008//
+D
diff -Naur BOOK/chapter05/CVS/Repository BOOKfr/chapter05/CVS/Repository
--- BOOK/chapter05/CVS/Repository	1970-01-01 01:00:00.000000000 +0100
+++ BOOKfr/chapter05/CVS/Repository	2008-07-14 18:47:46.000000000 +0100
@@ -0,0 +1 @@
+lfs/chapter05
diff -Naur BOOK/chapter05/CVS/Root BOOKfr/chapter05/CVS/Root
--- BOOK/chapter05/CVS/Root	1970-01-01 01:00:00.000000000 +0100
+++ BOOKfr/chapter05/CVS/Root	2008-07-14 18:47:46.000000000 +0100
@@ -0,0 +1 @@
+:ext:texou@traduc.org:/var/lib/cvs/lfs
diff -Naur BOOK/chapter05/adjusting.xml BOOKfr/chapter05/adjusting.xml
--- BOOK/chapter05/adjusting.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/adjusting.xml	2008-06-23 23:04:09.000000000 +0100
@@ -8,62 +8,64 @@
 <sect1 id="ch-tools-adjusting">
   <?dbhtml filename="adjusting.html"?>
 
-  <title>Adjusting the Toolchain</title>
+  <title>Ajuster l'ensemble d'outils</title>
 
-  <para>Now that the temporary C libraries have been installed, all
-  tools compiled in the rest of this chapter should be linked against
-  these libraries. In order to accomplish this, the linker and the
-  compiler's specs file need to be adjusted.</para>
-
-  <para>The linker, adjusted at the end of the first pass of Binutils, needs
-  to be renamed so that it can be properly found and used. First, backup the
-  original linker, then replace it with the adjusted linker. We'll also
-  create a link to its counterpart in <filename class="directory">
-  /tools/$(gcc -dumpmachine)/bin</filename>:</para>
+  <para>Maintenant que les bibliothèques C temporaires ont été installées, tous
+  les outils compilés dans le reste de ce chapitre doivent être liés avec ces
+  bibliothèques. Pour accomplir cela, l'éditeur de liens et le fichier specs du
+  compilateur doivent être ajustés.</para>
+
+  <para>L'éditeur de liens ajusté (à la fin de la première passe de Binutils)
+  est installé en lançant la commande suivante à partir du répertoire 
+  <filename class="directory">/tools/$(gcc -dumpmachine)/bin</filename>&nbsp;:</para>
 
 <screen><userinput>mv -v /tools/bin/{ld,ld-old}
 mv -v /tools/$(gcc -dumpmachine)/bin/{ld,ld-old}
 mv -v /tools/bin/{ld-new,ld}
 ln -sv /tools/bin/ld /tools/$(gcc -dumpmachine)/bin/ld</userinput></screen>
 
-  <para>From this point onwards, everything will link only against the
-  libraries in <filename class="directory">/tools/lib</filename>.</para>
+  <para>À partir de ce moment, tout sera lié uniquement avec les bibliothèques
+  comprises dans <filename class="directory">/tools/lib</filename>.</para>
 
-  <para>The next task is to point GCC to the new dynamic linker. This is done by
-  dumping GCC's <quote>specs</quote> file to a location where GCC will look for it
-  by default. A simple <command>sed</command> substitution then alters the
-  dynamic linker that GCC will use.</para>
-
-  <para>For the sake of accuracy, it is recommended to use a copy-and-paste
-  method when issuing the following command. Be sure to visually inspect the
-  specs file and verify that all occurrences of <quote>/lib/ld-linux.so.2</quote>
-  have been replaced with <quote>/tools/lib/ld-linux.so.2</quote>:</para>
+  <para>La prochaine tâche est de modifier le fichier specs de GCC pour qu'il
+  pointe vers le nouvel éditeur de liens. Ceci se fait en plaçant le fichier 
+  <quote>specs</quote> de GCC à un endroit où GCC va le chercher par défaut.
+  Un simple script <command>sed</command> modifie alors l'éditeur de liens
+  dynamique que GCC utilisera.</para>
+
+  <para>Par soucis de précision, il est recommandé que la commande
+  ci-dessus soit copiée/collée.
+  Assurez-vous  d'inspecter visuellement le fichier specs pour vérifier
+  que toutes les occurrences de <quote>/lib/ld-linux.so.2</quote> ont
+  été remplacées par <quote>/tools/lib/ld-linux.so.2</quote>&nbsp;:</para>
 
   <important>
-    <para>If working on a platform where the name of the dynamic linker is
-    something other than <filename class="libraryfile">ld-linux.so.2</filename>,
-    replace <quote>ld-linux.so.2</quote> with the name of the platform's
-    dynamic linker in the following commands. Refer to <xref
-    linkend="ch-tools-toolchaintechnotes" role=","/> if necessary.</para>
+    <para>Au cas où le nom de l'éditeur de liens de la plateforme de
+    travail est autre que  <filename class="libraryfile">ld-linux.so.2</filename>,
+    remplacez <quote>ld-linux.so.2</quote> par le nom de l'éditeur de liens de
+    votre plateforme dans les commandes ci-dessus. Référez-vous à 
+    <xref linkend="ch-tools-toolchaintechnotes" role=","/> si
+    nécessaire</para>
   </important>
 
 <!-- Ampersands are needed to allow copy and paste -->
 <screen><userinput>gcc -dumpspecs | sed 's@/lib/ld-linux.so.2@/tools&amp;@g' \
   > `dirname $(gcc -print-libgcc-file-name)`/specs</userinput></screen>
 
-  <para>During the build process, GCC runs a script
-  (<command>fixincludes</command>) that scans the system for header files
-  that may need to be fixed (they might contain syntax errors, for example),
-  and installs the fixed versions in a private include directory. There is a
-  possibility that, as a result of this process, some header files from the
-  host system have found their way into GCC's private include directory. As
-  the rest of this chapter only requires the headers from GCC and Glibc,
-  which have both been installed at this point, any <quote>fixed</quote>
-  headers can safely be removed. This helps to avoid any host headers
-  polluting the build environment. Run the following commands to remove the
-  header files in GCC's private include directory (you may find it easier to
-  copy and paste these commands, rather than typing them by hand, due to
-  their length):</para>
+  <para>Pendant la procédure de construction, GCC exécute un script 
+  (<command>fixincludes</command>) qui parcourt le système pour déterminer les
+  fichiers d'en-tête qui pourraient nécessiter une réparation (ils pourraient
+  contenir des erreurs de syntaxe, par exemple), et qui installe les versions
+  corrigées dans un répertoire include autonome. Il se peut que, au terme de ce
+  processus, certains fichiers d'en-tête du système hôte se trouvent placés
+  dans le répertoire autonome include de GCC. Comme le reste de ce chapitre
+  n'exige que les en-têtes de GCC et de Glibc, qui ont désormais été installées,
+  toute en-tête <quote>corrigée</quote> peut être supprimée en toute sécurité. Cela
+  permet d'éviter toute pollution de l'environnement de construction par les
+  en-têtes du système hôte. Lancez les commandes suivantes pour supprimer
+  les fichiers d'en-tête dans le répertoire autonome include de GCC (il se
+  peut que vous trouviez plus facile de copier-coller les commandes plutôt que
+  de les saisir à la main, du fait de leur longueur)&nbsp;:</para>
 
 <!-- && used to ease copy and pasting -->
 <screen><userinput>GCC_INCLUDEDIR=`dirname $(gcc -print-libgcc-file-name)`/include &amp;&amp;
@@ -72,49 +74,53 @@
 unset GCC_INCLUDEDIR</userinput></screen>
 
   <caution>
-    <para>At this point, it is imperative to stop and ensure that the basic
-    functions (compiling and linking) of the new toolchain are working as
-    expected. To perform a sanity check, run the following commands:</para>
+    <para>Il est impératif à ce moment de s'arrêter et de s'assurer que les
+    fonctions basiques (compilation et édition des liens) du nouvel ensemble
+    d'outils fonctionnent comme attendu. Pour réaliser une vérification de
+    propreté, lancez les commandes suivantes&nbsp;:</para>
 
 <screen><userinput>echo 'main(){}' &gt; dummy.c
 cc dummy.c
 readelf -l a.out | grep ': /tools'</userinput></screen>
 
-    <para>If everything is working correctly, there should be no errors,
-    and the output of the last command will be of the form:</para>
+    <para>Si tout fonctionne correctement, il ne devrait pas y avoir d'erreurs et
+    la sortie de la dernière commande sera de la forme&nbsp;:</para>
 
 <screen><computeroutput>[Requesting program interpreter:
     /tools/lib/ld-linux.so.2]</computeroutput></screen>
 
-    <para>Note that <filename class="directory">/tools/lib</filename>
-    appears as the prefix of the dynamic linker.</para>
+    <para>Notez que <filename class="directory">/tools/lib</filename>
+    apparaît comme préfixe de l'éditeur de liens dynamique.</para>
 
-    <para>If the output is not shown as above or there was no output at all,
-    then something is wrong. Investigate and retrace the steps to find out
-    where the problem is and correct it. This issue must be resolved before
-    continuing on. First, perform the sanity check again, using
-    <command>gcc</command> instead of <command>cc</command>. If this works,
-    then the <filename class="symlink">/tools/bin/cc</filename> symlink is
-    missing. Revisit <xref linkend="ch-tools-gcc-pass1" role=","/> and install
-    the symlink. Next, ensure that the <envar>PATH</envar> is correct. This
-    can be checked by running <command>echo $PATH</command> and verifying that
-    <filename class="directory">/tools/bin</filename> is at the head of the
-    list. If the <envar>PATH</envar> is wrong it could mean that you are not
-    logged in as user <systemitem class="username">lfs</systemitem> or that
-    something went wrong back in <xref linkend="ch-tools-settingenviron"
-    role="."/> Another option is that something may have gone wrong with the
-    specs file amendment above. In this case, redo the specs file amendment,
-    being careful to copy-and-paste the commands.</para>
+    <para>Si l'affichage diffère ou s'il n'y a aucun affichage, alors
+    quelque chose ne se passe pas bien. Enquêtez et tracez vos étapes pour
+    trouver où se cache le problème et comment le corriger. Ce problème doit
+    être corrigé avant de continuer. Tout d'abord, relancez la vérification
+    de propreté en utilisant
+    <command>gcc</command> au lieu de <command>cc</command>. Si cela fonctionne,
+    le lien symbolique <filename class="symlink">/tools/bin/cc</filename> est 
+    manquant. Lisez de nouveau <xref linkend="ch-tools-gcc-pass1" role=","/>  et 
+    installez le lien symbolique.
+    Ensuite, assurez-vous que le <envar>PATH</envar> est correct. Ceci se
+    vérifie en lançant <command>echo $PATH</command> et en vérifiant que
+    <filename class="directory">/tools/bin</filename> est en tête de la
+    liste. Si le <envar>PATH</envar> est mauvais, cela pourrait signifier
+    que vous n'êtes pas connecté en tant qu'utilisateur 
+    <systemitem class="username">lfs</systemitem> ou que quelque chose s'est mal passé dans 
+    <xref linkend="ch-tools-settingenviron" role="."/>. Une autre possibilité
+    est que quelque chose a pu mal se passer avec la correction du fichier specs
+    ci-dessus. Dans ce cas, refaites la modification de ce fichier en vous 
+    assurant de copier/coller les commandes.</para>
 
-    <para>Once all is well, clean up the test files:</para>
+    <para>Une fois que tout va bien, nettoyez les fichiers de test&nbsp;::</para>
 
 <screen><userinput>rm -v dummy.c a.out</userinput></screen>
 
   </caution>
 
-  <note><para>Building Tcl in the next section will serve as an additional check that
-  the toolchain has been built properly.  If Tcl fails to build, it is an
-  indication that something has gone wrong with the Binutils, GCC, or Glibc
-  installation, but not with Tcl itself.</para></note>
+  <note><para>Construire Tcl dans la prochaine section servira comme vérification
+  supplémentaire de la bonne mise en place de l'outil de construction. Si TCL
+  échoue à la construction, c'est une indication d'un problème avec l'installation
+  de Binutils, GCC ou Glibc, mais pas avec Tcl lui-même.</para></note>
 
 </sect1>
diff -Naur BOOK/chapter05/bash.xml BOOKfr/chapter05/bash.xml
--- BOOK/chapter05/bash.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/bash.xml	2008-06-24 07:08:46.000000000 +0100
@@ -18,7 +18,7 @@
 
   <indexterm zone="ch-tools-bash">
     <primary sortas="a-Bash">Bash</primary>
-    <secondary>tools</secondary>
+    <secondary>outils</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,47 +41,47 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Bash</title>
+    <title>Installation de Bash</title>
 
-    <para>Apply fixes for several bugs discovered since the initial release of
-    Bash-&bash-version;:</para>
+    <para>Appliquez les corrections de plusieurs bogues découverts depuis
+    la version initiale de Bash-&bash-version;&nbsp;:</para>
 
 <screen><userinput remap="pre">patch -Np1 -i ../&bash-fixes-patch;</userinput></screen>
 
-    <para>Prepare Bash for compilation:</para>
+    <para>Préparez la compilation de Bash&nbsp;:</para>
 
 <screen><userinput remap="configure">./configure --prefix=/tools --without-bash-malloc</userinput></screen>
 
     <variablelist>
-      <title>The meaning of the configure option:</title>
+      <title>Voici la signification des options de configure&nbsp;:</title>
 
       <varlistentry>
         <term><parameter>--without-bash-malloc</parameter></term>
         <listitem>
-          <para>This option turns off the use of Bash's memory allocation
-          (<function>malloc</function>) function which is known to cause
-          segmentation faults. By turning this option off, Bash will use
-          the <function>malloc</function> functions from Glibc which are
-          more stable.</para>
+          <para>Cette option désactive l'utilisation par Bash de la fonction
+          d'allocation mémoire
+          <function>malloc</function> qui est connue pour causer des erreurs de
+          segmentation. En désactivant cette option, Bash utilisera les fonctions
+          <function>malloc</function> de Glibc qui sont plus stables.</para>
         </listitem>
       </varlistentry>
 
     </variablelist>
 
-    <para>Compile the package:</para>
+    <para>Compilez le paquet&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>To test the results, issue:</para>
+    <para>Pour tester les résultats, lancez&nbsp;:</para>
 
 <screen><userinput remap="test">make tests</userinput></screen>
 
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
-    <para>Make a link for the programs that use <command>sh</command> for
-    a shell:</para>
+    <para>Créez un lien pour les programmes qui utilisent
+    <command>sh</command> comme shell&nbsp;:</para>
 
 <screen><userinput remap="install">ln -vs bash /tools/bin/sh</userinput></screen>
 
@@ -90,7 +90,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails sur ce paquet sont situés dans
     <xref linkend="contents-bash" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/binutils-pass1.xml BOOKfr/chapter05/binutils-pass1.xml
--- BOOK/chapter05/binutils-pass1.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/binutils-pass1.xml	2008-06-23 22:18:23.000000000 +0100
@@ -7,18 +7,18 @@
 
 <sect1 id="ch-tools-binutils-pass1" role="wrap">
   <?dbhtml filename="binutils-pass1.html"?>
-
+  
   <sect1info condition="script">
-    <productname>binutils</productname>
-    <productnumber>&binutils-version;</productnumber>
-    <address>&binutils-url;</address>
+      <productname>binutils</productname>
+      <productnumber>&binutils-version;</productnumber>
+      <address>&binutils-url;</address>
   </sect1info>
 
-  <title>Binutils-&binutils-version; - Pass 1</title>
+  <title>Binutils-&binutils-version; - Passe 1</title>
 
   <indexterm zone="ch-tools-binutils-pass1">
     <primary sortas="a-Binutils">Binutils</primary>
-    <secondary>tools, pass 1</secondary>
+    <secondary>outils, passe 1</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,48 +41,51 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Binutils</title>
-
-    <para>It is important that Binutils be the first package compiled
-    because both Glibc and GCC perform various tests on the available
-    linker and assembler to determine which of their own features to
-    enable.</para>
 
-    <para>Binutils does not recognize versions of Texinfo newer than 4.9.  Fix
-    this issue by applying the following patch:</para>
+       <title>Installation de  Binutils</title>
 
-<screen><userinput remap="pre">patch -Np1 -i ../&binutils-configure-patch;</userinput></screen>
-
-    <para>The Binutils documentation recommends building Binutils outside of the
-    source directory in a dedicated build directory:</para>
+    <para>Il est important que Binutils soit le premier paquet compilé
+    parce que Glibc et GCC réalisent différents tests sur l'éditeur de
+    liens et l'assembleur disponibles pour déterminer leur propres
+    fonctionnalités à activer.</para>
+    
+    <para>Binutils ne reconnaît pas les veriions de Texinfo supérieures
+    à 4.9. Réparez ce problème en appliquant le patch suivant&nbsp;:
+    
+    <screen><userinput remap="pre">patch -Np1 -i ../&binutils-configure-patch;</userinput></screen>
+
+    <para>La documentation de Binutils recommande de construire Binutils
+    en dehors du répertoire des sources, c'est-à-dire dans un répertoire
+    de construction dédié&nbsp;:</para>
 
 <screen><userinput remap="pre">mkdir -v ../binutils-build
 cd ../binutils-build</userinput></screen>
 
     <note>
-      <para>In order for the SBU values listed in the rest of the book
-      to be of any use, measure the time it takes to build this package from
-      the configuration, up to and including the first install. To achieve
-      this easily, wrap the three commands in a <command>time</command>
-      command like this: <userinput>time { ./configure ... &amp;&amp; make
-      &amp;&amp; make install; }</userinput>.</para>
-    </note>
 
-    <para>Now prepare Binutils for compilation:</para>
+       <para>Pour que les valeurs SBU listées dans le reste du livre vous soient
+    utiles, mesurez le temps pris pour construire ce paquet, de la configuration
+    jusqu'à la première installation. Pour cela, englobez les trois commandes
+    dans une commande <command>time</command> de cette façon&nbsp;:
+<userinput>time { ./configure ... &amp;&amp; make      
+&amp;&amp; make install; }</userinput>.</para>     </note>
+
+    <para>Maintenant, préparez la compilation de Binutils&nbsp;:</para>
 
 <screen><userinput remap="configure">CC="gcc -B/usr/bin/" ../binutils-&binutils-version;/configure \
     --prefix=/tools --disable-nls --disable-werror</userinput></screen>
 
     <variablelist>
-      <title>The meaning of the configure options:</title>
+      <title>Voici la signification des options de configure&nbsp;:</title>
 
       <varlistentry>
         <term><envar>CC="gcc -B/usr/bin/"</envar></term>
         <listitem>
-          <para>This forces <command>gcc</command> to prefer the linker from
-          the host in <filename class="directory">/usr/bin</filename>. This
-          is necessary on some hosts where the new <command>ld</command>
-          built here is not compatible with the host's <command>gcc</command>.
+          <para>Cela oblige <command>gcc</command> à préférer l'éeiteur de lien
+          du système hôte dans <filename class="directory">/usr/bin</filename>.
+          C'est nécessaire sur certains systèmes hôtes où le nouveau
+          <command>ld</command> compilé ici n'est pas compatible avec le
+          <command>gcc</command> du système hôte.
           </para>
         </listitem>
       </varlistentry>
@@ -90,73 +93,75 @@
       <varlistentry>
         <term><parameter>--prefix=/tools</parameter></term>
         <listitem>
-          <para>This tells the configure script to prepare to install the
-          Binutils programs in the <filename class="directory">/tools</filename>
-          directory.</para>
+          <para>Ceci indique au script configure de se préparer à installer les
+          programmes Binutils dans le répertoire
+          <filename class="directory">/tools</filename>.</para>.
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><parameter>--disable-nls</parameter></term>
         <listitem>
-          <para>This disables internationalization as i18n is not needed for the
-          temporary tools.</para>
+          <para>Ceci désactive l'internationalisation comme i18n car ce n'est pas
+          nécessaire pour des outils temporaires.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><parameter>--disable-werror</parameter></term>
         <listitem>
-          <para>This prevents the build from stopping in the event that there
-          are warnings from the host's compiler.</para>
+          <para>Ceci empêche la compilation de s'arrêter lorsqu'interviennent des
+          événements comme des avertissements du compilateur du système 
+          hôte.</para>
         </listitem>
       </varlistentry>
 
     </variablelist>
 
-    <para>Continue with compiling the package:</para>
+    <para>Continuez avec la compilation du paquet&nbsp;:</para
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>Compilation is now complete. Ordinarily we would now run the
-    test suite, but at this early stage the test suite framework (Tcl,
-    Expect, and DejaGNU) is not yet in place. The benefits of running the
-    tests at this point are minimal since the programs from this
-    first pass will soon be replaced by those from the second.</para>
+    <para>La compilation est maintenant terminée. Normalement, la suite
+    de tests devrait être lancée mais, à ce moment, l'ensemble de
+    travail de la suite de tests (Tcl, Expect et DejaGnu) n'est pas
+    encore en place. Les bénéfices à lancer les tests maintenant
+    seraient minimes car les programmes de la première passe seront
+    bientôt remplacés par ceux de la seconde.</para>
 
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
-    <para>Next, prepare the linker for the <quote>Adjusting</quote> phase
-    later on:</para>
+    <para>Ensuite, préparez l'éditeur de liens pour la phase
+    d'<quote>ajustement</quote> un peu plus tard&nbsp;:</para>
 
 <screen><userinput remap="adjust">make -C ld clean
 make -C ld LIB_PATH=/tools/lib
 cp -v ld/ld-new /tools/bin</userinput></screen>
 
     <variablelist>
-      <title>The meaning of the make parameters:</title>
+      <title>Voici la signification des paramètres de make&nbsp;:</title>
 
       <varlistentry>
         <term><parameter>-C ld clean</parameter></term>
         <listitem>
-          <para>This tells the make program to remove all compiled
-          files in the <filename class="directory">ld</filename>
-          subdirectory.</para>
+          <para>Ceci indique au programme make de supprimer tous les fichiers
+          compilés du sous-répertoire <filename class="directory">ld</filename>.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><parameter>-C ld LIB_PATH=/tools/lib</parameter></term>
         <listitem>
-          <para>This option rebuilds everything in the <filename
-          class="directory">ld</filename> subdirectory. Specifying the
-          <envar>LIB_PATH</envar> Makefile variable on the command line
-          allows us to override the default value and point it to the
-          temporary tools location. The value of this variable specifies
-          the linker's default library search path. This preparation is
-          used later in the chapter.</para>
+          <para>Cette option reconstruit tout ce qui se trouve dans le
+          sous-répertoire <filename class="directory">ld</filename>. Spécifier
+          la variable makefile <envar>LIB_PATH</envar> en ligne de commande 
+          nous autorise à écraser la valeur par défaut et à la faire pointer 
+          vers notre emplacement temporaire des outils. La valeur de
+          cette variable spécifie le chemin de recherche des bibliothèques par 
+          défaut pour l'éditeur de liens. Cette préparation est utilisée plus 
+          tard dans le chapitre.</para>
         </listitem>
       </varlistentry>
 
@@ -167,7 +172,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails sur ce paquet sont disponibles dans
     <xref linkend="contents-binutils" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/binutils-pass2.xml BOOKfr/chapter05/binutils-pass2.xml
--- BOOK/chapter05/binutils-pass2.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/binutils-pass2.xml	2008-06-24 07:00:43.000000000 +0100
@@ -14,11 +14,11 @@
     <address>&binutils-url;</address>
   </sect1info>
 
-  <title>Binutils-&binutils-version; - Pass 2</title>
+  <title>Binutils-&binutils-version; - Passe 2</title>
 
   <indexterm zone="ch-tools-binutils-pass2">
     <primary sortas="a-Binutils">Binutils</primary>
-    <secondary>tools, pass 2</secondary>
+    <secondary>outils, passe 2</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,67 +41,71 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Re-installation of Binutils</title>
-
-    <para>Binutils does not recognize versions of Texinfo newer than 4.9.  Fix
-    this issue by applying the following patch:</para>
+    <title>Ré-installation de Binutils</title>
 
+    <para>Binutils ne reconnaît pas les versions de Texinfo supérieures
+    à la 4.9. Réparez ce problème en appliquant le correctif
+    suivant&nbsp;:
+    
 <screen><userinput remap="pre">patch -Np1 -i ../&binutils-configure-patch;</userinput></screen>
 
-    <para>Create a separate build directory again:</para>
+    <para>Créez de nouveau un répertoire de construction
+    séparé&nbsp;:</para>
 
 <screen><userinput remap="pre">mkdir -v ../binutils-build
 cd ../binutils-build</userinput></screen>
 
-    <para>Prepare Binutils for compilation:</para>
+    <para>Préparez la compilation de Binutils&nbsp;:</para>
 
 <screen><userinput remap="configure">../binutils-&binutils-version;/configure --prefix=/tools \
     --disable-nls --with-lib-path=/tools/lib</userinput></screen>
 
     <variablelist>
-      <title>The meaning of the new configure options:</title>
+      <title>Voici la signification des nouvelles options de configure&nbsp;:</title>
 
       <varlistentry>
         <term><parameter>--with-lib-path=/tools/lib</parameter></term>
         <listitem>
-          <para>This tells the configure script to specify the library
-          search path during the compilation of Binutils, resulting in
-          <filename class="directory">/tools/lib</filename> being passed
-          to the linker. This prevents the linker from searching through
-          library directories on the host.</para>
+          <para>Ceci indique au script configure de spécifier le chemin de
+          recherche des bibliothèques lors de la compilation de Binutils, aboutissant au
+          passage de
+          <filename class="directory">/tools/lib</filename> à l'éditeur de
+          liens. Ceci empêche l'éditeur de liens de chercher dans tous les répertoires de
+          bibliothèques de l'hôte.</para>
         </listitem>
       </varlistentry>
 
     </variablelist>
 
-    <para>Compile the package:</para>
+    <para>Compilez le paquet&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>Compilation is now complete. As discussed earlier, running the
-    test suite is not mandatory for the temporary tools here in this
-    chapter. To run the Binutils test suite anyway, issue the following
-    command:</para>
+    <para>La compilation est maintenant terminée. Comme dit précédemment, lancer les
+    suites de tests n'est pas nécessaire pour les outils temporaires dans ce
+    chapitre. Néanmoins, pour lancer la suite de tests Binutils, lancez la commande
+    suivante&nbsp;:</para>
 
 <screen><userinput remap="test">make check</userinput></screen>
 
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
-    <para>Now prepare the linker for the <quote>Re-adjusting</quote> phase in
-    the next chapter:</para>
+    <para>Maintenant, préparez l'éditeur de liens pour la phase de
+    <quote>Ré-ajustement</quote> du prochain chapitre&nbsp;:</para>
 
 <screen><userinput remap="adjust">make -C ld clean
 make -C ld LIB_PATH=/usr/lib:/lib
 cp -v ld/ld-new /tools/bin</userinput></screen>
 
+
   </sect2>
 
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails sur ce paquet sont disponibles dans
     <xref linkend="contents-binutils" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/bison.xml BOOKfr/chapter05/bison.xml
--- BOOK/chapter05/bison.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/bison.xml	2008-06-24 09:12:42.000000000 +0100
@@ -18,7 +18,7 @@
 
   <indexterm zone="ch-tools-bison">
     <primary sortas="a-Bison">Bison</primary>
-    <secondary>tools</secondary>
+    <secondary>outils</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,21 +41,21 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Bison</title>
+    <title>Installation de Bison</title>
 
-    <para>Prepare Bison for compilation:</para>
+    <para>Préparez la compilation de Bison&nbsp;:</para>
 
 <screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
 
-    <para>Compile the package:</para>
+    <para>Compilez le paquet&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>To test the results, issue:</para>
+    <para>Pour tester les résultats, lancez&nbsp;:</para>
 
 <screen><userinput remap="test">make check</userinput></screen>
 
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
@@ -64,7 +64,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails de ce paquet sont situés dans
     <xref linkend="contents-bison" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/bzip2.xml BOOKfr/chapter05/bzip2.xml
--- BOOK/chapter05/bzip2.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/bzip2.xml	2008-06-24 07:10:39.000000000 +0100
@@ -18,7 +18,7 @@
 
   <indexterm zone="ch-tools-bzip2">
     <primary sortas="a-Bzip2">Bzip2</primary>
-    <secondary>tools</secondary>
+    <secondary>outils</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,14 +41,14 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Bzip2</title>
+    <title>Installation de Bzip2</title>
 
-    <para>The Bzip2 package does not contain a <command>configure</command>
-    script. Compile and test it with:</para>
+    <para>Le paquet Bzip2 ne contient pas de script <command>configure</command>.
+    Compilez-le et testez-le avec&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make PREFIX=/tools install</userinput></screen>
 
@@ -57,7 +57,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails sur ce paquet sont situés dans
     <xref linkend="contents-bzip2" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/changingowner.xml BOOKfr/chapter05/changingowner.xml
--- BOOK/chapter05/changingowner.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/changingowner.xml	2008-06-24 09:10:51.000000000 +0100
@@ -8,46 +8,52 @@
 <sect1 id="ch-tools-changingowner">
   <?dbhtml filename="changingowner.html"?>
 
-  <title>Changing Ownership</title>
+  <title>Changer de propriétaire</title>
 
   <note>
-    <para>The commands in the remainder of this book must be performed while
-    logged in as user <systemitem class="username">root</systemitem> and no
-    longer as user <systemitem class="username">lfs</systemitem>. Also, double
-    check that <envar>$LFS</envar> is set in <systemitem
-    class="username">root</systemitem>'s environment.</para>
+    <para>Les commandes dans la suite de ce livre doivent être exécutées alors
+    que vous êtes connecté en tant que 
+    <systemitem class="username">root</systemitem> et non connecté en tant que
+    qu'utilisateur <systemitem class="username">lfs</systemitem>. Contrôlez
+    à nouveau que <envar>$LFS</envar> est paramétré dans l'environnement de
+    <systemitem class="username">root</systemitem>.</para>
   </note>
 
-  <para>Currently, the <filename class="directory">$LFS/tools</filename> directory
-  is owned by the user <systemitem class="username">lfs</systemitem>, a user
-  that exists only on the host system. If the <filename
-  class="directory">$LFS/tools</filename> directory is kept as is, the files are
-  owned by a user ID without a corresponding account. This is dangerous because
-  a user account created later could get this same user ID and would own the
-  <filename class="directory">$LFS/tools</filename> directory and all the files
-  therein, thus exposing these files to possible malicious manipulation.</para>
-
-  <para>To avoid this issue, you could add the <systemitem
-  class="username">lfs</systemitem> user to the new LFS system later when
-  creating the <filename>/etc/passwd</filename> file, taking care to assign it
-  the same user and group IDs as on the host system. Better yet, change the
-  ownership of the <filename class="directory">$LFS/tools</filename> directory to
-  user <systemitem class="username">root</systemitem> by running the following
-  command:</para>
+  <para>Pour l'instant, le répertoire
+  <filename class="directory">$LFS/tools</filename> appartient à l'utilisateur
+  <systemitem class="username">lfs</systemitem>, un utilisateur
+  qui n'existe que sur le système hôte. Si le répertoire
+  <filename class="directory">$LFS/tools</filename> reste ainsi, les fichiers 
+  appartiennent à un ID utilisateur sans compte correspondant. C'est dangereux
+  car un compte utilisateur créé plus tard pourrait se voir attribuer ce même
+  ID utilisateur et être propriétaire du répertoire
+  <filename class="directory">$LFS/tools</filename> et de tous les fichiers  
+  à l'intérieur, les exposant ainsi à des manipulations suspectes.</para>
+
+  <para>Pour éviter ce problème, vous pourriez ajouter l'utilisateur
+   <systemitem class="username">lfs</systemitem> au nouveau système LFS
+   plus tard lorsque vous créeriez le fichier <filename>/etc/passwd</filename>, en prenant garde à 
+  assigner les ID utilisateur et groupe de la même manière que sur le
+  Système hôte. Mieux encore, changez le propriétaire du répertoire 
+  <filename class="directory">$LFS/tools</filename> en le rendant à l'utilisateur
+  <systemitem class="username">root</systemitem> en exécutant les commandes
+  suivantes&nbsp;:</para>
 
 <screen><userinput>chown -R root:root $LFS/tools</userinput></screen>
 
-  <para>Although the <filename class="directory">$LFS/tools</filename> directory
-  can be deleted once the LFS system has been finished, it can be retained to build
-  additional LFS systems <emphasis>of the same book version</emphasis>. How best
-  to backup <filename class="directory">$LFS/tools</filename> is a matter of
-  personal preference and is left as an exercise for the reader.</para>
+  <para>Bien que le dossier <filename class="directory">$LFS/tools</filename> 
+  puisse être effacé quand la construction du système sera fini, il peut être conservé 
+  pour construire des systèmes LFS supplémentaires <emphasis>de la même
+  version du livre</emphasis>. La meilleure façon de sauvegarder
+  <filename class="directory">$LFS/tools</filename> est celle qui correspond à
+  vos préférences personnelles et nous laissons le choix au lecteur.</para>
 
   <caution>
-    <para>If you intend to keep the temporary tools for use in building future LFS
-    systems, <emphasis>now</emphasis> is the time to back them up. Subsequent
-    commands in chapter 6 will alter the tools currently in place, rendering them
-    useless for future builds.</para>
+    <para>Si vous souhaitez conserver les outils temporaires pour un usage dans
+    la construction de futurs systèmes LFS, c'est  le moment 
+    <emphasis>à présent</emphasis> de les sauvegarder. Les commandes qu'implique
+    le chapitre 6 vont  modifier les outils actuellement en place, les rendant
+    inutiles pour de futures constructions.</para>
   </caution>
 
 </sect1>
diff -Naur BOOK/chapter05/chapter05.xml BOOKfr/chapter05/chapter05.xml
--- BOOK/chapter05/chapter05.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/chapter05.xml	2008-06-23 21:52:55.000000000 +0100
@@ -5,11 +5,11 @@
   %general-entities;
 ]>
 
-<chapter id="chapter-temporary-tools" xreflabel="Chapter 5">
+<chapter id="chapter-temporary-tools" xreflabel="Chapitre 5">
   <?dbhtml dir="chapter05"?>
   <?dbhtml filename="chapter05.html"?>
 
-  <title>Constructing a Temporary System</title>
+  <title>Construire un système temporaire</title>
 
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="introduction.xml"/>
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="toolchaintechnotes.xml"/>
diff -Naur BOOK/chapter05/coreutils.xml BOOKfr/chapter05/coreutils.xml
--- BOOK/chapter05/coreutils.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/coreutils.xml	2008-06-24 07:21:28.000000000 +0100
@@ -18,7 +18,7 @@
 
   <indexterm zone="ch-tools-coreutils">
     <primary sortas="a-Coreutils">Coreutils</primary>
-    <secondary>tools</secondary>
+    <secondary>outils</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,48 +41,50 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Coreutils</title>
+    <title>Installation de Coreutils</title>
 
-    <para>Prepare Coreutils for compilation:</para>
+    <para>Préparez la compilation de Coreutils&nbsp;:</para>
 
-<screen><userinput remap="configure">./configure --prefix=/tools --enable-install-program=hostname</userinput></screen>
+<screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
 
     <variablelist>
-      <title>The meaning of the configure options:</title>
-
+      <title<Voici la signification des options de configuration&nbsp;:</para>
+      
       <varlistentry>
         <term><envar>--enable-install-program=hostname</envar></term>
         <listitem>
-          <para>This enables the <command>hostname</command> binary to be built
-          and installed &ndash; it is disabled by default but is required by the
-          Perl test suite.</para>
+          <para>Ceci fait que le binaire <command>hostname</command> sera compilé
+          et installé &ndash; ceci est désactivé par défaut mais c'est requis
+          par la suite de tests de Perl./para>
+          
         </listitem>
       </varlistentry>
-    </variablelist>
+   </variablelist>
 
-    <para>Compile the package:</para>
+    <para>Compilez le paquet&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>To test the results, issue:</para>
+    <para>Pour tester les résultats, lancez&nbsp;:</para>
 
 <screen><userinput remap="test">make RUN_EXPENSIVE_TESTS=yes check</userinput></screen>
 
-    <para>The <parameter>RUN_EXPENSIVE_TESTS=yes</parameter> parameter tells the
-    test suite to run several additional tests that are considered
-    relatively expensive (in terms of CPU power and memory usage) on some
-    platforms, but generally are not a problem on Linux.</para>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-    <para>The above command refuses to install <filename>su</filename>
-    because it cannot install it setuid root as a non-privileged user. By
-    manually installing it with a different name, we can use it for running
-    tests in the final system as a non-privileged user and we keep a possibly
-    useful <command>su</command> from our host first place in our PATH. Install
-    it with:</para>
+    <para>Le paramètre <parameter>RUN_EXPENSIVE_TESTS=yes</parameter>  indique à 
+    la suite de tests de lancer quelques tests supplémentaires, considérés 
+    relativement coûteux (en terme de puissance CPU et d'utilisation mémoire) 
+    mais habituellement sans problème sous Linux.</para>
+
+    <para>Installez le paquet&nbsp;:</para>
+
+<screen><userinputremap="install">make install</userinput></screen>
+
+    <para>La commande ci-dessus refuse l'installation de <filename>su</filename>
+    car il ne peut  installer l'uid de root en tant qu'utilisateur non
+    privilégié. En l'installant à la  main avec un nom différent, nous pouvons
+    l'utiliser pour exécuter les tests dans le système final en tant
+    qu'utilisateur non privilégié et nous conservons un <command>su</command>
+    utile de notre système hôte effacé dans la PATH. Installez-le
+    avec&nbsp:</para>
 
 <screen><userinput remap="install">cp -v src/su /tools/bin/su-tools</userinput></screen>
 
@@ -91,7 +93,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails sur ce paquet sont disponibles dans
     <xref linkend="contents-coreutils" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/dejagnu.xml BOOKfr/chapter05/dejagnu.xml
--- BOOK/chapter05/dejagnu.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/dejagnu.xml	2008-06-23 23:32:50.000000000 +0100
@@ -23,8 +23,8 @@
   <sect2 role="package">
     <title/>
 
-    <para>The DejaGNU package contains a framework for testing other
-    programs.</para>
+    <para>Le paquet DejaGNU contient un ensemble de travail pour tester d'autres
+    programmes.</para>
 
     <segmentedlist>
       <segtitle>&buildtime;</segtitle>
@@ -39,17 +39,17 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of DejaGNU</title>
+    <title>Installation de DejaGNU</title>
 
-    <para>Prepare DejaGNU for compilation:</para>
+    <para>Préparez la compilation de DejaGNU&nbsp;:</para>
 
 <screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
 
-    <para>Build and install the package:</para>
+    <para>Construisez et installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
-    <para>To test the results, issue:</para>
+    <para>Pour tester le résultat, lancez&nbsp;:</para>
 
 <screen><userinput remap="test">make check</userinput></screen>
 
@@ -57,10 +57,10 @@
 
 
   <sect2 id="contents-dejagnu" role="content">
-    <title>Contents of DejaGNU</title>
+    <title>Contenu de DejaGNU</title>
 
     <segmentedlist>
-      <segtitle>Installed program</segtitle>
+      <segtitle>Programme installé</segtitle>
 
       <seglistitem>
         <seg>runtest</seg>
@@ -68,15 +68,16 @@
     </segmentedlist>
 
     <variablelist>
-      <bridgehead renderas="sect3">Short Descriptions</bridgehead>
+      <bridgehead renderas="sect3">Courte descriptions</bridgehead>
       <?dbfo list-presentation="list"?>
       <?dbhtml list-presentation="table"?>
 
       <varlistentry id="runtest">
         <term><command>runtest</command></term>
         <listitem>
-          <para>A wrapper script that locates the proper
-          <command>expect</command> shell and then runs DejaGNU</para>
+          <para>Un script d'emballage qui trouve le bon shell
+          <command>expect</command>,
+          puis qui lance DejaGNU</para>
           <indexterm zone="ch-tools-dejagnu runtest">
             <primary sortas="b-runtest">runtest</primary>
           </indexterm>
diff -Naur BOOK/chapter05/diffutils.xml BOOKfr/chapter05/diffutils.xml
--- BOOK/chapter05/diffutils.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/diffutils.xml	2008-06-24 07:24:29.000000000 +0100
@@ -18,7 +18,7 @@
 
   <indexterm zone="ch-tools-diffutils">
     <primary sortas="a-Diffutils">Diffutils</primary>
-    <secondary>tools</secondary>
+    <secondary>outils</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,19 +41,19 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Diffutils</title>
+    <title>Installation de Diffutils</title>
 
-    <para>Prepare Diffutils for compilation:</para>
+    <para>Préparez la compilation de Diffutils&nbsp;:</para>
 
 <screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
 
-    <para>Compile the package:</para>
+    <para>Compilez le paquet&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>This package does not come with a test suite.</para>
+    <para>Ce paquet ne contient pas de suite de tests.</para>
 
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
@@ -62,7 +62,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails sur ce paquet sont situés dans
     <xref linkend="contents-diffutils" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/e2fsprogs.xml BOOKfr/chapter05/e2fsprogs.xml
--- BOOK/chapter05/e2fsprogs.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/e2fsprogs.xml	2008-06-24 07:31:22.000000000 +0100
@@ -40,23 +40,24 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of E2fsprogs</title>
+    <title>Installation de E2fsprogs</title>
 
-    <para>The E2fsprogs documentation recommends that the package be built in
-    a subdirectory of the source tree: </para>
+    <para>La documentation de E2fsprogs recommande de construire E2fsprogs 
+    dans un sous-répertoire du répertoire source&nbsp;:</para>
 
 <screen><userinput remap="pre">mkdir -v build
 cd build</userinput></screen>
 
-    <para>Prepare E2fsprogs for compilation:</para>
+    <para>Préparez la compilation d'E2fsprogs&nbsp;:</para>
 
 <screen><userinput remap="configure">../configure --prefix=/tools</userinput></screen>
 
-    <para>Compile the package:</para>
+    <para>Compilez le paquet&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>Install the static libraries and headers required by Util-linux-ng:</para>
+    <para>Installez les bibliothèques statiques et les en-têtes exigées par
+    Util-linux-ng:</para>
 
 <screen><userinput remap="install">make install-libs</userinput></screen>
 
@@ -65,7 +66,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails sur ce paquet sont disponibles dans
     <xref linkend="contents-e2fsprogs" role="."/></para>
   </sect2>
 
diff -Naur BOOK/chapter05/expect.xml BOOKfr/chapter05/expect.xml
--- BOOK/chapter05/expect.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/expect.xml	2008-06-23 23:28:15.000000000 +0100
@@ -8,11 +8,11 @@
 <sect1 id="ch-tools-expect" role="wrap">
   <?dbhtml filename="expect.html"?>
 
-  <sect1info condition="script">
-    <productname>expect</productname>
-    <productnumber>&expect-version;</productnumber>
-    <address>&expect-url;</address>
-  </sect1info>
+   <sect1info condition="script">
+     <productname>expect</productname>
+     <productnumber>&expect-version;</productnumber>
+     <address>&expect-url;</address>
+   </sect1info>
 
   <title>Expect-&expect-version;</title>
 
@@ -23,8 +23,8 @@
   <sect2 role="package">
     <title/>
 
-    <para>The Expect package contains a program for carrying out scripted
-    dialogues with other interactive programs.</para>
+    <para>Le paquet Expect contient un programme pour réaliser des dialogues
+    scriptés avec d'autres programmes interactifs.</para>
 
     <segmentedlist>
       <segtitle>&buildtime;</segtitle>
@@ -39,85 +39,88 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Expect</title>
+    <title>Installation de Expect</title>
 
-    <para>First, fix a bug that can result in false failures during the GCC test
-    suite run:</para>
+    <para>Tout d'abord, corrigez un bogue aboutissant en de nombreux faux
+    échecs lors de l'exécution de la suite de tests de GCC&nbsp;:</para>
 
 <screen><userinput remap="pre">patch -Np1 -i ../&expect-spawn-patch;</userinput></screen>
 
-    <para>Next, force Expect's configure script to use <filename>/bin/stty</filename>
-    instead of a <filename>/usr/local/bin/stty</filename> it may find on the host system.
-    This will ensure that our testsuite tools remain sane for the final builds of our
-    toolchain:</para>
+     <para>Ensuite, forcez le script configure de expect à utiliser
+     <filename>/bin/stty</filename> au lieu d'un 
+     <filename>/usr/local/bin/stty</filename> qu'il pourrait trouver sur le 
+     système hôte. Cela garantira que nos outils de test demeurent propres 
+     pour les constructions finales de l'ensemble d'outils&nbsp;:</para>
 
 <screen><userinput remap="pre">cp configure{,.bak}
 sed 's:/usr/local/bin:/bin:' configure.bak &gt; configure</userinput></screen>
 
-    <para>Now prepare Expect for compilation:</para>
+    <para>Construisez maintenant le paquet&nbsp;:</para>
 
 <screen><userinput remap="configure">./configure --prefix=/tools --with-tcl=/tools/lib \
   --with-tclinclude=/tools/include --with-x=no</userinput></screen>
 
     <variablelist>
-      <title>The meaning of the configure options:</title>
+      <title>Voici la signification des options de configure&nbsp;:</title>
 
       <varlistentry>
         <term><parameter>--with-tcl=/tools/lib</parameter></term>
         <listitem>
-          <para>This ensures that the configure script finds the Tcl
-          installation in the temporary tools location instead of possibly
-          locating an existing one on the host system.</para>
+          <para>Ceci nous assure que le script configure trouve l'installation
+          Tcl dans l'emplacement temporaire des outils à la place d'un résidant 
+          sur le système hôte.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><parameter>--with-tclinclude=/tools/include</parameter></term>
         <listitem>
-          <para>This explicitly tells Expect where to find Tcl's internal
-          headers. Using this option avoids conditions where
-          <command>configure</command> fails because it cannot automatically
-          discover the location of Tcl's headers.</para>
+          <para>Ceci indique explicitement à Expect où trouver le répertoire
+          des sources de Tcl et ses en-têtes internes. Utiliser cette option évite
+          certaines conditions d'échec pour 
+          <command>configure</command> s'il ne peut
+          pas découvrir automatiquement l'emplacement des en-têtes de Tcl.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><parameter>--with-x=no</parameter></term>
         <listitem>
-          <para>This tells the configure script not to search for Tk (the
-          Tcl GUI component) or the X Window System libraries, both of which
-          may reside on the host system but will not exist in the temporary
-          environment.</para>
+          <para>Ceci indique au script configure de ne pas chercher Tk (le
+          composant interface de Tcl) ou les bibliothèques d'X Window System, les deux
+          pouvant résider sur le système hôte mais n'existant pas sur l'environnement
+          temporaire.</para>
         </listitem>
       </varlistentry>
 
     </variablelist>
 
-    <para>Build the package:</para>
+    <para>Construisez le paquet&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>To test the results, issue:</para>
-
+    <para>Pour tester les résultats, lancez&nbsp;:
+    
 <screen><userinput remap="test">make test</userinput></screen>
 
-    <para>Note that the Expect test suite is known to experience failures under
-    certain host conditions that are not within our control. Therefore,
-    test suite failures here are not surprising and are not considered
-    critical.</para>
+    <para>Notez que la suite de tests d'Expect est connue pour
+    avoir de nombreux échecs sous certaines conditions de l'hôte, conditions
+    qui ne sont pas de notre ressort. Du coup, les échecs de la suite de
+    tests ne sont pas surprenants et ne sont pas considérés comme
+    critiques.</para>
 
-    <para>Install the package:</para>
+    <para>Installez-le&nbsp;:</para>
 
 <screen><userinput remap="install">make SCRIPTS="" install</userinput></screen>
 
     <variablelist>
-      <title>The meaning of the make parameter:</title>
+      <title>Voici la signification du paramètre de make&nbsp;:</title>
 
       <varlistentry>
         <term><parameter>SCRIPTS=""</parameter></term>
         <listitem>
-          <para>This prevents installation of the supplementary Expect
-          scripts, which are not needed.</para>
+          <para>Ceci empêche l'installation de scripts expect supplémentaires 
+          non nécessaires.</para>
         </listitem>
       </varlistentry>
 
@@ -126,11 +129,11 @@
   </sect2>
 
   <sect2 id="contents-expect" role="content">
-    <title>Contents of Expect</title>
+    <title>Contenu d'Expect</title>
 
     <segmentedlist>
-      <segtitle>Installed program</segtitle>
-      <segtitle>Installed library</segtitle>
+      <segtitle>Programme installé</segtitle>
+      <segtitle>Bibliothèque installée</segtitle>
 
       <seglistitem>
         <seg>expect</seg>
@@ -139,15 +142,15 @@
     </segmentedlist>
 
     <variablelist>
-      <bridgehead renderas="sect3">Short Descriptions</bridgehead>
+      <bridgehead renderas="sect3">Courte description</bridgehead>
       <?dbfo list-presentation="list"?>
       <?dbhtml list-presentation="table"?>
 
       <varlistentry id="expect">
         <term><command>expect</command></term>
         <listitem>
-          <para>Communicates with other interactive programs according
-          to a script</para>
+          <para>Communique avec les autres programmes interactifs suivant un
+          script.</para>
           <indexterm zone="ch-tools-expect expect">
             <primary sortas="b-expect">expect</primary>
           </indexterm>
@@ -157,8 +160,9 @@
       <varlistentry id="libexpect">
         <term><filename class="libraryfile">libexpect-&expect-lib-version;.a</filename></term>
         <listitem>
-          <para>Contains functions that allow Expect to be used as a Tcl
-          extension or to be used directly from C or C++ (without Tcl)</para>
+          <para>Contient des fonctions qui permettent à Expect d'être utilisé comme une
+          extension Tcl ou d'être utilisé directement à partir du langage C ou du langage
+          C++ (sans Tcl)</para>
           <indexterm zone="ch-tools-expect libexpect">
             <primary sortas="c-libexpect-&expect-lib-version;">libexpect-&expect-lib-version;</primary>
           </indexterm>
diff -Naur BOOK/chapter05/findutils.xml BOOKfr/chapter05/findutils.xml
--- BOOK/chapter05/findutils.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/findutils.xml	2008-06-24 07:33:52.000000000 +0100
@@ -18,7 +18,7 @@
 
   <indexterm zone="ch-tools-findutils">
     <primary sortas="a-Findutils">Findutils</primary>
-    <secondary>tools</secondary>
+    <secondary>outils</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,21 +41,21 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Findutils</title>
+    <title>Installation de Findutils</title>
 
-    <para>Prepare Findutils for compilation:</para>
+    <para>Préparez la compilation de Findutils&nbsp;:</para>
 
 <screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
 
-    <para>Compile the package:</para>
+    <para>Compilez le paquet&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>To test the results, issue:</para>
+    <para>Pour tester les résultats, lancez&nbsp;:</para>
 
 <screen><userinput remap="test">make check</userinput></screen>
 
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
@@ -64,7 +64,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails sur ce paquet sont situés dans
     <xref linkend="contents-findutils" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/flex.xml BOOKfr/chapter05/flex.xml
--- BOOK/chapter05/flex.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/flex.xml	2008-06-24 09:15:44.000000000 +0100
@@ -18,7 +18,7 @@
 
   <indexterm zone="ch-tools-flex">
     <primary sortas="a-Flex">Flex</primary>
-    <secondary>tools</secondary>
+    <secondary>outils</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,33 +41,34 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Flex</title>
+    <title>Installation de Flex</title>
 
-    <para>Flex contains several known bugs. These can be fixed with the
-    following patch:</para>
+    <para>Flex contient des bogues connus. Vous pouvez les corriger grâce au
+    correctif suivant&nbsp;:</para>
 
 <screen><userinput remap="pre">patch -Np1 -i ../&flex-fixes-patch;</userinput></screen>
 
-    <para>The GNU autotools will detect that the Flex source code has been
-    modified by the previous patch and tries to update the man page
-    accordingly.  This does not work on many systems, and the default page is
-    fine, so make sure it does not get regenerated:</para>
+    <para>GNU autotools détecte que le code source de Flex a été modifié par
+    le correctif précédent et essaie de mettre à jour la page de manuel 
+    en conséquence. Cela ne fonctionne pas sur la plupart des systèmes, et la
+    page par défaut est très bien, donc assurez-vous qu'elle ne sera pas
+    régénérée&nbsp;:</para>
 
 <screen><userinput remap="pre">touch doc/flex.1</userinput></screen>
 
-    <para>Now prepare Flex for compilation:</para>
+    <para>Maintenant, préparez la compilation de Flex&nbsp;:</para>
 
 <screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
 
-    <para>Compile the package:</para>
+    <para>Compilez le paquet&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>To test the results, issue:</para>
+    <para>Pour tester les résultats, lancez&nbsp;:</para>
 
 <screen><userinput remap="test">make check</userinput></screen>
 
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
@@ -76,7 +77,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails de ce paquet sont situés dans
     <xref linkend="contents-flex" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/gawk.xml BOOKfr/chapter05/gawk.xml
--- BOOK/chapter05/gawk.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/gawk.xml	2008-06-24 07:37:16.000000000 +0100
@@ -18,7 +18,7 @@
 
   <indexterm zone="ch-tools-gawk">
     <primary sortas="a-Gawk">Gawk</primary>
-    <secondary>tools</secondary>
+    <secondary>outils</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,21 +41,21 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Gawk</title>
+    <title>Installation de Gawk</title>
 
-    <para>Prepare Gawk for compilation:</para>
+    <para>Préparez la compilation de Gawk&nbsp;:</para>
 
 <screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
 
-    <para>Compile the package:</para>
+    <para>Compilez le paquet&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>To test the results, issue:</para>
-
+    <para>Pour tester le résultat, lancez&nbsp;:</para>
+    
 <screen><userinput remap="test">make check</userinput></screen>
 
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
@@ -64,7 +64,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails sur ce paquet sont situés dans
     <xref linkend="contents-gawk" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/gcc-pass1.xml BOOKfr/chapter05/gcc-pass1.xml
--- BOOK/chapter05/gcc-pass1.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/gcc-pass1.xml	2008-06-23 22:38:47.000000000 +0100
@@ -8,17 +8,17 @@
 <sect1 id="ch-tools-gcc-pass1" role="wrap">
   <?dbhtml filename="gcc-pass1.html"?>
 
-  <sect1info condition="script">
-    <productname>gcc</productname>
-    <productnumber>&gcc-version;</productnumber>
-    <address>&gcc-url;</address>
-  </sect1info>
+<sect1info condition="script">
+     <productname>gcc</productname>
+     <productnumber>&gcc-version;</productnumber>
+     <address>&gcc-url;</address>
+</sect1info>
 
-  <title>GCC-&gcc-version; - Pass 1</title>
+  <title>GCC-&gcc-version; - Passe 1</title>
 
   <indexterm zone="ch-tools-gcc-pass1">
     <primary sortas="a-GCC">GCC</primary>
-    <secondary>tools, pass 1</secondary>
+    <secondary>outils, passe 1</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,92 +41,95 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of GCC</title>
+    <title>Installation de GCC</title>
 
-    <para>The GCC documentation recommends building GCC outside of the
-    source directory in a dedicated build directory:</para>
+    <para>La documentation de GCC recommande de ne pas construire GCC dans le
+    répertoire des sources mais dans un répertoire de construction dédié&nbsp;:</para>
 
-<screen><userinput remap="pre">mkdir -v ../gcc-build
+<screen><userinput remap="pre">mkdir -v ../gcc-build  
 cd ../gcc-build</userinput></screen>
 
-    <para>Prepare GCC for compilation:</para>
+    <para>Préparez la compilation de GCC&nbsp;:</para>
 
 <screen><userinput remap="configure">CC="gcc -B/usr/bin/" ../gcc-&gcc-version;/configure --prefix=/tools \
-    --with-local-prefix=/tools --disable-nls --enable-shared \
-    --enable-languages=c</userinput></screen>
+     --with-local-prefix=/tools --disable-nls --enable-shared \
+     --enable-languages=c</userinput></screen>
 
     <variablelist>
-      <title>The meaning of the configure options:</title>
+      <title>Voici la signification des options de configure&nbsp;:</title>
 
       <varlistentry>
         <term><envar>CC="gcc -B/usr/bin/"</envar></term>
         <listitem>
-          <para>This forces <command>gcc</command> to prefer the linker from
-          the host in <filename class="directory">/usr/bin</filename>. This
-          is necessary on some hosts where the new <command>ld</command>
-          built in the previous section is not compatible with the host's
-          <command>gcc</command>.</para>
+          <para>Ceci oblige <command>gcc</command> à préférer l'éditeur de liens
+          du système hôte dans <filename class="directory">/usr/bin</filename>.
+          C'est nécessaire sur certains systèmes hôtes où le nouveau <command>ld</command>
+          compilé dans la section précédente n'est pas compatible avec le 
+          <command>gcc</command> du système hôte.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><parameter>--with-local-prefix=/tools</parameter></term>
         <listitem>
-          <para>The purpose of this switch is to remove <filename
-          class="directory">/usr/local/include</filename> from
-          <command>gcc</command>'s include search path. This is not
-          absolutely essential, however, it helps to minimize the
-          influence of the host system.</para>
+          <para>Le but de cette option est de supprimer
+          <filename class="directory">/usr/local/include</filename> du chemin 
+          de recherche des fichiers include de
+          <command>gcc</command>. Ce n'est pas absolument
+          essentiel&nbsp;; néanmoins, c'est une aide pour minimiser l'influence 
+          du système hôte.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><parameter>--enable-shared</parameter></term>
         <listitem>
-          <para>This switch allows the building of <filename
-          class="libraryfile">libgcc_s.so.1</filename> and
+          <para>Cette option permet la construction de
+          <filename class="libraryfile">libgcc_s.so.1</filename> et
           <filename class="libraryfile">libgcc_eh.a</filename>.
-          Having <filename class="libraryfile">libgcc_eh.a</filename>
-          available ensures that the configure script for Glibc (the
-          next package we compile) produces the proper results.</para>
+          Disposer de <filename class="libraryfile">libgcc_eh.a</filename>
+          nous assure que le script configure
+          de Glibc (le prochain paquet à compiler) produira de bons résultats.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><parameter>--enable-languages=c</parameter></term>
         <listitem>
-          <para>This option ensures that only the C compiler is built.</para>
+          <para>Cette option nous assure que seul le compilateur C sera
+          construit.</para>
         </listitem>
       </varlistentry>
 
     </variablelist>
 
-    <para>The following command will compile GCC not once, but several times. It
-    uses the programs compiled in a first round to compile itself a second time,
-    and then again a third time. It then compares these second and third compiles
-    to make sure it can reproduce itself flawlessly. This is called
-    <quote>bootstrapping</quote>. Building GCC in this way ensures that it was
-    compiled correctly and is now the default configuration for the released
-    package. Continue with compiling by running:</para>
+    <para>La commande suivante ne va pas compiler GCC qu'une fois mais 
+    plusieurs fois. Elle utilise les programmes compilés dans le premier tour pour se 
+    compiler une deuxième fois, puis une troisième fois. Il compare alors 
+    les deuxième et troisième compilations pour s'assurer qu'il arrive à 
+    se reproduire lui-même proprement. Cela s'appelle le
+    <quote>bootstrapping</quote>. Compiler Glibc de cette façon assure que
+    GCC est compilé correctement et c'est à présent la configuration par défaut
+    pour le paquet actuel. Continuez avec la compilation du paquet&nbsp;:
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>Compilation is now complete. At this point, the test suite would
-    normally be run, but, as mentioned before, the test suite framework is
-    not in place yet. The benefits of running the tests at this point
-    are minimal since the programs from this first pass will soon be
-    replaced.</para>
+    <para>La compilation est maintenant terminée. À ce point, la suite de tests
+    devrait être lancée. Mais, comme nous l'avons dit plus tôt, l'ensemble de
+    travail de la suite de tests n'est pas encore en place. Les bénéfices à lancer
+    les tests maintenant seraient minimes car les programmes de la première passe
+    seront bientôt remplacés.</para>
 
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
-    <para>As a finishing touch, create a symlink. Many programs and scripts
-    run <command>cc</command> instead of <command>gcc</command>, which is
-    used to keep programs generic and therefore usable on all kinds of UNIX
-    systems where the GNU C compiler is not always installed. Running
-    <command>cc</command> leaves the system administrator free to decide
-    which C compiler to install:</para>
+    <para>En touche finale, créez un lien symbolique. Beaucoup de programmes
+    lancent <command>cc</command> au lieu de <command>gcc</command>, ceci pour
+    conserver des programmes génériques et donc utilisables sur tout type
+    de système Unix où le compilateur GNU C n'est pas toujours installé. Utiliser
+    <command>cc</command> permet de libérer l'administrateur système dans son choix
+    du compilateur C à installer.</para>
 
 <screen><userinput remap="install">ln -vs gcc /tools/bin/cc</userinput></screen>
 
@@ -135,7 +138,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails sur ce paquet sont disponibles dans
     <xref linkend="contents-gcc" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/gcc-pass2.xml BOOKfr/chapter05/gcc-pass2.xml
--- BOOK/chapter05/gcc-pass2.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/gcc-pass2.xml	2008-06-24 00:15:31.000000000 +0100
@@ -18,7 +18,7 @@
 
   <indexterm zone="ch-tools-gcc-pass2">
     <primary sortas="a-GCC">GCC</primary>
-    <secondary>tools, pass 2</secondary>
+    <secondary>outils, passe 2</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,98 +41,110 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Re-installation of GCC</title>
+    <title>Ré-installation de GCC</title>
 
-    <para>The tools required to test GCC and Binutils&mdash;Tcl, Expect
-    and DejaGNU&mdash;are installed now. GCC and Binutils can now be
-    rebuilt, linking them against the new Glibc and testing them properly
-    (if running the test suites in this chapter). Please note that these
-    test suites are highly dependent on properly functioning PTYs which
-    are provided by the host. PTYs are most commonly implemented via the
-    <systemitem class="filesystem">devpts</systemitem> file system. Check
-    to see if the host system is set up correctly in this regard by
-    performing a quick test:</para>
+    <para>Les outils requis pour tester GCC et Binutils (Tcl, Expect et
+    DejaGnu) sont maintenant installés. GCC et Binutils peuvent maintenant
+    être reconstruits en les liant avec la nouvelle Glibc et en les testant
+    correctement (si vous souhaitez lancer les suites de tests dans ce
+    chapitre). Merci de noter que ces suites de tests dépendent énormément
+    de pseudos terminaux (PTY) fonctionnels fournis par votre distribution
+    hôte. Les PTY sont le plus souvent implémentés via le système de
+    fichiers
+    <systemitem class="filesystem">devpts</systemitem>. Vérifiez si
+    le système hôte est correctement configuré en réalisant un simple
+    test&nbsp;:</para>
 
 <screen><userinput remap="test">expect -c "spawn ls"</userinput></screen>
 
-    <para>The response might be:</para>
+    <para>Le résultat pourrait être&nbsp;:</para>
 
 <screen><computeroutput>The system has no more ptys.
 Ask your system administrator to create more.</computeroutput></screen>
 
-    <para>If the above message is received, the host does not have its PTYs
-    set up properly. In this case, there is no point in running the test
-    suites for GCC and Binutils until this issue is resolved. Please consult
-    the LFS FAQ at <ulink url="&lfs-root;/lfs/faq.html#no-ptys"/> for more
-    information on how to get PTYs working.</para>
-
-    <para>As previously explained in <xref linkend="ch-tools-adjusting"/>,
-    under normal circumstances the GCC <command>fixincludes</command> script
-    is run in order to fix potentially broken header files. As GCC-&gcc-version;
-    and Glibc-&glibc-version; have already been installed at this point, and
-    their respective header files are known to not require fixing, the
-    <command>fixincludes</command> script is not required. As mentioned
-    previously, the script may in fact pollute the build environment by
-    installing fixed headers from the host system into GCC's private include
-    directory. The running of the <command>fixincludes</command> script can
-    be suppressed by issuing the following commands:</para>
+    <para>Si vous obtenez le message ci-dessus, la distribution hôte n'est
+    pas correctement configurée pour les PTY. Dans ce cas, il ne sert à rien
+    de lancer les suites de tests de GCC et Binutils jusqu'à la correction
+    de ce problème. Merci de consulter la FAQ LFS sur
+    <ulink url="&lfs-root;/lfs/faq.html#no-ptys"/>  pour plus d'informations sur la
+    façon de faire fonctionner les PTY.</para>
+
+    <para>Comme déjà expliqué à la section <xref linkend="ch-tools-adjusting"/>,
+    en temps normal le script GCC <command>fixincludes</command> est exécuté
+    afin de réparer des fichiers d'en-tête potentiellement cassés. Comme
+    GCC-&gcc-version; et Glibc-&glibc-version; ont désormais déjà été installés, 
+    et vu que leur fichiers d'en-têtes respectifs sont connus comme n'ayant
+    pas besoin de réparation, le script <command>fixincludes</command> n'est
+    pas utile. Comme mentionné précédemment, il se peut que le script pollue
+    l'environnement de construction en installant des en-têtes corrigées du
+    système hôte dans le répertoire autonome include de GCC. L'exécution du
+    script <command>fixincludes</command> peut être supprimée en lançant les
+    commandes suivantes&nbsp;:</para>
 
 <screen><userinput remap="pre">cp -v gcc/Makefile.in{,.orig}
 sed 's@\./fixinc\.sh@-c true@' gcc/Makefile.in.orig &gt; gcc/Makefile.in</userinput></screen>
 
-    <para>The bootstrap build performed in <xref linkend="ch-tools-gcc-pass1"/>
-    built GCC with the <option>-fomit-frame-pointer</option> compiler flag.
-    Non-bootstrap builds omit this flag by default, so apply the following
-    <command>sed</command> to use it in order to ensure consistent compiler
-    builds:</para>
+    <para>La construction bootstrap effectuée à la section
+    <xref linkend="ch-tools-gcc-pass1"/>
+    a compilé GCC avec le commutateur du compilateur
+    <option>-fomit-frame-pointer</option> compiler flag. Les constructions
+    Non-bootstrap ommettent ce commutateur par défaut, donc appliquez le  
+    correctif <command>sed</command> suivant pour l'utiliser afin de 
+    les constructions des compilateurs cohérent&nbsp;:</para>
 
 <screen><userinput remap="pre">cp -v gcc/Makefile.in{,.tmp}
 sed 's/^XCFLAGS =$/&amp; -fomit-frame-pointer/' gcc/Makefile.in.tmp \
   &gt; gcc/Makefile.in</userinput></screen>
 
-    <para>The following command will change the location of GCC's default
-    dynamic linker to use the one we installed in
-    <filename class="directory">/tools</filename>. It also removes <filename
-    class="directory">/usr/include</filename> from GCC's include search path.
-    Doing this now rather than adjusting the specs file after installation
-    ensures that the new dynamic linker is used during the actual build of
-    GCC. That is, all of the binaries created during the build will link
-    against the new Glibc. Issue:</para>
-
-<screen><userinput remap="pre">for file in $(find gcc/config -name linux64.h -o -name linux.h)
+    <para>La commande suivante modifiera l'emplacement de l'éditeur de lien
+    dynamique de GCC pour utiliser celui que nous avons installé dans
+    <filename class="directory">/tools</filename>. Il supprime aussi
+    <filename class="directory">/usr/include</filename> du chemin de 
+    recherche des en-têtes de GCC.</para>
+
+    <para>Faire cela maintenant plutôt qu'ajuster le fichier specs après
+    l'installation nous assure que l'éditeur de liens dynamiques sera utilisé
+    lors de la construction de GCC. C'est-à-dire, tous les binaires finaux (et
+    temporaires) créés lors de la construction seront liés à la nouvelle Glibc.
+    Lancez&nbsp;:</para>
+    
+<screen><userinput remap="pre">for file in $(find gcc/config -name linux64.h -o -name linux.h) 
 do
-  cp -uv $file{,.orig}
-  sed -e 's@/lib\(64\)\?\(32\)\?/ld@/tools&amp;@g' \
-  -e 's@/usr@/tools@g' $file.orig &gt; $file
-  echo "
+   cp -uv $file{,.orig}
+   sed -e 's@/lib\(64\)\?\(32\)\?/ld@/tools&amp;@g' \
+   -e 's@/usr@/tools@g' $file.orig &gt; $file
+   echo "
 #undef STANDARD_INCLUDE_DIR
 #define STANDARD_INCLUDE_DIR 0" &gt;&gt; $file
-  touch $file.orig
+   touch $file.orig
 done</userinput></screen>
 
-    <para>In case the above seems hard to follow, let's break it down a bit.
-    First we find all the files under the gcc/config directory that are named
-    either <filename>linux.h</filename> or <filename>linux64.h</filename>.
-    For each file found, we copy it to a file of the same name but with an added
-    suffix of <quote>.orig</quote>. Then the first sed expression prepends
-    <quote>/tools</quote> to every instance of <quote>/lib/ld</quote>,
-    <quote>/lib64/ld</quote> or <quote>/lib32/ld</quote>, while the second one
-    replaces hard-coded instances of <quote>/usr</quote>. Then we add our define
-    statements which alter the include search path to the end of the file. Finally,
-    we use <command>touch</command> to update the timestamp on the copied files.
-    When used in conjunction with <command>cp -u</command>, this prevents unexpected
-    changes to the original files in case the command is inadvertently run twice.
-    </para>
+    <para>Si ce qui précède vous semble dur à suivre, décomposons-le un peu.
+    D'abord, nous trouvons tous les fichiers sous le répertoire gcc/config qui
+    sont nommés soit <filename>linux.h</filename> soit
+    <filename>linux64.h</filename>. Pour chaque fichier trouvé, nous le copions
+    vers un fichier du même nom mais avec en plus le suffixe <quote>.orig</quote>.
+    Puis la première expression sed rattafee <quote>/tools</quote> à chaque
+    occurrence de <quote>/lib/ld</quote>, <quote>/lib64/ld</quote> ou
+    <quote>/lib32/ld</quote>, tandis que la deuxième remplace les occurrences
+    <quote>/usr</quote>. liées. Nous ajoutons alors nos déclarations define qui
+    modifie le chemin de recherche à la fin du fichier. Enfin, nous utilisons
+    <command>touch</command> pour mettre à jour la date sur les fichiers copiés.
+    Utilisé conjointement avec <command>cp -u</command>, cela empêche les
+    modifications inattendues des fichiers d'origine au cas où la commande
+    serait exécutée trois fois par inadvertence.</para>
 
-    <para>Create a separate build directory again:</para>
+    <para>De nouveau, créez un répertoire de construction
+    séparé&nbsp;:</para>
 
 <screen><userinput remap="pre">mkdir -v ../gcc-build
 cd ../gcc-build</userinput></screen>
 
-    <para>Before starting to build GCC, remember to unset any environment
-    variables that override the default optimization flags.</para>
+    <para>Avant de commencer la construction de GCC, rappelez-vous de désinitialiser
+    toute variable d'environnement surchargeant les options d'optimisation par
+    défaut.</para>
 
-    <para>Now prepare GCC for compilation:</para>
+    <para>Maintenant, préparez la compilation de GCC&nbsp;:</para>
 
 <screen><userinput remap="configure">../gcc-&gcc-version;/configure --prefix=/tools \
     --with-local-prefix=/tools --enable-clocale=gnu \
@@ -141,92 +153,97 @@
     --disable-libstdcxx-pch --disable-bootstrap</userinput></screen>
 
     <variablelist>
-      <title>The meaning of the new configure options:</title>
+      <title>Voici la signification des nouvelles options de configure&nbsp;:</title>
 
       <varlistentry>
         <term><parameter>--enable-clocale=gnu</parameter></term>
         <listitem>
-          <para>This option ensures the correct locale model is selected
-          for the C++ libraries under all circumstances. If the configure
-          script finds the <emphasis>de_DE</emphasis> locale installed,
-          it will select the correct gnu locale model. However, if the
-          <emphasis>de_DE</emphasis> locale is not installed, there is the
-          risk of building Application Binary Interface (ABI)-incompatible
-          C++ libraries because the incorrect generic locale model may be
-          selected.</para>
+          <para>Cette option nous assure que le bon modèle de locale est
+          sélectionné pour les bibliothèques C++ sous toutes les circonstances. Si le
+          script configure trouve la locale <emphasis>de_DE</emphasis> installée, il
+          sélectionnera le bon modèle de locale gnu. Néanmoins, si la locale 
+          <emphasis>de_DE</emphasis> n'est pas installée, il existe un risque de
+          construire des bibliothèques C++ incompatibles avec ABI (Application
+          Binary Interface) à cause du choix d'un
+          mauvais modèle générique de locale.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><parameter>--enable-threads=posix</parameter></term>
         <listitem>
-          <para>This enables C++ exception handling for multi-threaded code.</para>
+          <para>Ceci active la gestion des exceptions C++ pour le code
+          multi-threadé.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><parameter>--enable-__cxa_atexit</parameter></term>
         <listitem>
-          <para>This option allows use of <function>__cxa_atexit</function>,
-          rather than <function>atexit</function>, to register C++ destructors
-          for local statics and global objects. This option is essential for
-          fully standards-compliant handling of destructors. It also affects
-          the C++ ABI, and therefore results in C++ shared libraries and C++
-          programs that are interoperable with other Linux distributions.</para>
+          <para>Cette option autorise l'utilisation de
+          <function>__cxa_atexit</function>, plutôt que
+          <function>atexit</function>, pour enregistrer les destructeurs C++ des objets statiques locaux et globaux.
+          Cette option est essentielle pour la gestion des destructeurs en compatibilité
+          complète avec les standards. Il affecte aussi l'ABI C++ et donc résulte en des
+          bibliothèques partagées et des programmes C++ interopérables avec les autres
+          distributions Linux.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><parameter>--enable-languages=c,c++</parameter></term>
         <listitem>
-          <para>This option ensures that both the C and C++ compilers are
-          built.</para>
+          <para>Cette option garantie que les compilateurs
+          C et C++ seront construits.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><parameter>--disable-libstdcxx-pch</parameter></term>
         <listitem>
-          <para>Do not build the pre-compiled header (PCH) for
-          <filename class="libraryfile">libstdc++</filename>. It takes up a
-          lot of space, and we have no use for it.</para>
+          <para>Ce commutateur empêche la construction de l'en-tête précompilé
+          (PCH) de
+          <filename class="libraryfile">libstdc++</filename>. Il prend beaucoup
+          d'espace et nous n'en avons aucune utilité.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><parameter>--disable-bootstrap</parameter></term>
         <listitem>
-          <para>Bootstrapping the compiler is now the default for GCC. However,
-	  our build method should provide us with a solid compiler without the
-	  need to bootstrap each time.</para>
+          <para>Le bootstrapping du compilateur est le comportement par
+          défaut dans GCC. Cependant, notre méthode de compilation devrait
+          nous fournir un compilateur solide sans besoin de bootstrap chaque
+          fois.</para>
         </listitem>
       </varlistentry>
-
     </variablelist>
 
-    <para>Compile the package:</para>
+    <para>Compilez le paquet&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>There is no need to use the <parameter>bootstrap</parameter> target
-    now because the compiler being used to compile this GCC was built from
-    the exact same version of the GCC sources used earlier.</para>
-
-    <para>Compilation is now complete. As previously mentioned, running the test
-    suites for the temporary tools compiled in this chapter is not mandatory.
-    To run the GCC test suite anyway, use the following command:</para>
+    <para>Il n'est pas nécessaire d'utiliser la cible 
+    <parameter>bootstrap</parameter> maintenant car le compilateur utilisé pour
+    compiler ce GCC a été construit avec
+    exactement la même version des sources de GCC utilisées précédemment.</para>
+
+    <para>La compilation est maintenant terminée. Comme mentionné plus tôt,
+    lancer les suites de test pour les outils temporaires de ce chapitre n'est pas
+    nécessaire. Néanmoins, pour exécuter la suite de tests de GCC, lancez la
+    commande suivante&nbsp;:</para>
 
 <screen><userinput remap="test">make -k check</userinput></screen>
 
-    <para>The <parameter>-k</parameter> flag is used to make the test suite run
-    through to completion and not stop at the first failure. The GCC test
-    suite is very comprehensive and is almost guaranteed to generate a few
-    failures.</para>
+    <para>L'option <parameter>-k</parameter> est utilisée pour faire en
+    sorte que toute la suite de tests est exécutée et qu'elle ne s'arrête
+    pas au premier échec. La suite de tests GCC est très complète et il est
+    pratiquement garanti que certaines erreurs apparaîtront.</para>
 
-    <para>For a discussion of test failures that are of particular
-    importance, please see <xref linkend="ch-system-gcc" role="."/></para>
+    <para>Pour des précisions sur l'échec de tests qui revêtent une importance 
+    particulière, merci de lire <xref linkend="ch-system-gcc" role="."/></para>
 
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
@@ -239,7 +256,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails sur ce paquet sont situés dans
     <xref linkend="contents-gcc" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/gettext.xml BOOKfr/chapter05/gettext.xml
--- BOOK/chapter05/gettext.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/gettext.xml	2008-06-24 07:39:37.000000000 +0100
@@ -18,7 +18,7 @@
 
   <indexterm zone="ch-tools-gettext">
     <primary sortas="a-Gettext">Gettext</primary>
-    <secondary>tools</secondary>
+    <secondary>outils</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,40 +41,40 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Gettext</title>
+    <title>Installation de Gettext</title>
 
-    <para>For our temporary set of tools, we only need to build and install
-    one binary from Gettext.</para>
+    <para>Pour notre paramétrage temporaire des outils, nous n'avons besoin de
+    compiler et d'installer qu'un binaire de Gettext.</para>
 
-    <para>Prepare Gettext for compilation:</para>
+    <para>Préparez la compilation de Gettext&nbsp;:</para>
 
 <screen><userinput remap="configure">cd gettext-tools
 ./configure --prefix=/tools --disable-shared</userinput></screen>
 
     <variablelist>
-      <title>The meaning of the configure option:</title>
+      <title>Voici la signification des options de configure&nbsp;:</title>
 
       <varlistentry>
         <term><parameter>--disable-shared</parameter></term>
         <listitem>
-          <para>We do not need to install any of the shared Gettext libraries at
-          this time, therefore there is no need to build them.</para>
+          <para>Nous n'avons besoin d'installer aucune bibliothèque partagée de
+          Gettext pour le moment, donc ce n'est pas nécessaire de les compiler.</para>
         </listitem>
       </varlistentry>
 
     </variablelist>
 
-    <para>Compile the package:</para>
+    <para>Compilez le paquet&nbsp;:<para>
 
 <screen><userinput remap="make">make -C gnulib-lib
 make -C src msgfmt</userinput></screen>
 
-    <para>As only one binary has been compiled, it is not possible to run the
-    testsuite without compiling additional support libraries from the Gettext
-    package. It is therefore not recommended to attempt to run the testsuite at
-    this stage.</para>
+    <para>Comme seul un binaire a été compilé, ce n'est pas possibbe 
+    d'exécuter la suite de tests sans compiler des bibliothèques de support
+    complémentaires du paquet Gettext. Il n'est donc pas recommandé d'essayer
+    d'exécuter la suite de tests à cette étape.</para>
 
-    <para>Install the <command>msgfmt</command> binary:</para>
+    <para>Installez le binaire <command>msgfmt</command>&nbsp;:</para>
 
 <screen><userinput remap="install">cp -v src/msgfmt /tools/bin</userinput></screen>
 
@@ -83,7 +83,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails sur ce paquet sont situés dans
     <xref linkend="contents-gettext" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/glibc.xml BOOKfr/chapter05/glibc.xml
--- BOOK/chapter05/glibc.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/glibc.xml	2008-06-23 22:57:30.000000000 +0100
@@ -18,7 +18,7 @@
 
   <indexterm zone="ch-tools-glibc">
     <primary sortas="a-Glibc">Glibc</primary>
-    <secondary>tools</secondary>
+    <secondary>outils</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,27 +41,29 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Glibc</title>
+    <title>Installation de Glibc</title>
 
-    <para>The Glibc documentation recommends building Glibc outside of the source
-    directory in a dedicated build directory:</para>
+    <para>La documentation de Glibc recommande de construire Glibc en dehors du
+    répertoire des sources, c'est-à-dire dans un répertoire dédié&nbsp;:</para>
 
 <screen><userinput remap="pre">mkdir -v ../glibc-build
 cd ../glibc-build</userinput></screen>
 
-    <para>Because Glibc no longer supports i386, its developers say to use the
-    compiler flag <parameter>-march=i486</parameter> when building it for x86
-    machines. There are several ways to accomplish that, but testing shows that
-    the flag is best placed inside the build variable <quote>CFLAGS</quote>.
-    Instead of overriding completely what Glibc's internal build system uses
-    for CFLAGS, append the new flag to the existing contents of CFLAGS by
-    making use of the special file <filename>configparms</filename>. The
-    -mtune=native flag is also necessary to reset a reasonable value for -mtune
-    that is changed when setting -march.</para>
-
+    <para>Glibc ne supportant plus i386, ses développeurs disent d'utiliser
+    le commutateur du compilateur <parameter>-march=i486</parameter> lorsqu'on
+    le compile pour des machines x86. On peut faire cela de plusieurs manières,
+    mais des tests montrent que la meilleure place pour le commutateur est à
+    l'intérieur de la variable du compilajeur <quote>CFLAGS</quote>. Au lieu de
+    remplacer entièrement ce que le système de compilation interne de
+    Glibc utilise pour CFLAGS, ajoutez le nouveau commutateur au contenu 
+    existant de CFLAGS en utilisant le fichier spécial
+    <filename>configparms</filename>. Le commutateur -mtune=native est également
+    requis pour réinitialiser une valeur raisonnable pour -mtune, laquelle est
+    modifiée lors du paramétrage de -march.</para>
+    
 <screen><userinput remap="configure">echo "CFLAGS += -march=i486 -mtune=native" &gt; configparms</userinput></screen>
 
-    <para>Next, prepare Glibc for compilation:</para>
+    <para>Ensuite, préparez la compilation de Glibc&nbsp;:</para>
 
 <screen><userinput remap="configure">../glibc-&glibc-version;/configure --prefix=/tools \
     --disable-profile --enable-add-ons \
@@ -70,72 +72,77 @@
     --without-selinux</userinput></screen>
 
     <variablelist>
-      <title>The meaning of the configure options:</title>
+      <title>Voici la signification des options de configure&nbsp;:</title>
 
       <varlistentry>
         <term><parameter>--disable-profile</parameter></term>
         <listitem>
-          <para>This builds the libraries without profiling information. Omit
-          this option if profiling on the temporary tools is necessary.</para>
+          <para>Ceci construit les bibliothèques sans les informations de
+          profilage. Enlevez cette option si le profilage sur les outils 
+          temporaires est nécessaire.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><parameter>--enable-add-ons</parameter></term>
         <listitem>
-          <para>This tells Glibc to use the NPTL add-on as its threading
-          library.</para>
+          <para>>Ceci indique à Glibc d'utiliser le composant NPTL comme
+          bibliothèque de threads.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><parameter>--enable-kernel=2.6.0</parameter></term>
         <listitem>
-          <para>This tells Glibc to compile the library with support
-          for 2.6.x Linux kernels.</para>
+          <para>Ceci indique à Glibc de compiler la bibliothèque avec le support
+          des noyaux 2.6.x.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><parameter>--with-binutils=/tools/bin</parameter></term>
         <listitem>
-          <para>While not required, this switch ensures that there are
-          no errors pertaining to which Binutils programs get used during the
-          Glibc build.</para>
+          <para>Bien que pas nécessaire, ce commutateur nous assure qu'il ne
+          reste aucune erreur provenant des programmes Binutils lors de la construction
+          de Glibc.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><parameter>--without-gd</parameter></term>
         <listitem>
-          <para>This prevents the build of the <command>memusagestat</command>
-          program, which insists on linking against the host's libraries
-          (libgd, libpng, libz, etc.).</para>
+          <para>Ce commutateur empêche la construction du programme
+          <command>memusagestat</command>, qui insiste pour être lié avec les
+          bibliothèques de l'hôte (libgd, libpng, libz et ainsi de suite)..</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><parameter>--with-headers=/tools/include</parameter></term>
         <listitem>
-          <para>This tells Glibc to compile itself against the headers recently
-          installed to the tools directory, so that it knows exactly what
-          features the kernel has and can optimize itself accordingly.</para>
+          <para>Ceci dit à Glibc de se compiler contre les en-têtes qui
+          viennent d'être installés dans le répertoire tools, afin qu'il sache
+          exactement quelles options a le noyau et qu'il puisse s'optimiser en
+          conséquence.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><parameter>--without-selinux</parameter></term>
         <listitem>
-          <para>When building from hosts that include SELinux functionality
-          (e.g., Fedora Core 3), Glibc will build with support for SELinux.
-          As the LFS tools environment does not contain support for SELinux, a
-          Glibc compiled with such support will fail to operate correctly.</para>
+          <para>Lors de la construction à partir d'hôtes qui incluent la
+          fonctionnalité SELinux (par exemple Fedora Core 3), Glibc construira 
+          le support pour SELinux. Comme l'environnement d'outils LFS ne 
+          contient pas de support
+          pour SELinux, une Glibc compilée avec ce support ne fonctionnera pas
+          correctement.</para>
         </listitem>
       </varlistentry>
 
     </variablelist>
 
-    <para>During this stage the following warning might appear:</para>
+    <para>Lors de cette étape, le message d'avertissement suivant peut
+    apparaître&nbsp;:</para>
 
     <blockquote>
 <screen><computeroutput>configure: WARNING:
@@ -145,66 +152,70 @@
 *** Check the INSTALL file for required versions.</computeroutput></screen>
     </blockquote>
 
-    <para>The missing or incompatible <command>msgfmt</command> program is
-    generally harmless, but it can sometimes cause issues when running the
-    test suite. This <command>msgfmt</command> program is part of the
-    Gettext package which the host distribution should provide. If
-    <command>msgfmt</command> is present but deemed incompatible, upgrade
-    the host system's Gettext package or continue without it and see if
-    the test suite runs without problems regardless.</para>
+    <para>Le programme <command>msgfmt</command>, manquant ou incompatible, ne
+    pose généralement pas de problème mais certaines personnes pensent qu'il 
+    peut poser problème lors de l'exécution de la suite de tests. Ce programme
+    <command>msgfmt</command> fait partie du paquet Gettext que la distribution hôte
+    devrait fournir. Si <command>msgfmt</command> est présent mais semble
+    incompatible, mettez à jour le paquet Gettext du système hôte ou continuez sans
+    et voyez si la suite de tests continue son exécution sans problèmes.</para>
 
-    <para>Compile the package:</para>
+    <para>Compilez le paquet&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>Compilation is now complete. As mentioned earlier, running the
-    test suites for the temporary tools installed in this chapter is not
-    mandatory. To run the Glibc test suite (if desired), the following
-    command will do so:</para>
+    <para>La compilation est maintenant terminée. Comme dit plus tôt, lancer les
+    suites de tests pour les outils temporaires de ce chapitre n'est pas nécessaire.
+    Pour exécuter la suite de tests Glibc, si désiré, lancez la commande
+    suivante&nbsp;:</para>
 
 <screen><userinput remap="test">make check</userinput></screen>
 
-    <para>For a discussion of test failures that are of particular
-    importance, please see <xref linkend="ch-system-glibc" role="."/></para>
+    <para>Pour une discussion sur les échecs de tests qui ont une importance
+    particulière, merci de voir <xref linkend="ch-system-glibc" role="."/></para>
 
-    <para>In this chapter, some tests can be adversely affected by
-    existing tools or environmental issues on the host system. Glibc test
-    suite failures in this chapter are typically not worrisome. The Glibc
-    installed in <xref linkend="chapter-building-system"/> is the one that
-    will ultimately end up being used, so that is the one that needs to pass
-    most tests (even in <xref linkend="chapter-building-system"/>, some
-    failures could still occur, for example, with the math tests).</para>
-
-    <para>When experiencing a failure, make a note of it, then continue by
-    reissuing the <command>make check</command> command. The test suite
-    should pick up where it left off and continue. This stop-start sequence
-    can be circumvented by issuing a <command>make -k check</command> command.
-    If using this option, be sure to log the output so that the log file can
-    be examined for failures later.</para>
-
-    <para>The install stage of Glibc will issue a harmless warning at the
-    end about the absence of <filename>/tools/etc/ld.so.conf</filename>.
-    Prevent this warning with:</para>
+    <para>Dans ce chapitre, certains tests peuvent être perturbés par des outils
+    existants ou par des problèmes d'environnement sur le système hôte. Les échecs
+    de la suite de tests de Glibc dans ce chapitre ne portent typiquement pas à
+    conséquence. La bibliothèque Glibc installée dans
+    <xref linkend="chapter-building-system"/> est celle qui sera utilisée à 
+    la fin, donc c'est celle qui aura besoin de passer la plupart des tests (y 
+    compris dans <xref linkend="chapter-building-system"/>, certains échecs pourraient survenir, par
+    exemple celui des mathématiques)..</para>
+
+    <para>Si vous rencontrez un échec, prenez-en note puis continuez en
+    ré-exécutant la commande <command>make check</command>. La suite de tests devrait
+    reprendre là où elle a quitté précédemment. Cette séquence d'arrêt/relancement
+    est annulée en lançant la commande <command>make -k check</command>.
+    En utilisant cette option, assurez-vous de tracer la sortie pour que le 
+    journal des traces puisse être examiné plus tard pour les différents échecs.</para>
+
+    <para>L'étape d'installation de Glibc affichera un message d'avertissement sans
+    conséquence pour l'absence de 
+    <filename>/tools/etc/ld.so.conf</filename>.
+    Supprimez ce message avec&nbsp;:</para>
 
 <screen><userinput remap="install">mkdir -v /tools/etc
 touch /tools/etc/ld.so.conf</userinput></screen>
 
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
-    <para>Different countries and cultures have varying conventions for
-    how to communicate. These conventions range from the format for
-    representing dates and times to more complex issues, such as the
-    language spoken. The <quote>internationalization</quote> of GNU
-    programs works by locale.</para>
+    <para>Différents pays et cultures ont des conventions variables sur la 
+    façon de communiquer. Ces conventions vont du très simple, telle que la 
+    représentation de la date et de l'heure à du très compliqué, telle que le 
+    langage parlé. 
+    L'<quote>internationalisation</quote> des programmes GNU fonctionne en 
+    utilisant les locales.</para>
 
     <note>
-      <para>If the test suites are not being run in this chapter (as per
-      the recommendation), there is no need to install the locales now.
-      The appropriate locales will be installed in the next chapter.
-      To install the Glibc locales anyway, use instructions from
-      <xref linkend="ch-system-glibc" role="."/></para>
+      <para>Si les suites de tests ne seront pas exécutés dans ce chapitre
+      (suivant ainsi notre recommandation), il y a peu d'intérêts à installer les
+      locales maintenant. Les bonnes locales seront installées dans le chapitre
+      suivant.
+      Néanmoins, pour installer les locales Glibc, utilisez les instructions de
+      la section <xref linkend="ch-system-glibc" role="."/></para>
     </note>
 
   </sect2>
@@ -212,7 +223,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails sur ce paquet sont situés dans
     <xref linkend="contents-glibc" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/grep.xml BOOKfr/chapter05/grep.xml
--- BOOK/chapter05/grep.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/grep.xml	2008-06-24 07:41:22.000000000 +0100
@@ -18,7 +18,7 @@
 
   <indexterm zone="ch-tools-grep">
     <primary sortas="a-Grep">Grep</primary>
-    <secondary>tools</secondary>
+    <secondary>outils</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,37 +41,37 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Grep</title>
+    <title>Installation de Grep</title>
 
-    <para>Prepare Grep for compilation:</para>
+    <para>Préparez la compilation de Grep&nbsp;:</para>
 
 <screen><userinput remap="configure">./configure --prefix=/tools \
     --disable-perl-regexp</userinput></screen>
 
     <variablelist>
-      <title>The meaning of the configure option:</title>
+      <title>Voici la signification des options de configure&nbsp;:</title>
 
       <varlistentry>
         <term><parameter>--disable-perl-regexp</parameter></term>
         <listitem>
-          <para>This ensures that the <command>grep</command> program does
-          not get linked against a Perl Compatible Regular Expression (PCRE)
-          library that may be present on the host but will not be available
-          once we enter the <command>chroot</command> environment.</para>
+          <para>Ceci nous assure que le programme <command>grep</command>
+          ne sera pas lié à une bibliothèque PCRE (Perl Compatible Regular 
+          Expression) qui pourrait être présente sur l'hôte et qui ne serait
+          pas disponible une fois que nous serons entrés dans l'environnement
+          <command>chroot</command>.</para>
         </listitem>
       </varlistentry>
 
     </variablelist>
 
-    <para>Compile the package:</para>
+    <para>Compilez les programmes&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>To test the results, issue:</para>
+    <para>Pour tester les résultats, lancez&nbsp;:
+    <userinput>make check</userinput>.</para>
 
-<screen><userinput remap="test">make check</userinput></screen>
-
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
@@ -80,7 +80,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails sur ce paquet sont disponibles dans
     <xref linkend="contents-grep" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/gzip.xml BOOKfr/chapter05/gzip.xml
--- BOOK/chapter05/gzip.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/gzip.xml	2008-06-24 08:34:32.000000000 +0100
@@ -9,16 +9,16 @@
   <?dbhtml filename="gzip.html"?>
 
   <sect1info condition="script">
-    <productname>gzip</productname>
-    <productnumber>&gzip-version;</productnumber>
-    <address>&gzip-url;</address>
+    <productname>grep</productname>
+    <productnumber>&grep-version;</productnumber>
+    <address>&grep-url;</address>
   </sect1info>
 
   <title>Gzip-&gzip-version;</title>
 
   <indexterm zone="ch-tools-gzip">
     <primary sortas="a-Gzip">Gzip</primary>
-    <secondary>tools</secondary>
+    <secondary>outils</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,30 +41,22 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Gzip</title>
+    <title>Installation de Gzip</title>
 
-    <para>The version of the function <quote>futimens</quote> used
-    by Gzip is incompatible with the version that current
-    Glibc provides, so we'll rename the function:</para>
+    <para>Préparez la compilation de Gzip&nbsp;:</para>
 
-<screen><userinput remap="pre">for file in gzip.c lib/utimens.{c,h} ; do \
-   cp -v $file{,.orig}
-   sed 's/futimens/gl_&amp;/' $file.orig &gt; $file
-done</userinput></screen>
+<screen><userinput remap="configure">./configure --prefix=/tools \
+     --disable-perl-regexp</userinput></screen>
 
-    <para>Prepare Gzip for compilation:</para>
-
-<screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
-
-    <para>Compile the package:</para>
+    <para>Compilez le paquet&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>To test the results, issue:</para>
+    <para>Pour tester le résultat, lancez&nbsp;:</para>
 
 <screen><userinput remap="test">make check</userinput></screen>
 
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
@@ -73,7 +65,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails sur ce paquet sont situés dans
     <xref linkend="contents-gzip" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/introduction.xml BOOKfr/chapter05/introduction.xml
--- BOOK/chapter05/introduction.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/introduction.xml	2008-06-23 21:56:31.000000000 +0100
@@ -10,58 +10,73 @@
 
   <title>Introduction</title>
 
-  <para>This chapter shows how to compile and install a minimal Linux system.
-  This system will contain just enough tools to start constructing the final
-  LFS system in <xref linkend="chapter-building-system"/> and allow a working
-  environment with more user convenience than a minimum environment would.</para>
-
-  <para>There are two steps in building this minimal system. The first step
-  is to build a new and host-independent toolchain (compiler, assembler,
-  linker, libraries, and a few useful utilities).  The second step uses this
-  toolchain to build the other essential tools.</para>
-
-  <para>The files compiled in this chapter will be installed under the
-  <filename class="directory">$LFS/tools</filename> directory to keep them
-  separate from the files installed in the next chapter and the host
-  production directories. Since the packages compiled here are temporary,
-  we do not want them to pollute the soon-to-be LFS system.</para>
+  <para>Ce chapitre montre comment compiler et installer un système
+  Linux minimal.
+
+  Ce système ne contiendra que les outils nécessaires pour commencer la
+  construction du système LFS final dans
+
+  <xref linkend="chapter-building-system"/> et de créer un environnement
+  de travail avec plus de facilité pour l'utilisateur que ne le
+  permettrait un environnement minimum.</para>
+
+  <para>Il y a deux étapes dans la construction de ce système minimal.
+  La première étape consiste à construire un ensemble d'outils tous
+  nouveaux et indépendant de l'hôte (compilateur, assembleur, éditeur de
+  liens, bibliothèques et quelques outils). La deuxième étape utilise
+  cet ensemble d'outils pour construire tous les autres outils
+  essentiels.</para>
+
+  <para>Les fichiers compilés dans ce chapitre vont être installés sous
+  le répertoire <filename class="directory">$LFS/tools</filename> de
+  façon à les garder séparés des fichiers installés dans le chapitre
+  suivant et des répertoires de production de votre hôte. Comme tous les
+  paquets compilés ici sont simplement temporaires, nous ne voulons pas
+  polluer le futur système LFS.</para>
 
   <important>
-    <para>Before issuing the build instructions for a package, the package
-    should be unpacked as user <systemitem class="username">lfs</systemitem>,
-    and a <command>cd</command> into the created directory should be performed.
-    The build instructions assume that the <command>bash</command> shell is
-    in use.</para>
+    <para>Avant de lancer les instructions de construction pour un
+    paquet, le paquet doit être déballé en tant qu'utilisateur
+    <systemitem class="username">lfs</systemitem>, et vous devez utiliser la
+    commande <command>cd</command> pour entrer dans le répertoire tout juste créé. Les instructions
+    de construction supposent que le shell <command>bash</command> est utilisé.</para>
   </important>
 
-  <para>Several of the packages are patched before compilation, but only when
-  the patch is needed to circumvent a problem. A patch is often needed in both
-  this and the next chapter, but sometimes in only one or the other. Therefore,
-  do not be concerned if instructions for a downloaded patch seem to be missing.
-  Warning messages about <emphasis>offset</emphasis> or <emphasis>fuzz</emphasis>
-  may also be encountered when applying a patch. Do not worry about these
-  warnings, as the patch was still successfully applied.</para>
-
-  <para>During the compilation of most packages, there will be several warnings
-  that scroll by on the screen. These are normal and can safely be ignored.
-  These warnings are as they appear&mdash;warnings about deprecated, but not
-  invalid, use of the C or C++ syntax. C standards change fairly often, and
-  some packages still use the older standard. This is not a problem, but does
-  prompt the warning.</para>
+  <para>Plusieurs paquets sont corrigés avant d'être compilés, mais
+  seulement dans le cas où la correction est nécessaire pour résoudre un
+  problème. Souvent, le correctif est nécessaire à la fois dans ce
+  chapitre et dans le suivant, mais quelque fois dans seulement un des
+  deux. Donc, ne vous inquiétez pas lorsque des instructions pour un
+  correctif téléchargé semblent manquer. Des messages d'avertissements
+  sur un décalage (<emphasis>offset</emphasis>) ou sur autre chose
+  (<emphasis>fuzz</emphasis>) peuvent apparaître lors de
+
+  l'application d'un correctif. Ne vous inquiétez pas pour ces messages,
+  le correctif a bien été appliqué.</para>
+
+  <para>Pendant la compilation de la plupart des paquets, plusieurs
+  messages d'avertissement du compilateur défileront sur votre écran.
+  Ceci est normal et peut être ignoré sans danger. Ces messages
+  d'avertissement ne sont que des avertissements&mdash; sur une
+  utilisation obsolète, mais pas invalide, de la syntaxe de C ou de C++.
+  Les standards C changent assez souvent et quelques paquets continuent
+  à utiliser les anciens standards. Ce n'est pas un véritable problème
+  mais cela provoque les messages.</para>
 
   <important>
-    <para>After installing each package, delete its source and build directories,
-    unless specifically instructed otherwise. Deleting the sources prevents
-    mis-configuration when the same package is reinstalled later.</para>
+    <para>Après l'installation de chaque paquet, supprimez son répertoire
+    source et son répertoire de construction, sauf si nous vous le demandons
+    spécifiquement. Supprimer les sources empêche une mauvaise
+    configuration lorsque le même paquet est réinstallé un peu plus tard.</para>
   </important>
 
-  <para>Check one last time that the <envar>LFS</envar> environment
-  variable is set up properly:</para>
+  <para>Vérifiez une dernière fois que la variable d'environnement
+  <envar>LFS</envar> est configurée correctement&nbsp;:</para>
 
 <screen role="nodump"><userinput>echo $LFS</userinput></screen>
 
-  <para>Make sure the output shows the path to the LFS partition's mount
-  point, which is <filename class="directory">/mnt/lfs</filename>, using
-  our example.</para>
+  <para>Assurez-vous que le résultat contient le bon répertoire vers le
+  point de montage de la partition LFS, qui est <filename
+  class="directory">/mnt/lfs</filename>, suivant notre exemple.</para>
 
 </sect1>
diff -Naur BOOK/chapter05/kernel-headers.xml BOOKfr/chapter05/kernel-headers.xml
--- BOOK/chapter05/kernel-headers.xml	1970-01-01 01:00:00.000000000 +0100
+++ BOOKfr/chapter05/kernel-headers.xml	2007-06-06 15:27:04.000000000 +0100
@@ -0,0 +1,76 @@
+<?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-tools-kernel-headers" role="wrap">
+<title>En-têtes Linux-&linux-version;</title>
+<?dbhtml filename="kernel-headers.html"?>
+
+<indexterm zone="ch-tools-kernel-headers">
+<primary sortas="a-Linux">Linux</primary>
+<secondary>outils, en-tête</secondary></indexterm>
+
+<sect2 role="package"><title/>
+<para>Le paquet du noyau Linux contient les sources ainsi que les fichiers
+d'en-têtes utilisés par Glibc.</para>
+
+<segmentedlist>
+<segtitle>&buildtime;</segtitle>
+<segtitle>&diskspace;</segtitle>
+<seglistitem><seg>0,1&nbsp;SBU</seg><seg>186&nbsp;Mo</seg></seglistitem>
+</segmentedlist>
+
+<segmentedlist>
+<segtitle>L'installation des en-têtes Linux dépend de</segtitle>
+<seglistitem><seg>Coreutils et Make</seg></seglistitem>
+</segmentedlist>
+
+</sect2>
+
+<sect2 role="installation">
+<title>Installation des en-têtes du noyau</title>
+
+<para>Comme certains paquets se réfèrent aux fichiers d'en-têtes du
+noyau, c'est le moment de déballer l'archive du noyau, puis de 
+configurer et copier les fichiers requis à un endroit où <command>gcc</command>
+pourra les trouver plus tard.</para>
+
+<para>Préparez l'installation des en-têtes avec&nbsp;:</para>
+
+<screen><userinput>make mrproper</userinput></screen>
+
+<para>Ceci nous assure que le répertoire du noyau est totalement propre.
+Il est recommandé d'exécuter cette commande à <emphasis>chaque</emphasis>
+compilation du noyau. Ne supposez pas que le contenu du répertoire soit propre après
+le déballage.</para>
+
+<para>Créez le fichier <filename class="headerfile">include/linux/version.h</filename>&nbsp;:</para>
+
+<screen><userinput>make include/linux/version.h</userinput></screen>
+
+<beginpage/>
+
+<para>Créez le lien symbolique spécifique à la plateforme
+<filename class="symlink">include/asm</filename>&nbsp;:</para>
+
+<screen><userinput>make include/asm</userinput></screen>
+
+<para>Installez les fichiers d'en-têtes spécifiques à la platforme&nbsp;:</para>
+
+<screen><userinput>mkdir /tools/glibc-kernheaders
+cp -HR include/asm /tools/glibc-kernheaders
+cp -R include/asm-generic /tools/glibc-kernheaders</userinput></screen>
+
+<para>Enfin, installez les autres fichiers d'en-têtes du noyau&nbsp;:</para>
+
+<screen><userinput>cp -R include/linux /tools/glibc-kernheaders</userinput></screen>
+
+</sect2>
+
+<sect2 role="content"><title/>
+<para>Les détails sur ce paquet sont situés dans <xref
+linkend="contents-kernel" role="."/></para>
+</sect2>
+
+</sect1>
diff -Naur BOOK/chapter05/linux-headers.xml BOOKfr/chapter05/linux-headers.xml
--- BOOK/chapter05/linux-headers.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/linux-headers.xml	2008-06-23 22:40:55.000000000 +0100
@@ -8,17 +8,17 @@
 <sect1 id="ch-tools-linux-headers" role="wrap">
   <?dbhtml filename="linux-headers.html"?>
 
-  <sect1info condition="script">
-    <productname>linux</productname>
-    <productnumber>&linux-version;</productnumber>
-    <address>&linux-url;</address>
-  </sect1info>
+   <sect1info condition="script">
+     <productname>linux</productname>
+     <productnumber>&linux-version;</productnumber>
+     <address>&linux-url;</address>
+   </sect1info>
 
   <title>Linux-&linux-version; API Headers</title>
 
   <indexterm zone="ch-tools-linux-headers">
     <primary sortas="a-Linux">Linux</primary>
-    <secondary>tools, API headers</secondary>
+    <secondary>outils, en-têtes API</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,14 +41,14 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Linux API Headers</title>
+    <title>Installation de Linux API Headers</title>
 
-    <para>The Linux kernel needs to expose an Application Programming Interface
-    (API) for the system's C library (Glibc in LFS) to utilize.  This is done
-    by way of sanitizing various C header files that are shipped in the Linux
-    kernel source tarball.</para>
+    <para>Le noyau Linux a besoin d'exposer une interface de programmation de 
+    l'application (API) pour la bibliothèque C du système (Glibc dans LFS) à
+    utiliser. Cela est possible en nettoyant certains fichiers d'en-tête C qui 
+    sont laissés dans le paquetage des sources du noyau Linux.</para>
 
-    <para>Install the header files:</para>
+    <para>Installez les fichiers d'en-têtes&nbsp;:</para>
 
 <screen><userinput remap="install">make mrproper
 make headers_check
@@ -60,7 +60,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails sur ce paquet sont situés dans
     <xref linkend="contents-linux-headers" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/linux-libc-headers.xml BOOKfr/chapter05/linux-libc-headers.xml
--- BOOK/chapter05/linux-libc-headers.xml	1970-01-01 01:00:00.000000000 +0100
+++ BOOKfr/chapter05/linux-libc-headers.xml	2007-06-06 15:27:04.000000000 +0100
@@ -0,0 +1,59 @@
+<?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-tools-linux-libc-headers" role="wrap">
+<title>Linux-Libc-Headers-&linux-libc-headers-version;</title>
+<?dbhtml filename="linux-libc-headers.html"?>
+
+<indexterm zone="ch-tools-linux-libc-headers">
+<primary sortas="a-Linux-Libc-Headers">Linux-Libc-Headers</primary>
+<secondary>outils, en-têtes</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>0,1&nbsp;SBU</seg><seg>26,9&nbsp;Mo</seg></seglistitem>
+</segmentedlist>
+
+<xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
+	href="../chapter06/linux-libc-headers.xml"
+	xpointer="xpointer(/sect1/sect2[1]/segmentedlist[2])"/>
+
+
+</sect2>
+
+<sect2 role="installation">
+<title>Installation de Linux-Libc-Headers</title>
+
+<para>Pendant des années, la pratique était d'utiliser les en-têtes
+<quote>bruts</quote> du noyau (directement extraits de l'archive tar du noyau) dans
+<filename class="directory">/usr/include</filename> mais, ces dernières années, les
+développeurs du noyau ont pris fortement position contre cet état de fait. Ceci
+a donné naissance au projet Linux-Libc-Headers, conçu pour offrir
+une version stable de l'interface de programmation des applications (API) des
+en-têtes du noyau Linux.</para>
+
+<para>Installez les fichiers d'en-têtes&nbsp;:</para>
+
+<screen><userinput>cp -Rv include/asm-i386 /tools/include/asm
+cp -Rv include/linux /tools/include</userinput></screen>
+
+<para>Si votre architecture n'est pas i386 (compatible), modifiez la première
+commande comme nécessaire.</para>
+
+</sect2>
+
+<sect2 role="content"><title/>
+<para>Les détails sur ce paquet sont situés dans <xref
+linkend="contents-linux-libc-headers" role="."/></para>
+</sect2>
+
+</sect1>
+
diff -Naur BOOK/chapter05/m4.xml BOOKfr/chapter05/m4.xml
--- BOOK/chapter05/m4.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/m4.xml	2008-06-24 08:36:34.000000000 +0100
@@ -18,7 +18,7 @@
 
   <indexterm zone="ch-tools-m4">
     <primary sortas="a-M4">M4</primary>
-    <secondary>tools</secondary>
+    <secondary>outils</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,21 +41,21 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of M4</title>
+    <title>Installation de M4</title>
 
-    <para>Prepare M4 for compilation:</para>
+    <para>Préparez la compilation de M4&nbsp;:</para>
 
 <screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
 
-    <para>Compile the package:</para>
+    <para>Compilez le paquet&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>To test the results, issue:</para>
+    <para>Pour tester les résultats, lancez&nbsp;:</para>
 
 <screen><userinput remap="test">make check</userinput></screen>
 
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
@@ -64,7 +64,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails de ce paquet sont situés dans
     <xref linkend="contents-m4" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/make.xml BOOKfr/chapter05/make.xml
--- BOOK/chapter05/make.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/make.xml	2008-06-24 08:43:58.000000000 +0100
@@ -17,7 +17,7 @@
 
   <indexterm zone="ch-tools-make">
     <primary sortas="a-Make">Make</primary>
-    <secondary>tools</secondary>
+    <secondary>outils</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -40,21 +40,21 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Make</title>
+    <title>Installation de Make</title>
 
-    <para>Prepare Make for compilation:</para>
+    <para>Préparez la compilation de Make&nbsp;:</para>
 
 <screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
 
-    <para>Compile the package:</para>
+    <para>Compilez le paquet&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>To test the results, issue:</para>
-
+    <para>Pour tester les résultats, lancez&nbsp;:</para>
+    
 <screen><userinput remap="test">make check</userinput></screen>
 
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
@@ -63,7 +63,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails de ce paquet sont situés dans
     <xref linkend="contents-make" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/ncurses.xml BOOKfr/chapter05/ncurses.xml
--- BOOK/chapter05/ncurses.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/ncurses.xml	2008-06-24 07:04:28.000000000 +0100
@@ -18,7 +18,7 @@
 
   <indexterm zone="ch-tools-ncurses">
     <primary sortas="a-Ncurses">Ncurses</primary>
-    <secondary>tools</secondary>
+    <secondary>outils</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,45 +41,45 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Ncurses</title>
+    <title>Installation de Ncurses</title>
 
-    <para>Prepare Ncurses for compilation:</para>
+    <para>Préparez la compilation de Ncurses&nbsp;:</para>
 
 <screen><userinput remap="configure">./configure --prefix=/tools --with-shared \
     --without-debug --without-ada --enable-overwrite</userinput></screen>
 
     <variablelist>
-      <title>The meaning of the configure options:</title>
+      <title>Voici la signification des options de configure&nbsp;:</title>
 
       <varlistentry>
         <term><parameter>--without-ada</parameter></term>
         <listitem>
-          <para>This ensures that Ncurses does not build support for the Ada
-          compiler which may be present on the host but will not be available
-          once we enter the <command>chroot</command> environment.</para>
+          <para>Ceci nous assure que Ncurses ne construira pas le support du
+          compilateur Ada qui pourrait être présent sur l'hôte mais qui ne sera pas
+          disponible lorsque nous entrerons dans l'environnement
+          <command>chroot</command>.</para>
         </listitem>
       </varlistentry>
 
       <varlistentry>
         <term><parameter>--enable-overwrite</parameter></term>
         <listitem>
-          <para>This tells Ncurses to install its header files into
-          <filename class="directory">/tools/include</filename>, instead of
-          <filename class="directory">/tools/include/ncurses</filename>, to
-          ensure that other packages can find the Ncurses headers
-          successfully.</para>
+          <para>Ceci indique à Ncurses d'installer les fichiers d'en-tête dans
+          <filename class="directory">/tools/include</filename>, au lieu de
+          <filename class="directory">/tools/include/ncurses</filename>, pour
+          s'assurer que les autres paquets trouveront bien les en-têtes de Ncurses.</para>
         </listitem>
       </varlistentry>
 
     </variablelist>
 
-    <para>Compile the package:</para>
+    <para>Compilez le paquet&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>This package does not come with a test suite.</para>
+    <para>Ce paquet ne fournit pas de suite de tests.</para>
 
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
@@ -88,7 +88,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails sur ce paquet sont disponibles dans
     <xref linkend="contents-ncurses" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/patch.xml BOOKfr/chapter05/patch.xml
--- BOOK/chapter05/patch.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/patch.xml	2008-06-24 08:46:44.000000000 +0100
@@ -18,7 +18,7 @@
 
   <indexterm zone="ch-tools-patch">
     <primary sortas="a-Patch">Patch</primary>
-    <secondary>tools</secondary>
+    <secondary>outils</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,19 +41,19 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Patch</title>
+    <title>Installation de Patch</title>
 
-    <para>Prepare Patch for compilation:</para>
+    <para>Préparez la compilation de Patch&nbsp;:</para>
 
 <screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
 
-    <para>Compile the package:</para>
+    <para>Compilez le paquet&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>This package does not come with a test suite.</para>
+    <para>Ce paquet ne fournit pas de suite de tests.</para>
 
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
@@ -62,7 +62,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails sur ce paquet sont situés dans
     <xref linkend="contents-patch" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/perl.xml BOOKfr/chapter05/perl.xml
--- BOOK/chapter05/perl.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/perl.xml	2008-06-24 08:54:16.000000000 +0100
@@ -18,7 +18,7 @@
 
   <indexterm zone="ch-tools-perl">
     <primary sortas="a-Perl">Perl</primary>
-    <secondary>tools</secondary>
+    <secondary>outils</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,50 +41,51 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Perl</title>
+    <title>Installation de Perl</title>
 
-    <para>First adapt some hard-wired paths to the C library by applying
-    the following patch:</para>
+    <para>Tout d'abord, adaptez quelques chemins codés en dur vers la
+    bibliothèque C en appliquant le correctif suivant&nbsp;:</para>
 
 <screen><userinput remap="pre">patch -Np1 -i ../&perl-libc-patch;</userinput></screen>
 
-    <para>Fix an incompatibility with gcc-&gcc-version;:</para>
-
+    <para>Corrigez une ´incompatibilité avec gcc-&gcc-version;:</para>
+    
 <screen><userinput remap="pre">mv -v makedepend.SH{,.orig}
-sed 's/command /command[ -]/' makedepend.SH.orig &gt; makedepend.SH</userinput></screen>
+sed 's/command /command[ -]/' makedepend.SH.orig &gt; makedepend.SH</userinput>/screen>
 
-    <para>Prepare Perl for compilation (make sure to get the
-    'Data/Dumper Fcntl IO POSIX' part of the command correct&mdash;they are all
-    letters):</para>
+    <para>Préparez la compilation de Perl (assurez-vous que la partie de la
+    commande 'Data/Dumper Fcntl IO POSIX' est saisie correctement&mdash;ce
+    ne sont que des lettres)&nbsp;:</para>
 
-<screen><userinput remap="configure">./configure.gnu --prefix=/tools -Dstatic_ext='Data/Dumper Fcntl IO POSIX'</userinput></screen>
+<screen><userinputremap="configure">./configure.gnu --prefix=/tools -Dstatic_ext='Data/Dumper Fcntl IO POSIX'</userinput></screen>
 
     <variablelist>
-      <title>The meaning of the configure options:</title>
+      <title>Voici la signification de l'option de configure&nbsp;:</title>
 
       <varlistentry>
         <term><parameter>-Dstatic_ext='Data/Dumper Fcntl IO POSIX'</parameter></term>
         <listitem>
-          <para>This tells Perl to build the minimum set of static extensions
-          needed for installing and testing the Coreutils and Glibc packages in the
-          next chapter.</para>
+          <para>Ceci indique à Perl de construire l'ensemble minimal d'extensions statiques
+          nécessaires à l'installation et au test du paquet Coreutils dans le 
+          prochain chapitre.</para>
         </listitem>
       </varlistentry>
 
     </variablelist>
 
-    <para>Only a few of the utilities contained in this package, and one of its
-    libraries need to be built:</para>
+    <para>Seulement une partie des outils de ce paquetage et une de ses
+    bibliothèques doivent être construit&nbsp;:</para>
 
 <screen><userinput remap="make">make perl utilities ext/Errno/pm_to_blib</userinput></screen>
 
-    <para>Although Perl comes with a test suite, it is not recommended to
-    run it at this point. Only part of Perl was built and running
-    <command>make test</command> now will cause the rest of Perl to be
-    built as well, which is unnecessary at this point. The test suite can
-    be run in the next chapter if desired.</para>
+    <para>Bien que Perl est fourni avec une suite de tests, il n'est pas recommandé
+    de l'exécuter maintenant. Seules des parties de Perl ont été construites et
+    l'exécution de
+    <command>make test</command> obligerait la construction du
+    reste de Perl, ce qui n'est pas nécessaire actuellement. La suite de tests peut
+    être exécutée dans le chapitre suivant si désiré.</para>
 
-    <para>Install these tools and their libraries:</para>
+    <para>Puis, installez ces outils et leurs bibliothèques&nbsp;:</para>
 
 <screen><userinput remap="install">cp -v perl pod/pod2man /tools/bin
 mkdir -pv /tools/lib/perl5/&perl-version;
@@ -95,7 +96,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails sur ce paquet sont disponibles dans
     <xref linkend="contents-perl" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/sed.xml BOOKfr/chapter05/sed.xml
--- BOOK/chapter05/sed.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/sed.xml	2008-06-24 08:57:32.000000000 +0100
@@ -18,7 +18,7 @@
 
   <indexterm zone="ch-tools-sed">
     <primary sortas="a-Sed">Sed</primary>
-    <secondary>tools</secondary>
+    <secondary>outils</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,21 +41,21 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Sed</title>
+    <title>Installation de Sed</title>
 
-    <para>Prepare Sed for compilation:</para>
+    <para>Préparez la compilation de Sed&nbsp;:</para>
 
 <screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
 
-    <para>Compile the package:</para>
+    <para>Compilez le paquet&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>To test the results, issue:</para>
+    <para>Pour tester les résultats, lancez&nbsp;:</para>
 
 <screen><userinput remap="test">make check</userinput></screen>
 
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
@@ -64,7 +64,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails de ce paquet sont situés dans
     <xref linkend="contents-sed" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/stripping.xml BOOKfr/chapter05/stripping.xml
--- BOOK/chapter05/stripping.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/stripping.xml	2008-06-24 09:10:45.000000000 +0100
@@ -8,32 +8,35 @@
 <sect1 id="ch-tools-stripping">
   <?dbhtml filename="stripping.html"?>
 
-  <title>Stripping</title>
+  <title>Supprimer les symboles des fichiers objets</title>
 
-  <para>The steps in this section are optional, but if the LFS partition is
-  rather small, it is beneficial to learn that unnecessary items can be removed.
-  The executables and libraries built so far contain about 70 MB of unneeded
-  debugging symbols. Remove those symbols with:</para>
+  <para>Les étapes de cette section sont optionnelles mais si la partition LFS
+  est plutôt petite, il est intéressant d'apprendre que des éléments inutiles
+  sont
+  supprimables. Les exécutables et les bibliothèques que vous avez construit
+  jusqu'à maintenant contiennent jusqu'à 130&nbsp;Mo de symboles de débogages
+  inutiles. Supprimez ces symboles avec&nbsp;:</para>
 
 <screen><userinput>strip --strip-debug /tools/lib/*
 strip --strip-unneeded /tools/{,s}bin/*</userinput></screen>
 
-  <para>The last of the above commands will skip some twenty files,
-  reporting that it does not recognize their file format. Most of these
-  are scripts instead of binaries.</para>
-
-  <para>Take care <emphasis>not</emphasis> to use
-  <parameter>--strip-unneeded</parameter> on the libraries. The static
-  ones would be destroyed and the toolchain packages would need to be
-  built all over again.</para>
+  <para>La dernière des commandes ci-dessus laissera de côté une vingtaine de
+  fichiers en indiquant qu'elle ne reconnaît pas leur format. La
+  plupart sont des scripts et non pas des binaires.</para>
+
+  <para>Faites attention à ne <emphasis>pas</emphasis> utiliser
+  <parameter>--strip-unneeded</parameter>  sur les bibliothèques. Cela
+  détruirait les versions statiques et les paquets devraient être de nouveau
+  construits.</para>
 
-  <para>To save nearly 20 MB more, remove the documentation:</para>
+  <para>Pour sauver encore 30&nbsp;Mo, supprimez toute la
+  documentation&nbsp;:</para>
 
 <screen><userinput>rm -rf /tools/{info,man}</userinput></screen>
 
-  <para>At this point, you should have at least 850 MB of free space in
-  <envar>$LFS</envar> that can be used to build and install Glibc in the
-  next phase. If you can build and install Glibc, you can build and install
-  the rest too.</para>
+  <para>Il y aura maintenant au moins 850&nbsp;Mo d'espace disque libre sur le
+  système de fichiers <envar>$LFS</envar> à utiliser pour construire et installer Glibc dans la
+  prochaine phase. Si vous pouvez construire et installer Glibc, vous pourrez
+  aussi construire et installer le reste.</para>
 
 </sect1>
diff -Naur BOOK/chapter05/tar.xml BOOKfr/chapter05/tar.xml
--- BOOK/chapter05/tar.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/tar.xml	2008-06-24 09:00:19.000000000 +0100
@@ -18,7 +18,7 @@
 
   <indexterm zone="ch-tools-tar">
     <primary sortas="a-Tar">Tar</primary>
-    <secondary>tools</secondary>
+    <secondary>outils</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,21 +41,21 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Tar</title>
+    <title>Installation de Tar</title>
 
-    <para>Prepare Tar for compilation:</para>
+    <para>Préparez la compilation de Tar&nbsp;:</para>
 
-<screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
+<screen><userinput rema´p="configure">./configure --prefix=/tools</userinput></screen>
 
-    <para>Compile the package:</para>
+    <para>Compilez le paquet&nbsp;:</para>
 
-<screen><userinput remap="make">make</userinput></screen>
-
-    <para>To test the results, issue:</para>
+<screen><userinput rema?p="make">make</userinput></screen>
 
+    <para>Pour tester les résultats, lancez&nbsp;:</para>
+    
 <screen><userinput remap="test">make check</userinput></screen>
 
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
@@ -64,7 +64,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails sur ce paquet sont situés dans
     <xref linkend="contents-tar" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/tcl.xml BOOKfr/chapter05/tcl.xml
--- BOOK/chapter05/tcl.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/tcl.xml	2008-06-23 23:12:12.000000000 +0100
@@ -8,11 +8,11 @@
 <sect1 id="ch-tools-tcl" role="wrap">
   <?dbhtml filename="tcl.html"?>
 
-  <sect1info condition="script">
-    <productname>tcl</productname>
-    <productnumber>&tcl-version;</productnumber>
-    <address>&tcl-url;</address>
-  </sect1info>
+   <sect1info condition="script">
+     <productname>tcl</productname>
+     <productnumber>&tcl-version;</productnumber>
+     <address>&tcl-url;</address>
+   </sect1info>
 
   <title>Tcl-&tcl-version;</title>
 
@@ -23,7 +23,7 @@
   <sect2 role="package">
     <title/>
 
-    <para>The Tcl package contains the Tool Command Language.</para>
+       <para>Le paquet Tcl contient le langage de commandes des outils.</para>
 
     <segmentedlist>
       <segtitle>&buildtime;</segtitle>
@@ -38,75 +38,80 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Tcl</title>
+    <title>Installation de Tcl</title>
 
-    <para>This package and the next two (Expect and DejaGNU) are installed
-    to support running the test suites for GCC and Binutils. Installing
-    three packages for testing purposes may seem excessive, but it is very
-    reassuring, if not essential, to know that the most important tools are
-    working properly. Even if the test suites are not run in this chapter
-    (they are not mandatory), these packages are required to run the test
-    suites in <xref linkend="chapter-building-system"/>.</para>
+    <para>Ce paquet et les deux suivants (Expect et DejaGNU) sont installés
+    uniquement pour supporter les suites de tests de GCC et Binutils.
+    Installer ces trois paquets dans un but de tests pourrait sembler
+    excessif mais c'est très rassurant, voire essentiel, de savoir que les
+    outils les plus importants fonctionnent correctement. Même si les suites
+    de tests ne sont pas exécutées dans ce chapitre (elles ne sont pas
+    obligatoires), ces paquets sont nécessaires pour lancer les suites de
+    tests du <xref linkend="chapter-building-system"/>.</para>
 
-    <para>Prepare Tcl for compilation:</para>
+    <para>Préparez la compilation de Tcl&nbsp;:</para>
 
 <screen><userinput remap="configure">cd unix
 ./configure --prefix=/tools</userinput></screen>
 
-    <para>Build the package:</para>
+    <para>Construisez le paquet&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>To test the results, issue:</para>
+    <para>Pour tester les résultats, lancez&nbsp;:
+    
+    <screen><userinput remap="test">TZ=UTC make test</userinput></screen>
+
+    La suite de tests de Tcl
+    est connue pour ses échecs sous certaines conditions concernant l'hôte,
+    conditions qu'on ne comprend pas toujours. Du coup, des échecs de la suite 
+    de tests ne sont pas surprenants ici et ne doivent pas être considérés comme critiques. Le
+    paramètre <parameter>TZ=UTC</parameter>  initialise le fuseau horaire avec 
+    le temps universel coordonné (<foreignphrase>Coordinated
+    Universal Time soit l'UTC) connu aussi sous le nom de Greenwich Mean Time
+    (GMT), mais seulement pour
+    la durée de l'exécution de la suite de tests. Ceci nous assure que les tests
+    d'horloge fonctionneront correctement. Des détails sur la variable
+    d'environnement <envar>TZ</envar> sont fournis dans
+    <xref linkend="chapter-bootscripts"/>.</para>
 
-<screen><userinput remap="test">TZ=UTC make test</userinput></screen>
-
-    <para>The Tcl test suite is known to experience failures under certain host
-    conditions that are not fully understood. Therefore, test suite failures
-    here are not surprising, and are not considered critical. The
-    <parameter>TZ=UTC</parameter> parameter sets the time zone to Coordinated
-    Universal Time (UTC), also known as Greenwich Mean Time (GMT), but only
-    for the duration of the test suite run. This ensures that the clock tests
-    are exercised correctly. Details on the <envar>TZ</envar> environment
-    variable are provided in <xref linkend="chapter-bootscripts"/>.</para>
-
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
-    <para>Install Tcl's headers. The next package, Expect, requires them
-    to build.</para>
+    <para>Installez les en-têtes de Tcl, le prochain paquet, Expect, en a
+    besoin pour se construire.</para>
 
 <screen><userinput remap="install">make install-private-headers</userinput></screen>
 
-    <para>Now make a necessary symbolic link:</para>
+    <para>Maintenant, ajoutez un lien symbolique nécessaire&nbsp;:</para>
 
-<screen><userinput remap="install">ln -sv tclsh8.4 /tools/bin/tclsh</userinput></screen>
+<screen><userinput remap="install">ln -sv tclsh8.4 /tools/bin/tclsh</userinput>
+</screen>
 
   </sect2>
 
   <sect2 id="contents-tcl" role="content">
-    <title>Contents of Tcl</title>
+    <title>Contenu de Tcl</title>
 
     <segmentedlist>
-      <segtitle>Installed programs</segtitle>
-      <segtitle>Installed library</segtitle>
+      <segtitle>Programmes installés</segtitle>
+      <segtitle>Bibliothèque installée</segtitle>
 
       <seglistitem>
-        <seg>tclsh (link to tclsh8.4) and tclsh8.4</seg>
-        <seg>libtcl8.4.so</seg>
+        <seg>tclsh (lien vers tclsh8.4) et tclsh8.4</seg> <seg>libtcl8.4.so</seg>
       </seglistitem>
     </segmentedlist>
 
     <variablelist>
-      <bridgehead renderas="sect3">Short Descriptions</bridgehead>
+      <bridgehead renderas="sect3">Descriptions courtes</bridgehead>
       <?dbfo list-presentation="list"?>
       <?dbhtml list-presentation="table"?>
 
       <varlistentry id="tclsh8.4">
         <term><command>tclsh8.4</command></term>
         <listitem>
-          <para>The Tcl command shell</para>
+          <para>Le shell de commandes Tcl</para>
           <indexterm zone="ch-tools-tcl tclsh8.4">
             <primary sortas="b-tclsh8.4">tclsh8.4</primary>
           </indexterm>
@@ -116,7 +121,7 @@
       <varlistentry id="tclsh">
         <term><command>tclsh</command></term>
         <listitem>
-          <para>A link to tclsh8.4</para>
+          <para>Un lien vers tclsh8.4</para>
           <indexterm zone="ch-tools-tcl tclsh">
             <primary sortas="b-tclsh">tclsh</primary>
           </indexterm>
@@ -126,7 +131,7 @@
       <varlistentry id="libtcl8.4.so">
         <term><filename class="libraryfile">libtcl8.4.so</filename></term>
         <listitem>
-          <para>The Tcl library</para>
+          <para>La bibliothèque Tcl</para>
           <indexterm zone="ch-tools-tcl libtcl8.4.so">
             <primary sortas="c-libtcl8.4.so">libtcl8.4.so</primary>
           </indexterm>
diff -Naur BOOK/chapter05/texinfo.xml BOOKfr/chapter05/texinfo.xml
--- BOOK/chapter05/texinfo.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/texinfo.xml	2008-06-24 09:02:47.000000000 +0100
@@ -18,7 +18,7 @@
 
   <indexterm zone="ch-tools-texinfo">
     <primary sortas="a-Texinfo">Texinfo</primary>
-    <secondary>tools</secondary>
+    <secondary>outils</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,21 +41,21 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Texinfo</title>
+    <title>Installation de Texinfo</title>
 
-    <para>Prepare Texinfo for compilation:</para>
+    <para>Préparez la compilation de Texinfo&nbsp;:</para>
 
 <screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
 
-    <para>Compile the package:</para>
+    <para>Compilez le paquet&nbsp;:</para>
 
 <screen><userinput remap="make">make</userinput></screen>
 
-    <para>To test the results, issue:</para>
+    <para>Pour tester les résultats, lancez&nbsp;:</para>
 
 <screen><userinput remap="test">make check</userinput></screen>
 
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
@@ -64,7 +64,7 @@
   <sect2 role="content">
     <title/>
 
-    <para>Details on this package are located in
+    <para>Les détails de ce paquet sont situés dans
     <xref linkend="contents-texinfo" role="."/></para>
 
   </sect2>
diff -Naur BOOK/chapter05/toolchaintechnotes.xml BOOKfr/chapter05/toolchaintechnotes.xml
--- BOOK/chapter05/toolchaintechnotes.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/toolchaintechnotes.xml	2008-06-23 22:13:03.000000000 +0100
@@ -8,210 +8,278 @@
 <sect1 id="ch-tools-toolchaintechnotes">
   <?dbhtml filename="toolchaintechnotes.html"?>
 
-  <title>Toolchain Technical Notes</title>
+  <title>Notes techniques sur l'ensemble d'outils</title>
 
-  <para>This section explains some of the rationale and technical details
-  behind the overall build method. It is not essential to immediately
-  understand everything in this section. Most of this information will be
-  clearer after performing an actual build. This section can be referred
-  back to at any time during the process.</para>
-
-  <para>The overall goal of <xref linkend="chapter-temporary-tools"/> is to
-  provide a temporary environment that can be chrooted into and from which can be
-  produced a clean, trouble-free build of the target LFS system in <xref
-  linkend="chapter-building-system"/>. Along the way, we separate the new system
-  from the host system as much as possible, and in doing so, build a
-  self-contained and self-hosted toolchain. It should be noted that the build
-  process has been designed to minimize the risks for new readers and provide
-  maximum educational value at the same time.</para>
+  <para>Cette section explique certains détails rationnels et techniques
+  derrière la méthode de construction. Il n'est pas essentiel de
+  comprendre immédiatement tout ce qui se trouve dans cette section. La
+  plupart des informations seront plus claires après avoir réalisé
+  réellement une construction complète. Cette section peut servir de
+  référence à tout moment lors du processus de construction.</para>
+
+  <para>Le but global de <xref linkend="chapter-temporary-tools"/> est
+  de fournir un environnement temporaire où nous pouvons utiliser chroot
+  à partir duquel nous pouvons produit une construction propre, sans
+  soucis, du système LFS cible dans 
+
+  <xref linkend="chapter-building-system"/>. Tout au long du chemin,
+  nous nous séparons du système hôte autant que possible et, se faisant,
+  nous construisons un ensemble d'outils qui se tient. Il devrait être
+  noté que le processus de construction a été conçu pour minimiser les
+  risques pour les nouveaux lecteurs et pour fournir une valeur
+  éducative maximale en même temps.</para>
 
   <important>
-    <para>Before continuing, be aware of the name of the working platform,
-    often referred to as the target triplet. Many times, the target
-    triplet will probably be <emphasis>i686-pc-linux-gnu</emphasis>. A
-    simple way to determine the name of the target triplet is to run the
-    <command>config.guess</command> script that comes with the source for
-    many packages. Unpack the Binutils sources and run the script:
-    <userinput>./config.guess</userinput> and note the output.</para>
-
-    <para>Also be aware of the name of the platform's dynamic linker, often
-    referred to as the dynamic loader (not to be confused with the standard
-    linker <command>ld</command> that is part of Binutils). The dynamic linker
-    provided by Glibc finds and loads the shared libraries needed by a program,
-    prepares the program to run, and then runs it. The name of the dynamic
-    linker will usually be <filename class="libraryfile">ld-linux.so.2</filename>.
-    On platforms that are less prevalent, the name might be <filename
-    class="libraryfile">ld.so.1</filename>, and newer 64 bit platforms might
-    be named something else entirely. The name of the platform's dynamic linker
-    can be determined by looking in the <filename class="directory">/lib</filename>
-    directory on the host system. A sure-fire way to determine the name is to
-    inspect a random binary from the host system by running:
-    <userinput>readelf -l &lt;name of binary&gt; | grep interpreter</userinput>
-    and noting the output. The authoritative reference covering all platforms
-    is in the <filename>shlib-versions</filename> file in the root of the Glibc
-    source tree.</para>
+    <para>Avant de continuer, faites attention au nom de la plateforme de travail,
+    souvent appelée la triplette cible. La plupart du temps, la triplette
+    cible sera probablement <emphasis>i686-pc-linux-gnu</emphasis>. Une façon simple de
+    déterminer le nom de la triplette cible est de lancer le script
+    <command>config.guess</command> venant avec le source pour un grand nombre de
+    paquetages. Déballez les sources de Binutils, lancez le script
+    <userinput>./config.guess</userinput> et notez la sortie.</para>
+    
+    <para>De même, faites attention au nom de l'éditeur de liens de la
+    plateforme, souvent appelé le chargeur dynamique (à ne pas confondre
+    avec l'éditeur de liens <command>ld</command> faisant partie de
+    Binutils). Le chargeur dynamique fourni par Glibc trouve et charge
+    les bibliothèques partagées nécessaires à un programme pour
+    s'exécuter, puis l'exécute. Le nom de l'éditeur dynamique sera
+    habituelleme
+
+    <filename class="libraryfile">ld-linux.so.2</filename>.
+    Sur des plateformes moins connues, le nom pourrait être
+
+    <filename class="libraryfile">ld.so.1</filename>, alors que les
+    nouvelles plateformes 64 bits pourraient être nommées encore
+    différemment. Le nom de l'éditeur de liens dynamiques de la
+    plateforme peut être déterminé en cherchant dans le répertoire
+
+    <filename class="directory">/lib</filename> du système hôte. Une
+    façon certaine de déterminer le nom est d'inspecter un binaire au
+    hasard du système hôte en exécutant&nbsp;: 
+
+    <userinput>readelf -l &lt;nom du binaire&gt; | grep interpreter</userinput>
+    et de noter le résultat. La référence faisant autorité couvrant toutes les
+    plateformes est dans le fichier <filename>shlib-versions</filename> à la 
+
+    racine du répertoire des sources de Glibc.</para>
   </important>
 
-  <para>Some key technical points of how the <xref
-  linkend="chapter-temporary-tools"/> build method works:</para>
+  <para>Quelques points techniques sur la façon dont fonctionne la
+  méthode de construction 
+
+  <xref linkend="chapter-temporary-tools"/>&nbsp;:</para>
 
   <itemizedlist>
     <listitem>
-      <para>The process is similar in principle to cross-compiling, whereby
-      tools installed in the same prefix work in cooperation, and thus utilize
-      a little GNU <quote>magic</quote></para>
+      <para>Le processus est similaire dans son principe à la
+      cross-compilation où les outils installés dans le même préfixe fonctionnent
+      en coopération et utilisent, du coup, un peu de <quote>magie</quote> GNU.</para>
     </listitem>
     <listitem>
-      <para>Careful manipulation of the standard linker's library search path
-      ensures programs are linked only against chosen libraries</para>
+      <para>Une manipulation attentionnée du chemin de recherche des
+      bibliothèques de l'éditeur de liens standard vous assure que les programmes
+      sont liés seulement avec les bibliothèques choisies.</para>
     </listitem>
     <listitem>
-      <para>Careful manipulation of <command>gcc</command>'s
-      <filename>specs</filename> file tells the compiler which target dynamic
-      linker will be used</para>
+      <para>Une manipulation attentionnée du fichier <filename>specs</filename>
+      de <command>gcc</command> indique au compilateur
+      l'éditeur de liens dynamique cible à utiliser.</para>
     </listitem>
   </itemizedlist>
 
-  <para>Binutils is installed first because the <command>configure</command>
-  runs of both GCC and Glibc perform various feature tests on the assembler
-  and linker to determine which software features to enable or disable. This
-  is more important than one might first realize. An incorrectly configured
-  GCC or Glibc can result in a subtly broken toolchain, where the impact of
-  such breakage might not show up until near the end of the build of an
-  entire distribution. A test suite failure will usually highlight this error
-  before too much additional work is performed.</para>
-
-  <para>Binutils installs its assembler and linker in two locations,
-  <filename class="directory">/tools/bin</filename> and <filename
-  class="directory">/tools/$TARGET_TRIPLET/bin</filename>. The tools in one
-  location are hard linked to the other. An important facet of the linker is
-  its library search order. Detailed information can be obtained from
-  <command>ld</command> by passing it the <parameter>--verbose</parameter>
-  flag. For example, an <userinput>ld --verbose | grep SEARCH</userinput>
-  will illustrate the current search paths and their order. It shows which
-  files are linked by <command>ld</command> by compiling a dummy program and
-  passing the <parameter>--verbose</parameter> switch to the linker. For example,
-  <userinput>gcc dummy.c -Wl,--verbose 2&gt;&amp;1 | grep succeeded</userinput>
-  will show all the files successfully opened during the linking.</para>
-
-  <para>The next package installed is GCC. An example of what can be
-  seen during its run of <command>configure</command> is:</para>
+  <para>Binutils est tout d'abord installé parce que les exécutions de
+  Glibc et GCC par <command>configure</command> réalisent quelques tests
+  de fonctionnalités sur l'assembleur et l'éditeur de liens pour
+  déterminer quelle fonctionnalité logicielle activer ou désactiver.
+  Ceci est plus important que ce que vous pourriez imaginer. Un GCC ou
+  une Glibc mal configuré peut aboutir à un ensemble d'outils
+  subtilement cassé, et l'impact d'une telle cassure ne se verrait pas
+  avant la fin de la construction de la distribution complète. Un échec
+  dans la suite de tests surlignera habituellement cette erreur avant
+  que trop de travail supplémentaire n'ait été réalisé.<</para>
+
+  <para>Binutils installe son assembleur et son éditeur de liens à deux
+  endroits, <filename class="directory">/tools/bin</filename> et
+  <filename class="directory">/tools/$TARGET_TRIPLET/bin</filename>. Les
+  outils dans un emplacement sont liés en dur à l'autre. Un aspect
+  important de l'éditeur de liens est son ordre de recherche des
+  bibliothèques. Vous pouvez obtenir  des informations détaillées à
+  partir de <command>ld</command> en lui passant le commutateur
+  <parameter>--verbose</parameter>. Par exemple, un
+
+  <userinput>ld --verbose | grep SEARCH</userinput> illustrera les
+  chemins de recherche réels et leur ordre. Il montre quels fichiers
+  sont liés par <command>ld</command> en compilant un programme de test
+  et en passant le commutateur <parameter>--verbose</parameter> à
+  l'éditeur de liens. Par exemple, 
+
+  <userinput>gcc dummy.c -Wl,--verbose 2&gt;&amp;1 | grep
+  succeeded</userinput> affichera tous les fichiers ouverts avec succès
+  lors de l'édition des liens.</para>
+
+  <para>Le prochain paquetage installé est GCC. Un exemple de ce qui
+  peut être vu pendant son exécution de <command>configure</command>
+  est&nbsp;:</para>
 
 <screen><computeroutput>checking what assembler to use...
         /tools/i686-pc-linux-gnu/bin/as
 checking what linker to use... /tools/i686-pc-linux-gnu/bin/ld</computeroutput></screen>
 
-  <para>This is important for the reasons mentioned above. It also demonstrates
-  that GCC's configure script does not search the PATH directories to find which
-  tools to use. However, during the actual operation of <command>gcc</command>
-  itself, the same search paths are not necessarily used. To find out which
-  standard linker <command>gcc</command> will use, run:
-  <userinput>gcc -print-prog-name=ld</userinput>.</para>
-
-  <para>Detailed information can be obtained from <command>gcc</command> by
-  passing it the <parameter>-v</parameter> command line option while compiling
-  a dummy program. For example, <userinput>gcc -v dummy.c</userinput> will show
-  detailed information about the preprocessor, compilation, and assembly stages,
-  including <command>gcc</command>'s included search paths and their order.</para>
-
-  <para>The next package installed is Glibc. The most important considerations
-  for building Glibc are the compiler, binary tools, and kernel headers. The
-  compiler is generally not an issue since Glibc will always use the
-  <command>gcc</command> found in a <envar>PATH</envar> directory. The binary
-  tools and kernel headers can be a bit more complicated. Therefore, take no
-  risks and use the available configure switches to enforce the correct
-  selections. After the run of <command>configure</command>, check the contents
-  of the <filename>config.make</filename> file in the <filename
-  class="directory">glibc-build</filename> directory for all important details.
-  Note the use of <parameter>CC="gcc -B/tools/bin/"</parameter> to control which
-  binary tools are used and the use of the <parameter>-nostdinc</parameter>
-  and <parameter>-isystem</parameter> flags to control the compiler's include
-  search path. These items highlight an important aspect of the Glibc
-  package&mdash;it is very self-sufficient in terms of its build machinery and
-  generally does not rely on toolchain defaults.</para>
-
-  <para>After the Glibc installation, make some adjustments to ensure that
-  searching and linking take place only within the <filename
-  class="directory">/tools</filename> prefix.  Install an adjusted
-  <command>ld</command>, which has a hard-wired search path limited to
-  <filename class="directory">/tools/lib</filename>. Then amend
-  <command>gcc</command>'s specs file to point to the new dynamic linker in
-  <filename class="directory">/tools/lib</filename>. This last step is vital
-  to the whole process. As mentioned above, a hard-wired path to a dynamic
-  linker is embedded into every Executable and Link Format (ELF)-shared
-  executable.  This can be inspected by running:
-  <userinput>readelf -l &lt;name of binary&gt; | grep interpreter</userinput>.
-  Amending gcc's specs file ensures that every program compiled from here
-  through the end of this chapter will use the new dynamic linker in
+  <para>C'est important pour les raisons mentionnées ci-dessus. Cela démontre
+  aussi que le script configure de GCC ne cherche pas les répertoires PATH pour
+  trouver les outils à utiliser. Néanmoins, lors d'une opération normale de
+
+  <command>gcc</command>, les mêmes chemins de recherche ne sont pas
+  forcément utilisés. Pour trouver quel éditeur de liens standard
+  <command>gcc</command> utilisera, lancez&nbsp;:
+
+  <userinput>gcc  -print-prog-name=ld</userinput>.</para>
+
+  <para>Vous  pouvez obtenir des informations détaillées à partir de
+  <command>gcc</command> en lui fournissant l'option en ligne de
+  commande <parameter>-v</parameter> lors de la compilation d'un
+  programme de tests. Par exemple, <userinput>gcc -v dummy.c</userinput>
+  affichera des informations
+
+  détaillées sur les étapes du préprocesseur, de la compilation et de
+  l'assemblage ceci comprenant les chemins de recherche inclus par
+  <command>gcc</command> et leur ordre.</para>
+
+  <para>Le prochain paquetage installé est Glibc. Les plus importantes
+  considérations pour construire Glibc est le compilateur, les outils
+  binaires et les en-têtes du noyau. Le compilateur n'est généralement
+  pas un problème car Glibc utilise toujours le <command>gcc</command>
+  trouvé dans un répertoire du <envar>PATH</envar>. Les outils binaires
+  et les en-têtes du noyau peuvent être un peu plus compliqués. Du coup,
+  ne prenez pas de risque et utilisez les options disponibles de
+  configure pour renforcer les bonnes sélections. Après l'exécution de 
+  <command>configure</command>, vérifiez le contenu du fichier <filename>config.make</filename>
+  dans le répertoire <filename class="directory">glibc-build</filename> pour tous les détails importants. Notez
+  l'utilisation de 
+
+  <parameter>CC="gcc -B/tools/bin/"</parameter> pour contrôler le outils
+  binaires utilisés, et l'utilisation des  commutateurs
+  <parameter>-nostdinc</parameter> et <parameter>-isystem</parameter>
+  pour contrôler le chemin de recherche des en-têtes du compilateur. Ces
+  éléments soulignent un aspect important du paquetage glibc&mdash;il
+  est auto-suffisant en terme de machinerie de construction et ne repose
+  généralement pas sur l'ensemble d'outils par défaut.</para>
+
+  <para>Après l'installation de Glibc, réalisez les ajustements pour
+  vous assurer que la recherche et l'édition de liens prennent seulement
+  place à l'intérieur du préfixe
+
+  <filename class="directory">/tools</filename>. Installez un
+  <command>ld</command> ajusté qui a un chemin de recherche limité, codé
+  en dur, vers <filename class="directory">/tools/lib</filename>. Puis,
+  modifiez le
+  fichier specs de <command>gcc</command>  pour pointer vers le nouvel éditeur de
+
+  liens dynamique dans 
+
+  <filename class="directory">/tools/lib</filename>. Cette
+
+  dernière étape est vitale pour le processus complet. Comme mentionné ci-dessus,
+
+  un chemin en dur vers un éditeur de liens est intégré dans chaque exécutable
+
+  ainsi que dans chaque exécutable partagé (ELF). Ceci peut être inspecté en
+
+  exécutant&nbsp;:
+
+   <userinput>readelf -l &lt;nom du binaire&gt; | grep interpreter</userinput>. 
+
+  Modifier le fichier specs de gcc nous assure que chaque programme
+  compilé à partir de maintenant et jusqu'à la fin de ce chapitre
+  utilisera le nouvel éditeur de liens dynamiques dans 
+
   <filename class="directory">/tools/lib</filename>.</para>
 
-  <para>The need to use the new dynamic linker is also the reason why
-  the Specs patch is applied for the second pass of GCC. Failure to do
-  so will result in the GCC programs themselves having the name of the
-  dynamic linker from the host system's <filename
-  class="directory">/lib</filename> directory embedded into them, which
-  would defeat the goal of getting away from the host.</para>
-
-  <para>During the second pass of Binutils, we are able to utilize the
-  <parameter>--with-lib-path</parameter> configure switch to control
-  <command>ld</command>'s library search path.  From this point onwards,
-  the core toolchain is self-contained and self-hosted. The remainder of
-  the <xref linkend="chapter-temporary-tools"/> packages all build against
-  the new Glibc in <filename class="directory">/tools</filename>.</para>
-
-  <para>Upon entering the chroot environment in <xref
-  linkend="chapter-building-system"/>, the first major package to be
-  installed is Glibc, due to its self-sufficient nature mentioned above.
-  Once this Glibc is installed into <filename
-  class="directory">/usr</filename>, perform a quick changeover of the
-  toolchain defaults, then proceed in building the rest of the target
-  LFS system.</para>
+  <para>Le besoin d'utiliser le nouvel éditeur de liens dynamique est
+  aussi la raison pour laquelle le correctif Specs est appliqué lors de
+  la seconde passe de GCC. Échouer sur ce point aboutira à des
+  programmes GCC ayant le nom de l'éditeur de liens  provenant du
+  répertoire 
+
+  <filename class="directory">/lib</filename> Le besoin d'utiliser le
+  nouvel éditeur de liens dynamique est aussi la raison pour laquelle le
+  correctif Specs est appliqué lors de la seconde passe de GCC. Échouer
+  sur ce point aboutira à des programmes GCC ayant le nom de l'éditeur
+  de liens  provenant du répertoire 
+
+  <filename  class="directory">/lib</filename> du système hôte intégré
+  en eux, ce qui empêchera le but de s'éloigner de l'hôte.</para>
+
+  <para>Lors de la seconde passe de Binutils, nous sommes capable  
+d'utiliser l'option <parameter>--with-lib-path</parameter> de  
+configure pour contrôler le chemin de recherche des bibliothèques de
+<command>ld</command>. À partir de là, l'ensemble d'outils principal est
+contenu en lui-même. Le reste des paquetages de <xref  
+linkend="chapter-temporary-tools"/> se construit à partir de la nouvelle
+Glibc dans
+
+<filename class="directory">/tools</filename>.</para>
+
+  <para>Avant d'entrer dans l'environnement chroot dans <xref
+  linkend="chapter-building-system"/>, le premier paquetage majeur à
+  être installé est Glibc, à cause de sa nature auto-suffisante
+  mentionnée ci-dessus. Une fois que Glibc est installée dans  <filename
+  class="directory">/usr</filename>, réalisez une rapide modification
+  des valeurs par défaut de l'ensemble des outils puis continuez la
+  construction du reste du système LFS cible.</para>
 
   <!-- FIXME: Removed as part of the fix for bug 1061 - we no longer build pass1
       packages statically, therefore this explanation isn't required
 
-  <sect2>
-  <title>Notes on Static Linking</title>
+  <sect2> <title>Notes sur l'édition de liens statiques</title>
 
-  <para>Besides their specific task, most programs have to perform many
-  common and sometimes trivial operations. These include allocating
-  memory, searching directories, reading and writing files, string
-  handling, pattern matching, arithmetic, and other tasks. Instead of
-  obliging each program to reinvent the wheel, the GNU system provides
-  all these basic functions in ready-made libraries. The major library
-  on any Linux system is Glibc.</para>
-
-  <para>There are two primary ways of linking the functions from a
-  library to a program that uses them&mdash;statically or dynamically. When
-  a program is linked statically, the code of the used functions is
-  included in the executable, resulting in a rather bulky program. When
-  a program is dynamically linked, it includes a reference to the
-  dynamic linker, the name of the library, and the name of the function,
-  resulting in a much smaller executable. A third option is to use the
-  programming interface of the dynamic linker (see <filename>dlopen(3)</filename>
-  for more information).</para>
-
-  <para>Dynamic linking is the default on Linux and has three major
-  advantages over static linking. First, only one copy of the executable
-  library code is needed on the hard disk, instead of having multiple
-  copies of the same code included in several programs, thus saving
-  disk space. Second, when several programs use the same library
-  function at the same time, only one copy of the function's code is
-  required in core, thus saving memory space. Third, when a library
-  function gets a bug fixed or is otherwise improved, only the one
-  library needs to be recompiled instead of recompiling all programs
-  that make use of the improved function.</para>
-
-  <para>If dynamic linking has several advantages, why then do we
-  statically link the first two packages in this chapter? The reasons
-  are threefold&mdash;historical, educational, and technical. The
-  historical reason is that earlier versions of LFS statically linked
-  every program in this chapter. Educationally, knowing the difference
-  between static and dynamic linking is useful. The technical benefit is
-  a gained element of independence from the host, meaning that those
-  programs can be used independently of the host system. However, it is
-  worth noting that an overall successful LFS build can still be
-  achieved when the first two packages are built dynamically.</para>
+  <para>En dehors de leur tâches spécifiques, la plupart des programmes
+  doivent réaliser un grand nombre d'opérations habituelles, voire
+  triviales. Elles incluent l'allocation de mémoire, la recherche dans
+  des répertoire, la lecture et l'écriture de fichiers, la gestion des
+  chaînes de caractères, la reconnaissance de modèles, l'arithmétique et
+  d'autres tâches. Au lieu d'obliger chaque programme à réinventer la
+  roue, le système GNU fournit toutes ces fonctions de base dans des
+  bibliothèques toutes prêtes. La bibliothèque majeure sur un système
+  Linux est Glibc.</para>
+
+  <para>Il existe deux façons de lier les fonctions d'une bibliothèque
+  dans un programme qui les utilise&mdash;statiquement ou dynamiquement.
+  Quand un programme est lié statiquement, le code des fonctions
+  utilisées est inclus dans l'exécutable, donnant un gros programme.
+  Quand un programme est lié dynamiquement, il inclut une référence à
+  l'éditeur de liens, le nom de la bibliothèque et le nom de la
+  fonction, aboutissant à un exécutable bien plus petit. Une troisième
+  option est d'utiliser l'interface de programmation de l'éditeur de
+  liens (voir la page man <filename>dlopen(3)</filename> pour plus
+  d'informations).</para>
+
+  <para>L'édition de liens dynamiques est le comportement par défaut sur
+  Linux et a trois avantages majeurs sur l'édition de liens statiques.
+  Tout d'abord, seule une copie du code exécutable de la bibliothèque
+  est nécessaire sur le disque dur, à la place de plusieurs copies du
+  même code inclus dans plusieurs programmes, sauvegardant ainsi de
+  l'espace disque. Deuxièmement, quand plusieurs programmes utilisent la
+  même fonction de bibliothèque en même temps, seule une copie du code
+  de la fonction est requis en mémoire, sauvegardant ainsi de la mémoire
+  vive. Troisièmement, quand une fonction d'une bibliothèque est
+  corrigée ou améliorée, seule la bibliothèque doit être recompilée au
+  lieu de recompiler tous les programmes utilisant ladite
+  fonction.</para>
+
+  <para>Si l'édition de liens dynamiques a plusieurs avantages, alors  
+pourquoi   utilisons-nous l'édition statique pour les deux premiers
+paquetages   dans ce  chapitre&nbsp;? Il y a trois raisons &mdash;
+historique, éducative et technique. La raison historique est que les
+versions antérieures de LFS liaient statiquement tous les programmes de
+ce chapitre. Sur le plan éducatif, connaître les différences entre
+statique et dynamique est utile. Le bénéfice technique est un élément
+gagné pour l'indépendance sur le système hôte, signifiant que les
+programmes peuvent être utilisés indépendamment du système hôte.
+Néanmoins, il est bon de noter qu'une construction réussie de LFS peut
+toujours se faire quand les deux premiers paquetages de LFS sont
+construits dynamiquement.</para>
 
   </sect2>-->
 
diff -Naur BOOK/chapter05/udev.xml BOOKfr/chapter05/udev.xml
--- BOOK/chapter05/udev.xml	1970-01-01 01:00:00.000000000 +0100
+++ BOOKfr/chapter05/udev.xml	2007-06-06 15:27:04.000000000 +0100
@@ -0,0 +1,68 @@
+<?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-tools-udev" role="wrap">
+<title>Udev-&udev-version;</title>
+<?dbhtml filename="udev.html"?>
+
+<indexterm zone="ch-tools-udev">
+<primary sortas="a-Udev">Udev</primary>
+<secondary>outils</secondary></indexterm>
+
+<sect2 role="package"><title/>
+<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="../chapter06/udev.xml" xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
+
+<segmentedlist>
+<segtitle>&buildtime;</segtitle>
+<segtitle>&diskspace;</segtitle>
+<seglistitem><seg>0,2&nbsp;SBU</seg><seg>5,2&nbsp;Mo</seg></seglistitem>
+</segmentedlist>
+
+
+<xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="../chapter06/udev.xml" xpointer="xpointer(/sect1/sect2[1]/segmentedlist[2])"/>
+
+</sect2>
+
+<sect2 role="installation">
+<title>Installation d'Udev</title>
+
+<para>Le programme <command>udevstart</command> code en dur le chemin vers le
+programme <command>udev</command>, ce qui va créer des problèmes car
+<command>udev</command> a été installé à un emplacement non standard. Corrigez
+ceci en exécutant ces commandes&nbsp;:</para>
+
+<screen><userinput>sed -i 's@/sbin/udev@/tools/sbin/udev@g' udevstart.c</userinput></screen>
+
+<para>De plus, assurez-vous que <command>udev</command> recherche 
+ses fichiers de configuration au bon endroit&nbsp;:</para>
+
+<screen><userinput>sed -i 's@/etc@/tools/etc@g' etc/udev/udev.conf.in</userinput></screen>
+
+<para>Maintenant, compilez Udev&nbsp;:</para>
+
+<screen><userinput>make prefix=/tools etcdir=/tools/etc</userinput></screen>
+
+<para>Ce paquet ne propose pas de suite de tests.</para>
+
+<para>Installez le paquet&nbsp;:</para>
+
+<screen><userinput>make DESTDIR=/tools udevdir=/dev install</userinput></screen>
+
+<para>La configuration par défaut d'Udev est loin d'être idéale, installez
+en remplacement ces fichiers de configuration spécifiques à LFS&nbsp;:</para>
+
+<screen><userinput>cp ../udev-config-2.permissions \
+    /tools/etc/udev/permissions.d/00-lfs.permissions
+cp ../udev-config-1.rules /tools/etc/udev/rules.d/00-lfs.rules</userinput></screen>
+
+</sect2>
+
+<sect2 role="content"><title/>
+<para>Les détails sur ce paquet sont situés dans <xref
+linkend="contents-udev" role="."/></para>
+</sect2>
+
+</sect1>
+
diff -Naur BOOK/chapter05/util-linux-ng.xml BOOKfr/chapter05/util-linux-ng.xml
--- BOOK/chapter05/util-linux-ng.xml	2008-07-15 00:49:36.000000000 +0100
+++ BOOKfr/chapter05/util-linux-ng.xml	2008-06-24 09:08:50.000000000 +0100
@@ -18,7 +18,7 @@
 
   <indexterm zone="ch-tools-util-linux-ng">
     <primary sortas="a-Util-linux-ng">Util-linux-ng</primary>
-    <secondary>tools</secondary>
+    <secondary>outils</secondary>
   </indexterm>
 
   <sect2 role="package">
@@ -41,25 +41,25 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of Util-linux-ng</title>
+    <title>Installation de Util-linux-ng</title>
 
-    <para>Prepare Util-linux-ng for compilation:</para>
+    <para>Préparez la compilation de util-linux-ng&nbsp;:</para>
 
 <screen><userinput remap="configure">./configure --prefix=/tools</userinput></screen>
 
-    <para>Only a few of the utilities contained in this package need to be
-    built:</para>
+    <para>Seuls quelques utilitaires contenu dans ce paquet doivent être installés
+    construits&nbsp;:</para>
 
 <screen><userinput remap="make">make -C mount mount umount
 make -C text-utils more</userinput></screen>
 
-    <para>This package comes with a test suite, but running it will cause all of
-    the binaries to be built and tested.  If you still wish to run the tests,
-    issue:</para>
+    <para>Ce paquet est fourni avec une suite de test, mais son exécution
+    amènera tous les binaires à se compiler et à être testés. Si vous souhaitez
+    toujours lancer les tests, lancez&nbsp;:</para>
 
 <screen><userinput remap="test">make check</userinput></screen>
 
-    <para>Copy these programs to the temporary tools directory:</para>
+    <para>Copiez ces programmes dans le répertoire des outils temporaires:&nbsp;:</para>
 
 <screen><userinput remap="install">cp -v mount/{,u}mount text-utils/more /tools/bin</userinput></screen>
 
diff -Naur BOOK/chapter05/util-linux.xml BOOKfr/chapter05/util-linux.xml
--- BOOK/chapter05/util-linux.xml	1970-01-01 01:00:00.000000000 +0100
+++ BOOKfr/chapter05/util-linux.xml	2008-05-31 22:21:22.000000000 +0100
@@ -0,0 +1,76 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
+  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+  <!ENTITY % general-entities SYSTEM "../general.ent">
+  %general-entities;
+]>
+
+<sect1 id="ch-tools-util-linux" role="wrap">
+  <?dbhtml filename="util-linux.html"?>
+
+  <title>Util-linux-&util-linux-version;</title>
+
+  <indexterm zone="ch-tools-util-linux">
+    <primary sortas="a-Util-linux">Util-linux</primary>
+    <secondary>outils</secondary>
+  </indexterm>
+
+  <sect2 role="package">
+    <title/>
+
+    <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"
+    href="../chapter06/util-linux.xml"
+    xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
+
+    <segmentedlist>
+      <segtitle>&buildtime;</segtitle>
+      <segtitle>&diskspace;</segtitle>
+
+      <seglistitem>
+        <seg>&util-linux-ch5-sbu;</seg>
+        <seg>&util-linux-ch5-du;</seg>
+      </seglistitem>
+    </segmentedlist>
+
+  </sect2>
+
+  <sect2 role="installation">
+    <title>Installation de Util-linux</title>
+
+    <para>Util-linux n'utilise pas les en-têtes et bibliothèques tout juste
+    installés dans le répertoire <filename class="directory">/tools</filename>
+    par défaut. Ceci est corrigé en modifiant le script configure&nbsp;:</para>
+
+<screen><userinput>sed -i 's@/usr/include@/tools/include@g' configure</userinput></screen>
+
+    <para>Préparez la compilation de Util-linux&nbsp;:</para>
+
+<screen><userinput>./configure</userinput></screen>
+
+    <para>Compilez quelques routines d'aide&nbsp;:</para>
+
+<screen><userinput>make -C lib</userinput></screen>
+
+    <para>Seuls quelques utilitaires contenus dans ce paquet doivent être
+    compilés&nbsp;:</para>
+
+<screen><userinput>make -C mount mount umount
+make -C text-utils more</userinput></screen>
+
+    <para>Ce paquet ne fournit pas de suite de tests.</para>
+
+    <para>Copiez ces programmes dans le répertoire des outils temporaires:&nbsp;:</para>
+
+<screen><userinput>cp -v mount/{,u}mount text-utils/more /tools/bin</userinput></screen>
+
+  </sect2>
+
+  <sect2 role="content">
+    <title/>
+
+    <para>Les détails sur ce paquet sont disponibles dans
+    <xref linkend="contents-utillinux" role="."/></para>
+
+  </sect2>
+
+</sect1>
