Changeset 574b0ea for chapter05/gcc-pass2.xml

Timestamp:

05/30/2004 01:41:04 PM (20 years ago)

Author:

Manuel Canales Esparcia <manuel@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

07f719a

Parents:

b711e1d

Message:

Tagging corrections in chapters 5.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3730 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:

• chapter05/gcc-pass2.xml (modified) (11 diffs)

chapter05/gcc-pass2.xml

@@ -31 +31 @@
 highly dependent on properly functioning pseudo terminals (PTYs) which are
 provided by your host. These days, PTYs are most commonly implemented via the
-<emphasis>devpts</emphasis> file system. You can quickly check if your host
+<systemitem class="filesystem">devpts</systemitem> file system. You can quickly check if your host
 system is set up correctly in this regard by performing a simple test:</para>
 
@@ -38 +38 @@
 <para>The response might be:</para>
 
-<blockquote><screen>The system has no more ptys.  Ask your system administrator to create more.</screen></blockquote>
+<blockquote><screen><computeroutput>The system has no more ptys.  Ask your system administrator to create more.</computeroutput></screen></blockquote>
 
 <para>If you receive the above message, your host doesn't have its PTYs set up
@@ -49 +49 @@
 to unpack both the core and the g++ tarballs (and testsuite too, if you want to
 run the tests). Unpacking them in your working directory, they will all unfold
-into a single <filename>gcc-&gcc-version;/</filename> subdirectory.</para>
+into a single <filename class="directory">gcc-&gcc-version;/</filename> subdirectory.</para>
 
 <para>First correct a problem and make an essential adjustment:</para>
@@ -56 +56 @@
 patch -Np1 -i ../gcc-&gcc-short-version;-specs-1.patch</userinput></screen>
 
-<para>The first patch disables the GCC <quote>fixincludes</quote> script. We
+<para>The first patch disables the GCC <command>fixincludes</command> script. We
 mentioned this briefly earlier, but a slightly more in-depth explanation of
 the fixincludes process is warranted here. Under normal circumstances, the GCC
-fixincludes script scans your system for header files that need to be fixed. It
+<command>fixincludes</command> script scans your system for header files that need to be fixed. It
 might find that some Glibc header files on your host system need to be fixed,
 fix them and put them in the GCC private include directory. Then, later on in
@@ -99 +99 @@
 <variablelist>
 <varlistentry>
-<term><userinput>--enable-clocale=gnu</userinput></term>
+<term><parameter>--enable-clocale=gnu</parameter></term>
 <listitem><para>This option
 ensures the correct locale model is selected for the C++ libraries under all
@@ -110 +110 @@
 
 <varlistentry>
-<term><userinput>--enable-threads=posix</userinput></term>
+<term><parameter>--enable-threads=posix</parameter></term>
 <listitem><para>This enables
 C++ exception handling for multi-threaded code.</para></listitem>
@@ -116 +116 @@
 
 <varlistentry>
-<term><userinput>--enable-__cxa_atexit</userinput></term>
+<term><parameter>--enable-__cxa_atexit</parameter></term>
 <listitem><para>This option
 allows use of __cxa_atexit, rather than atexit, to register C++ destructors for
@@ -126 +126 @@
 
 <varlistentry>
-<term><userinput>--enable-languages=c,c++</userinput></term>
+<term><parameter>--enable-languages=c,c++</parameter></term>
 <listitem><para>This option
 ensures that both the C and C++ compilers are built.</para></listitem>
@@ -132 +132 @@
 
 <varlistentry>
-<term><userinput>--disable-libstdcxx-pch</userinput></term>
+<term><parameter>--disable-libstdcxx-pch</parameter></term>
 <listitem><para>Don't build the
 PCH (pre-compiled header) for libstdc++. It takes up a ton of space, and we
@@ -143 +143 @@
 <screen><userinput>make</userinput></screen>
 
-<para>There is no need to use the <emphasis>bootstrap</emphasis> target now,
+<para>There is no need to use the <parameter>bootstrap</parameter> target now,
 as the compiler we're using to compile this GCC was built from the exact same
 version of the GCC sources we used earlier.</para>
@@ -154 +154 @@
 <screen><userinput>make -k check</userinput></screen>
 
-<para>The <emphasis>-k</emphasis> flag is used to make the test suite run
+<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. To get