Changeset 9974e9b for chapter05/glibc.xml

Timestamp:

10/31/2022 06:58:31 AM (23 months ago)

Author:

Xi Ruoyao <xry111@…>

Branches:

xry111/arm64, xry111/arm64-12.0

Children:

6586901

Parents:

ad85e5b (diff), 61f8251 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.

Message:

Merge remote-tracking branch 'origin/trunk' into xry111/arm64

File:

• chapter05/glibc.xml (modified) (8 diffs)

chapter05/glibc.xml

@@ -44 +44 @@
     <title>Installation of Glibc</title>
 
-    <para>Some of the Glibc programs use the non-FHS compliant
+    <para>Some of the Glibc programs use the non-FHS-compliant
     <filename class="directory">/var/db</filename> directory to store their
     runtime data. Apply the following patch to make such programs store their
@@ -108 +108 @@
         <listitem>
           <para>This ensures that the library is installed in /usr/lib instead
-          of the default /lib64 on 64 bit machines.</para>
+          of the default /lib64 on 64-bit machines.</para>
         </listitem>
       </varlistentry>
@@ -126 +126 @@
     <para>The missing or incompatible <command>msgfmt</command> program is
     generally harmless. This <command>msgfmt</command> program is part of the
-    Gettext package which the host distribution should provide.</para>
+    Gettext package, which the host distribution should provide.</para>
 
     <note><para>There have been reports that this package may fail when
-    building as a "parallel make".  If this occurs, rerun the make command
-    with a "-j1" option.</para></note>
+    building as a "parallel make".  If that occurs, rerun the make command
+    with the "-j1" option.</para></note>
 
     <para>Compile the package:</para>
@@ -141 +141 @@
     recommendations, you are building as
     <systemitem class="username">root</systemitem>, the next command will
-    install the newly built glibc to your host system, which most likely
-    will render it unusable. So double check that the environment is
-    correctly set, before running the following command.</para></warning>
+    install the newly built Glibc to your host system, which will almost
+    certainly render it unusable. So double-check that the environment is
+    correctly set, and that you are not &root;, before running the following command.</para></warning>
 
 <screen><userinput remap="install">make DESTDIR=$LFS install</userinput></screen>
@@ -157 +157 @@
           installed. If it is not set, it defaults to the root (<filename
           class="directory">/</filename>) directory. Here we specify that
-          the package be installed in <filename class="directory">$LFS
-          </filename>, which will become the root after <xref linkend=
+          the package is installed in <filename class="directory">$LFS
+          </filename>, which will become the root directory in <xref linkend=
           "ch-tools-chroot"/>.</para>
         </listitem>
@@ -165 +165 @@
     </variablelist>
 
-    <para>Fix hardcoded path to the executable loader in
+    <para>Fix a hard coded path to the executable loader in the
     <command>ldd</command> script:</para>
 
@@ -186 +186 @@
           <filename>/lib/ld-linux-aarch64_be.so.1</filename>.</para>
 
-      <para>If the output is not shown as above or there was no output at all,
+      <para>If the output is not as shown above, or there is 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.</para>
+      continuing.</para>
 
       <para>Once all is well, clean up the test file:</para>
@@ -197 +197 @@
     </caution>
 
-    <note><para>Building packages in the next chapter will serve as an
+    <note><para>Building the packages in the next chapter will serve as an
     additional check that the toolchain has been built properly. If some
-    package, especially binutils-pass2 or gcc-pass2, fails to build, it is
+    package, especially Binutils-pass2 or GCC-pass2, fails to build, it is
     an indication that something has gone wrong with the
-    previous Binutils, GCC, or Glibc installations.</para></note>
+    preceding Binutils, GCC, or Glibc installations.</para></note>
 
     <para>Now that our cross-toolchain is complete, finalize the installation
-    of the limits.h header. For doing so, run a utility provided by the GCC
+    of the limits.h header. To do this, run a utility provided by the GCC
     developers:</para>