From ede9b9be0a3baef5e7b8daaab72b5ff594ea12e7 Mon Sep 17 00:00:00 2001 From: Alex Gronenwoud Date: Wed, 25 Feb 2004 22:04:14 +0000 Subject: Minor textual shuffles. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3261 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter05/gcc-pass1.xml | 34 +++++++++++++++------------------- 1 file changed, 15 insertions(+), 19 deletions(-) (limited to 'chapter05/gcc-pass1.xml') diff --git a/chapter05/gcc-pass1.xml b/chapter05/gcc-pass1.xml index 08822cbf0..6cb01b4fa 100644 --- a/chapter05/gcc-pass1.xml +++ b/chapter05/gcc-pass1.xml @@ -15,14 +15,14 @@ Installation of GCC -Unpack only the GCC-core tarball, as we won't be needing a C++ compiler -for the moment. +Unpack only the GCC-core tarball, as we won't be needing the C++ compiler +nor the test suite at the moment. -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. +This package is known to behave badly when you change 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 them when building GCC. The GCC documentation recommends building GCC outside of the source directory in a dedicated build directory: @@ -52,8 +52,8 @@ seem counter-intuitive at first. But using it allows the building of having libgcc_eh.a available ensures that the configure script for Glibc (the next package we compile) produces the proper results. Note that the gcc binaries will still be linked -statically, as this is controlled by the -static -value of BOOT_LDFLAGS further on. +statically, as this is controlled by the -static +value of BOOT_LDFLAGS in the next step. --enable-languages=c: This option ensures that only the C compiler is built. The option is only needed when you @@ -78,21 +78,17 @@ reproduce itself flawlessly, which most probably means that it was compiled correctly. -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. +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. And install the package: make install -As a finishing touch we'll create the /tools/bin/cc symlink. Many programs and -scripts run cc instead of gcc, +As a finishing touch we'll create a symlink. Many programs and scripts +run cc instead of gcc, 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 cc leaves the system administrator free to decide what -- cgit v1.2.3-54-g00ecf