chapter5-updates.patch on Ticket #2259 – Attachment – LFS Trac

chapter05/stripping.xml

 <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>These commands will skip a number of 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

 <screen><userinput remap="make">make</userinput></screen>
+    <para>This package does not come with a test suite.</para>
+    <para>This package has a test suite, but it can only be run after the
+    package has been installed.  The tests reside in the
+    <filename class="directory">test/</filename> directory.  See the
+    <filename>README</filename> file in that directory for further details.
+    </para>
     <para>Install 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>

   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
+  <para>For the second pass of GCC, its sources also need to be modified
+  to tell GCC to use the new dynamic linker. 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

 <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>
+    because the program cannot be installed 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>

         <term><parameter>BLKID_LIBS="-lblkid -luuid"</parameter></term>
         <listitem>
           <para>When building only a subset of the package, the
           <filename class="libraryfile">libuuid.so</filename> library is not
+          <filename class="libraryfile">libuuid.a</filename> library is not
           pulled into the build as it is supposed to. This command overrides
           the default from the <filename>Makefile</filename>.</para>
         </listitem>

 <screen><userinput remap="install">make install</userinput></screen>
+    <para>To test the results, issue:</para>
+    <para>This package does come with a test suite, however, it cannot be
+    run at this time because we do not have a C++ compiler yet.</para>
-<screen><userinput remap="test">make check</userinput></screen>
   </sect2>