Changeset ede9b9b for chapter05/gcc-pass1.xml

Timestamp:

02/25/2004 10:04:14 PM (20 years ago)

Author:

Alex Gronenwoud <alex@…>

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, v5_1, v5_1_1, 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:

dd3e8c6

Parents:

e421d2e

Message:

Minor textual shuffles.

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

File:

• chapter05/gcc-pass1.xml (modified) (4 diffs)

chapter05/gcc-pass1.xml

@@ -16 +16 @@
 <title>Installation of GCC</title>
 
-<para>Unpack only the GCC-core tarball, as we won't be needing a C++ compiler
-for the moment.</para>
+<para>Unpack only the GCC-core tarball, as we won't be needing the C++ compiler
+nor the test suite at the moment.</para>
 
-<para>This package is known to behave badly when you have changed its
-default optimization flags (including the -march and -mcpu options).
-Therefore, if you have defined any environment variables that override
-default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
-or modifying them when building GCC.</para>
+<para>This package is known to behave badly when you change its default
+optimization flags (including the <emphasis>-march</emphasis> and
+<emphasis>-mcpu</emphasis> options). Therefore, if you have defined any
+environment variables that override default optimizations, such as CFLAGS and
+CXXFLAGS, we recommend unsetting them when building GCC.</para>
 
 <para>The GCC documentation recommends building GCC outside of the source
@@ -53 +53 @@
 script for Glibc (the next package we compile) produces the proper results.
 Note that the <command>gcc</command> binaries will still be linked
-statically, as this is controlled by the <command>-static</command>
-value of BOOT_LDFLAGS further on.</para></listitem>
+statically, as this is controlled by the <emphasis>-static</emphasis>
+value of BOOT_LDFLAGS in the next step.</para></listitem>
 
 <listitem><para><userinput>--enable-languages=c</userinput>: This option
@@ -79 +79 @@
 </itemizedlist>
 
-<para>Compilation is now complete. This is the point where we would normally
-run the test suite. But as discussed earlier, we don't recommend running the
-test suites for the temporary tools here in this chapter. However, even if we
-still wanted to run the GCC test suite, we're unable do so at this early stage
-because the test suite framework is not yet in place. Not only that, the
-programs from this first pass will soon be overwritten by those installed in
-the second pass.</para>
+<para>Compilation is now complete, and at this point we would normally run the
+test suite. But, as mentioned before, the test suite framework is not in place
+yet. And there would be little point in running the tests anyhow, since the
+programs from this first pass will soon be replaced.</para>
 
 <para>And install the package:</para>
@@ -91 +88 @@
 <screen><userinput>make install</userinput></screen>
 
-<para>As a finishing touch we'll create the <filename
-class="symlink">/tools/bin/cc</filename> symlink. Many programs and
-scripts run <command>cc</command> instead of <command>gcc</command>,
+<para>As a finishing touch we'll create a symlink. Many programs and scripts
+run <command>cc</command> instead of <command>gcc</command>,
 a thing meant to keep programs generic and therefore usable on all kinds of
 Unix systems. Not everybody has the GNU C compiler installed. Simply running