diff options
| author | Alex Gronenwoud <alex@linuxfromscratch.org> | 2003-09-15 21:47:44 +0000 |
|---|---|---|
| committer | Alex Gronenwoud <alex@linuxfromscratch.org> | 2003-09-15 21:47:44 +0000 |
| commit | 1e163254645f9440f16ff2f5556c45bdd0050022 (patch) | |
| tree | aab93c3120918f7604b798923fd20ae74f3c597d /chapter01/how.xml | |
| parent | 6ebafb4dbc92f6119e68e4099db570ae9428d5aa (diff) | |
Correcting several typos and some inconsistencies.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2819 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter01/how.xml')
| -rw-r--r-- | chapter01/how.xml | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/chapter01/how.xml b/chapter01/how.xml index c6f0d3e1f..79d1bc869 100644 --- a/chapter01/how.xml +++ b/chapter01/how.xml @@ -16,7 +16,7 @@ partition and filesystem is where your new LFS system will be compiled and installed onto.</para> <para>Chapter 5 will then discuss the installation of a number of packages that -will form the basic development suite (or toolset) which is used to build the +will form the basic development suite (or tool-set) which is used to build the actual system in Chapter 6. Some of these packages are needed to resolve circular dependencies. For example, to compile a compiler you need a compiler.</para> @@ -31,7 +31,7 @@ pass.</para> <para>The third thing to do is build a second pass of the toolchain. This time the toolchain will be dynamically linked against the newly built Glibc. The remaining Chapter 5 packages are all built using this second pass toolchain and -dynamically linked against the new host independant Glibc. When this is done, +dynamically linked against the new host-independent Glibc. When this is done, the LFS installation process will no longer depend on the host distribution, with the exception of the running kernel. This is known as <quote>self contained</quote> and <quote>self hosted</quote>. There is a discussion of the @@ -50,9 +50,10 @@ the road (they have been well documented). The host's Glibc is usually an unknown quantity and can contain bugs or anything else we don't know about until it is too late. A well known issue is that statically linked binaries compiled on a Glibc-2.2.x based system that then contain calls to the -getpwuid() function crash when run on a glibc-2.3.x based system. You are +<emphasis>getpwuid()</emphasis> function crash when run on a Glibc-2.3.x based +system. You are about to build a Glibc-2.3.x based system. You do not want to build something -that is going to crash do you? Finally, the Glibc Autoconf tests produce +that is going to crash do you? Finally, the Glibc autoconf tests produce different results depending on whether an existing Glibc is found on the host distribution. This can lead to inconsistencies and encourages hacks and workarounds. With all these things in mind, you can see that the extra effort |