Context Navigation

-              rf5cc1c17
+              r2c094d6
 <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>

chapter05/gcc-exp.xml

-              rf5cc1c17
+              r2c094d6
 <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>

-              rf5cc1c17
+              r2c094d6
 <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>

rf5cc1c17	r2c094d6
4	4	<para><userinput>CPPFLAGS=-D_GNU_SOURCE: </userinput>
5	5	This flag fixes installation problems of this package on PPC and m68k
6		platforms (that we know of). It doesn't hurt compilation on other
	6	platforms (that we know of). It doesn't hurt compilation on other
7	7	platforms, such as x86, so we do it by default.</para>
8	8

-              rf5cc1c17
+              r2c094d6
 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
 …
 <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
 …
 <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>

Note: See TracChangeset for help on using the changeset viewer.