diff options
| author | Greg Schafer <greg@linuxfromscratch.org> | 2003-09-14 09:16:58 +0000 |
|---|---|---|
| committer | Greg Schafer <greg@linuxfromscratch.org> | 2003-09-14 09:16:58 +0000 |
| commit | fa2e6935d752ce276379bd57a1e8820cdda7ad9c (patch) | |
| tree | ef89db523eaa9518f5d41e3079f6b43373fe24f5 /chapter05 | |
| parent | 0bf1ea9287e37205420476c4c06af9c41a435e65 (diff) | |
Small grammar adjustments.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2812 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05')
| -rw-r--r-- | chapter05/lockingglibc.xml | 4 | ||||
| -rw-r--r-- | chapter05/whystatic.xml | 15 |
2 files changed, 10 insertions, 9 deletions
diff --git a/chapter05/lockingglibc.xml b/chapter05/lockingglibc.xml index a8bee36e8..7938df879 100644 --- a/chapter05/lockingglibc.xml +++ b/chapter05/lockingglibc.xml @@ -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 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 -explain more about this further on in this chapter. For now, run the +because of GCC's "fixincludes" process which runs as part of the GCC build. +We'll explain more about this further on in this chapter. For now, run the 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> diff --git a/chapter05/whystatic.xml b/chapter05/whystatic.xml index 86a550154..77e94e21e 100644 --- a/chapter05/whystatic.xml +++ b/chapter05/whystatic.xml @@ -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 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 -that, if you are pressed for time, you could skip the second passes over GCC -and Binutils, and just use the static versions to compile the rest of this -chapter and the first few packages in the next. As in the next chapter we -will be chrooted to the LFS partition and your host system's Glibc won't be -available, the programs from GCC and Binutils will need to be self-contained, -that is statically linked.</para> +independent from the libraries on your host system. The advantage is that, if +you are pressed for time, you could skip the second passes over GCC and +Binutils, and just use the static versions to compile the rest of this chapter +and the first few packages in the next. In the next chapter we will be +chrooted to the LFS partition and once inside the chroot environment, the host +system's Glibc won't be available, thus the programs from GCC and Binutils +will need to be self-contained, i.e. statically linked. However, we strongly +advise <emphasis>against</emphasis> skipping the second passes.</para> </sect1> |