Author: matthew Date: 2005-04-16 09:04:24 -0600 (Sat, 16 Apr 2005) New Revision: 4971
Modified: trunk/BOOK/chapter01/changelog.xml trunk/BOOK/chapter01/how.xml trunk/BOOK/general.ent Log: * Remove comments regarding statically linking the pass 1 toolchain Modified: trunk/BOOK/chapter01/changelog.xml =================================================================== --- trunk/BOOK/chapter01/changelog.xml 2005-04-15 22:37:29 UTC (rev 4970) +++ trunk/BOOK/chapter01/changelog.xml 2005-04-16 15:04:24 UTC (rev 4971) @@ -83,6 +83,10 @@ </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> Modified: trunk/BOOK/chapter01/how.xml =================================================================== --- trunk/BOOK/chapter01/how.xml 2005-04-15 22:37:29 UTC (rev 4970) +++ trunk/BOOK/chapter01/how.xml 2005-04-16 15:04:24 UTC (rev 4971) @@ -37,22 +37,18 @@ <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 Modified: trunk/BOOK/general.ent =================================================================== --- trunk/BOOK/general.ent 2005-04-15 22:37:29 UTC (rev 4970) +++ trunk/BOOK/general.ent 2005-04-16 15:04:24 UTC (rev 4971) @@ -1,6 +1,6 @@ <?xml version="1.0" encoding="ISO-8859-1"?> -<!ENTITY version "SVN-20050415"> -<!ENTITY releasedate "April 15, 2005"> +<!ENTITY version "SVN-20050416"> +<!ENTITY releasedate "April 16, 2005"> <!ENTITY milestone "6.2"> <!ENTITY lfs-root "http://www.linuxfromscratch.org/";> -- http://linuxfromscratch.org/mailman/listinfo/lfs-book FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
