diff options
author | Matthew Burgess <matthew@linuxfromscratch.org> | 2005-04-16 15:04:24 +0000 |
---|---|---|
committer | Matthew Burgess <matthew@linuxfromscratch.org> | 2005-04-16 15:04:24 +0000 |
commit | 8710bebc62b30794038283392d68bd14e60b9ba3 (patch) | |
tree | 3767dc9dbba922b7efb7f091f58fdad13d1d3016 /chapter01 | |
parent | 7b04736f195c48243d2923def0e4b88b1920d374 (diff) |
* Remove comments regarding statically linking the pass 1 toolchain
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@4971 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter01')
-rw-r--r-- | chapter01/changelog.xml | 4 | ||||
-rw-r--r-- | chapter01/how.xml | 22 |
2 files changed, 13 insertions, 13 deletions
diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml index 8d372da48..3916f284c 100644 --- a/chapter01/changelog.xml +++ b/chapter01/changelog.xml @@ -83,6 +83,10 @@ first a summary, then a detailed log.</para> </itemizedlist> </listitem> +<listitem><para>April 16, 2005 [matt]: Removed references to statically linking +the pass 1 toolchain which should have gone as part of bug 1061 (Andrew Benton) +</para></listitem> + <listitem><para>April 15, 2005 [jim]: Updated to udev 057.</para></listitem> <listitem><para>April 15, 2005 [jim]: Updated to file to 4.13.</para></listitem> diff --git a/chapter01/how.xml b/chapter01/how.xml index b2390fb48..2654ce7d3 100644 --- a/chapter01/how.xml +++ b/chapter01/how.xml @@ -37,22 +37,18 @@ to compile a compiler, you need a compiler.</para> <para><xref linkend="chapter-temporary-tools"/> also shows the user how to build a first pass of the toolchain, including Binutils and GCC (first pass basically means these two core packages will be -re-installed a second time). The programs from these packages will be -linked statically in order to be used independently of the host -system. The next step is to build Glibc, the C library. Glibc will be -compiled by the toolchain programs built in the first pass. Then, a -second pass of the toolchain will be built. This time, the toolchain -will be dynamically linked against the newly built Glibc. The -remaining <xref linkend="chapter-temporary-tools"/> packages are built -using this second pass toolchain. When this is done, the LFS -installation process will no longer depend on the host distribution, -with the exception of the running kernel.</para> +re-installed a second time). The next step is to build Glibc, the C library. +Glibc will be compiled by the toolchain programs built in the first pass. Then, +a second pass of the toolchain will be built. This time, the toolchain will be +dynamically linked against the newly built Glibc. The remaining +<xref linkend="chapter-temporary-tools"/> packages are built using this second +pass toolchain. When this is done, the LFS installation process will no longer +depend on the host distribution, with the exception of the running kernel. +</para> <para>While this may initially seem like a lot of work to get away from a host distribution, a full technical explanation is provided at -the beginning of <xref linkend="chapter-temporary-tools"/>, -including notes on the differences between -statically and dynamically-linked programs.</para> +the beginning of <xref linkend="chapter-temporary-tools"/>.</para> <para>In <xref linkend="chapter-building-system"/>, the full LFS system is built. The chroot (change root) program is used to enter a virtual |