diff options
Diffstat (limited to 'chapter05')
| -rw-r--r-- | chapter05/binutils-inst.xml | 4 | ||||
| -rw-r--r-- | chapter05/gcc-exp.xml | 4 | ||||
| -rw-r--r-- | chapter05/gcc-inst.xml | 4 | ||||
| -rw-r--r-- | chapter05/patch-exp.xml | 2 | ||||
| -rw-r--r-- | chapter05/whystatic.xml | 6 |
5 files changed, 10 insertions, 10 deletions
diff --git a/chapter05/binutils-inst.xml b/chapter05/binutils-inst.xml index 460b8c8f3..095f0942c 100644 --- a/chapter05/binutils-inst.xml +++ b/chapter05/binutils-inst.xml @@ -3,9 +3,9 @@ <para>This package is known to behave badly when you have changed its default optimization flags (including the -march and -mcpu options). Binutils is -best left alone. Therefore, if you have defined any environment variables +best left alone. 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 binutils. You have been +recommend unsetting or modifying them when building binutils. You have been warned.</para> <para>Install Binutils by running the following commands:</para> diff --git a/chapter05/gcc-exp.xml b/chapter05/gcc-exp.xml index 87a2bdf2e..6a95c53f3 100644 --- a/chapter05/gcc-exp.xml +++ b/chapter05/gcc-exp.xml @@ -6,9 +6,9 @@ This patch fixes a few bugs. In particular it contains the "copy fix" and "var fix" documented at <ulink url="http://www.zipworld.com.au/~gschafer/lfs-tweaks.html"/>.</para> -<para><userinput>--prefix=/static:</userinput> This is NOT a typo. GCC hard +<para><userinput>--prefix=/static:</userinput> This is NOT a typo. GCC hard codes some paths while compiling and so we need to pass /static as the -prefix during ./configure. We pass the real install prefix during the +prefix during ./configure. We pass the real install prefix during the make install command later.</para> <para><userinput>--enable-languages=c:</userinput> This builds the C diff --git a/chapter05/gcc-inst.xml b/chapter05/gcc-inst.xml index b31761aea..63565f160 100644 --- a/chapter05/gcc-inst.xml +++ b/chapter05/gcc-inst.xml @@ -7,9 +7,9 @@ commands.</para> <para>This package is known to behave badly when you have changed its default optimization flags (including the -march and -mcpu options). GCC is -best left alone. Therefore, if you have defined any environment variables +best left alone. 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. You have +recommend unsetting or modifying them when building GCC. You have been warned.</para> <para>Install GCC by running the following commands:</para> diff --git a/chapter05/patch-exp.xml b/chapter05/patch-exp.xml index 0c71ff135..ed90304af 100644 --- a/chapter05/patch-exp.xml +++ b/chapter05/patch-exp.xml @@ -3,7 +3,7 @@ <para><userinput>CPPFLAGS=-D_GNU_SOURCE: </userinput> This flag fixes installation problems of this package on PPC and m68k -platforms (that we know of). It doesn't hurt compilation on other +platforms (that we know of). It doesn't hurt compilation on other platforms, such as x86, so we do it by default.</para> </sect2> diff --git a/chapter05/whystatic.xml b/chapter05/whystatic.xml index e0fc14a6b..b383455b0 100644 --- a/chapter05/whystatic.xml +++ b/chapter05/whystatic.xml @@ -29,13 +29,13 @@ saved any space (except maybe RAM until the library is needed). The <emphasis>real</emphasis> advantage of dynamically linked libraries is that we only need one copy of the library. If <filename>ls</filename> and <filename>rm</filename> both use the same library, then we don't need two -copies of the library, as they can both get the code from the same file. +copies of the library, as they can both get the code from the same file. Even when in memory, the two programs share the same code, rather than loading duplicates into memory. So not only are we saving hard disk space, but also precious RAM.</para> <para>If dynamic linking saves so much room, then why are we making everything -statically linked? Well, that's because when you chroot into your brand new +statically linked? Well, that's because when you chroot into your brand new (but very incomplete) LFS environment, these dynamic libraries won't be available because they are somewhere else in your old directory tree (<filename>/usr/lib</filename> for example) which won't be accessible @@ -52,7 +52,7 @@ all the programs we just did in Chapter 5, but this time dynamically linked, so that we can take advantage of the space saving opportunities.</para> <para>And there you have it, that's why you need to use those weird -<userinput>-static</userinput> flags. If you try building everything +<userinput>-static</userinput> flags. If you try building everything without them, you'll see very quickly what happens when you chroot into your newly crippled LFS system.</para> |