gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-06 06:14:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

Small grammar adjustments.

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2812 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Greg Schafer 2003-09-14 09:16:58 +00:00
parent 0bf1ea9287
commit fa2e6935d7
2 changed files with 10 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
chapter05/lockingglibc.xml
View File

@ -39,8 +39,8 @@ all in. Or you can edit the specs file by hand if you want to: just replace
<para>Lastly, there is a possibility that some include files from the host <para>Lastly, there is a possibility that some include files from the host
system have found their way into gcc's private include dir. This can happen system have found their way into gcc's private include dir. This can happen
because of GCC's "fixincludes" process which part of the GCC build. We'll because of GCC's "fixincludes" process which runs as part of the GCC build.
explain more about this further on in this chapter. For now, run the We'll explain more about this further on in this chapter. For now, run the
following commands to eliminate this possibility.</para> following commands to eliminate this possibility.</para>
<para><screen><userinput>rm -f /tools/lib/gcc-lib/*/*/include/{pthread.h,bits/sigthread.h}</userinput></screen></para> <para><screen><userinput>rm -f /tools/lib/gcc-lib/*/*/include/{pthread.h,bits/sigthread.h}</userinput></screen></para>

15
chapter05/whystatic.xml
View File

@ -43,13 +43,14 @@ memory space, disk space, and recompile time.</para>
<para>But if dynamic linking saves so much space, why then are we linking <para>But if dynamic linking saves so much space, why then are we linking
the first two packages in this chapter statically? The reason is to make them the first two packages in this chapter statically? The reason is to make them
independent from the libraries on your host system. And the point in that is independent from the libraries on your host system. The advantage is that, if
that, if you are pressed for time, you could skip the second passes over GCC you are pressed for time, you could skip the second passes over GCC and
and Binutils, and just use the static versions to compile the rest of this Binutils, and just use the static versions to compile the rest of this chapter
chapter and the first few packages in the next. As in the next chapter we and the first few packages in the next. In the next chapter we will be
will be chrooted to the LFS partition and your host system's Glibc won't be chrooted to the LFS partition and once inside the chroot environment, the host
available, the programs from GCC and Binutils will need to be self-contained, system's Glibc won't be available, thus the programs from GCC and Binutils
that is statically linked.</para> will need to be self-contained, i.e. statically linked. However, we strongly
advise <emphasis>against</emphasis> skipping the second passes.</para>
</sect1> </sect1>