Context Navigation

-              r6952b96
+              r1cb7ced
 <?dbhtml filename="stripping.html" dir="chapter05"?>
 <para>If your LFS partition is rather small, you will be glad to learn that you
+can throw away some unnecessary things. The executables and libraries you have
+built so far contain about 130 MB of unneeded debugging symbols. Remove those
 symbols like this:</para>
+<para>The steps in this section are optional. If your LFS partition is rather
+small, you will be glad to learn that you can throw away some unnecessary
+things. The executables and libraries you have built so far contain about 130 MB
+of unneeded debugging symbols. Remove those symbols like this:</para>
 <para><screen><userinput>strip --strip-unneeded /tools/{,s}bin/*

chapter05/gcc-pass2-inst.xml

r6952b96	r1cb7ced
41	41	process is warranted here. Under normal circumstances, the GCC fixincludes
42	42	script scans your system for header files that need to be fixed. It might find
43		that the Glibc header files on your host system need to be fixed, fix them and
	43	that some Glibc header files on your host system need to be fixed, fix them and
44	44	put them in the GCC private include directory. Then, later on in Chapter 6,
45	45	after we've installed the newer Glibc, this private include directory would be

-              r6952b96
+              r1cb7ced
 <blockquote><screen>configure: WARNING:
 *** These auxiliary programs are missing or incompatible versions: autoconf
+*** These auxiliary programs are missing or incompatible versions: msgfmt
 *** some features will be disabled.
 *** Check the INSTALL file for required versions.</screen></blockquote>
 <para>The missing or incompatible <filename>autoconf</filename> program is
 harmless and doesn't cause any problems.</para>
+<para>The missing or incompatible <filename>msgfmt</filename> program is
+generally harmless and shouldn't cause us any problems.</para>
 <para>Continue with compiling the package:</para>

r6952b96	r1cb7ced
28	28
29	29	<para>Also note the use of the set +h directive. This tells bash to not use
30		it's internal path hashing. Without this directive, bash will remember paths
	30	its internal path hashing. Without this directive, bash will remember paths
31	31	to binaries. Since as we go thru chapter 6, we want to use our newly compiled
32	32	binaries as soon as they are installed, we turn off this function.</para>

-              r6952b96
+              r1cb7ced
 the possibilities for mistakes.</para>
+<para>If you plan to use compiler optimizations in this chapter,
+take a look at the optimization hint at
+<ulink url="&hints-root;optimization.txt"/>.
+Compiler optimizations can make a program run faster, but they
+may also cause compilation difficulties. If a package refuses
+to compile when using optimization, try to compile it without
+optimization and see if the problem goes away.</para>
+<para>If you plan to use compiler optimizations in this chapter, take a look at
+the optimization hint at <ulink url="&hints-root;optimization.txt"/>. Compiler
+optimizations can make a program run a touch faster, but they may also cause
+compilation difficulties and even problems when running the program. If a
+package refuses to compile when using optimization, try to compile it without
+optimization and see if the problem goes away. Even if the package does compile
+when using optimization, there is the risk it may have been compiled
+incorrectly due to compiler bugs or whatever. In short, the small gains achieved
+in using compiler optimization are generally outweighed by the risk. First time
+builders of LFS are encouraged not to bother. Your system will still be plenty
+fast enough and very stable at the same time.</para>
 <para>The order in which packages are installed in this chapter has

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