Some more adjustments.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2923 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Alex Gronenwoud 2003-10-05 12:57:37 +00:00
parent 7da1bffa1e
commit c84ddd992c
6 changed files with 23 additions and 18 deletions

View File

@ -17,26 +17,29 @@ reason for not using the latest version due to known problems that haven't
been worked around yet.</para> been worked around yet.</para>
<para>All the URLs, when possible, refer to the project's page at <para>All the URLs, when possible, refer to the project's page at
<ulink url="http://www.freshmeat.net"/>. The Freshmeat <ulink url="http://www.freshmeat.net/"/>. The Freshmeat
pages will give you easy access to the official download sites as well as pages will give you easy access to the official download sites as well as
project websites, mailinglists, FAQs, Changelogs and more.</para> project websites, mailinglists, FAQs, Changelogs and more.</para>
<para>We can't guarantee that these download locations are always available <para>We can't guarantee that these download locations are always available
to you. In case a download location has changed since this book was to you. In case a download location has changed since this book was
published, please try to google for the package. Should you remain published, please try to google for the package. Should you remain
unsuccessful with this you should consult the book's errata page at unsuccessful with this, you can consult the book's errata page at
<ulink url="http://linuxfromscratch.org/lfs/print"/> or try <ulink url="http://linuxfromscratch.org/lfs/print/"/> or try
the alternative means of download listed at the alternative means of downloading given at
<ulink url="http://linuxfromscratch.org/lfs/packages.html"/></para> <ulink url="http://linuxfromscratch.org/lfs/packages.html"/></para>
<para>You'll need to store all the downloaded packages and patches somewhere <para>You'll need to store all the downloaded packages and patches somewhere
that is conveniently available throughout the entire build. You'll also need a that is conveniently available throughout the entire build. You'll also need a
working directory in which to unpack the sources and build them. A scheme that working directory in which to unpack the sources and build them. A scheme that
works well is to use $LFS/tools/src/packages for all the downloaded files and works well is to use <filename>$LFS/tools/src/packages</filename> for all the
$LFS/tools/src for the working directory. In this way, everything will be on the downloaded files and <filename>$LFS/tools/src</filename> for the working
LFS partition and always available. Normally, you should delete the source and directory. In this way, everything will be on the LFS partition and always
build directories after each package installation, unless instructed to do available.</para>
otherwise.</para>
<para>Ater each package installation you should normally delete the source and
build directories (for cleanness sake and to save space),
<emphasis>unless</emphasis> instructed to do otherwise.</para>
<!-- <!--
<para>For your convenience the top of the list contains a link to a file <para>For your convenience the top of the list contains a link to a file
@ -325,7 +328,9 @@ Zlib Vsnprintf Patch (&zlib-patch-version;) - &zlib-patch-size;:
<para>In addition, there are a number of optional patches that have been <para>In addition, there are a number of optional patches that have been
created by the LFS community. Most of these solve slight problems, or enable created by the LFS community. Most of these solve slight problems, or enable
some functionality that's not enabled by default. Please feel free to examine some functionality that's not enabled by default. Please feel free to examine
the patches database, located at <ulink url="http://www.linuxfromscratch.org/patches"/>, and choose any additional patches you might wish to use.</para> the patches database, located at
<ulink url="http://www.linuxfromscratch.org/patches/"/>, and choose any
additional patches you might wish to use.</para>
</sect1> </sect1>

View File

@ -30,8 +30,8 @@ from the host) <emphasis>and</emphasis> in the next (when we are chrooted to
the LFS partition).</para> the LFS partition).</para>
<note><para>Study the above command closely. It can be confusing at first <note><para>Study the above command closely. It can be confusing at first
glance. The <userinput>ln</userinput> command has several syntax variations so glance. The <userinput>ln</userinput> command has several syntax variations,
be sure to check the ln man page before reporting what you may think is an so be sure to check the ln man page before reporting what you may think is an
error.</para></note> error.</para></note>
</sect1> </sect1>

View File

@ -37,7 +37,7 @@ chose.</para>
<para>The LC_ALL variable controls the localization of certain programs, <para>The LC_ALL variable controls the localization of certain programs,
making their messages follow the conventions of a specified country. If your making their messages follow the conventions of a specified country. If your
host system uses a version of <emphasis>glibc</emphasis> older than 2.2.4, host system uses a version of Glibc older than 2.2.4,
having LC_ALL set to something other than "POSIX" or "C" during this chapter having LC_ALL set to something other than "POSIX" or "C" during this chapter
may cause trouble if you exit the chroot environment and wish to return later. may cause trouble if you exit the chroot environment and wish to return later.
By setting LC_ALL to "POSIX" (or "C", the two are equivalent) we ensure that By setting LC_ALL to "POSIX" (or "C", the two are equivalent) we ensure that

View File

@ -18,7 +18,7 @@ compilation problem with some packages:</para>
<para>This package has a test suite available which can perform a number of <para>This package has a test suite available which can perform a number of
checks to ensure it built correctly. Should you choose to run it, the checks to ensure it built correctly. Should you choose to run it, the
following command will do so:</para> following command will do so (and takes a long time):</para>
<para><screen><userinput>make check</userinput></screen></para> <para><screen><userinput>make check</userinput></screen></para>

View File

@ -13,7 +13,7 @@
<para>This package has a test suite available which can perform a number of <para>This package has a test suite available which can perform a number of
checks to ensure it built correctly. Should you choose to run it, the checks to ensure it built correctly. Should you choose to run it, the
following command will do so:</para> following command will do so (and takes a very long time):</para>
<para><screen><userinput>make check</userinput></screen></para> <para><screen><userinput>make check</userinput></screen></para>

View File

@ -3,9 +3,9 @@
<sect2> <sect2>
<title>Installation of Zlib</title> <title>Installation of Zlib</title>
<para>Zlib has a potential buffer overflow in its gzprintf() function, <para>Zlib has a potential buffer overflow in its
that, though difficult to take advantage of, should be taken care of. Do <emphasis>gzprintf()</emphasis> function, that, though difficult to take
so by applying this patch:</para> advantage of, should be taken care of by applying this patch:</para>
<para><screen><userinput>patch -Np1 -i ../zlib-&zlib-patch-version;.patch</userinput></screen></para> <para><screen><userinput>patch -Np1 -i ../zlib-&zlib-patch-version;.patch</userinput></screen></para>