gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-06 06:14:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

Small fish.

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2937 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Alex Gronenwoud 2003-10-07 22:22:28 +00:00
parent 51c41b193e
commit 617bacdc91
2 changed files with 15 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
chapter04/chapter04.xml
View File

@ -27,19 +27,21 @@ published, please try to google for the package. Should you remain
unsuccessful with this, you can 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 downloading given 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 <filename>$LFS/tools/src/packages</filename> for all the works well is to use <filename>$LFS/usr/src/packages</filename> for all the
downloaded files and <filename>$LFS/tools/src</filename> for the working downloaded files and <filename>$LFS/usr/src</filename> as the working
directory. In this way, everything will be on the LFS partition and always directory. In this way, everything will be on the LFS partition and available
available.</para> during all stages of the building process.</para>
<para>Ater each package installation you should normally delete the source and <!--
build directories (for cleanness sake and to save space), <para>So you may want to execute the following command:</para>
<emphasis>unless</emphasis> instructed to do otherwise.</para>
<para><screen><userinput>mkdir -p $LFS/usr/src/packages</userinput></screen></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

4
chapter05/introduction.xml
View File

@ -36,6 +36,10 @@ warnings -- mostly about deprecated, but not invalid, use of the C or C++
syntax. It's just that C standards have changed rather often and some syntax. It's just that C standards have changed rather often and some
packages still use the older standard, which is not really a problem.</para> packages still use the older standard, which is not really a problem.</para>
<para><emphasis>Unless</emphasis> told not to, you should normally delete the
source and build directories after installing each package -- for cleanness
sake and to save space.</para>
<para>Before continuing, make sure the LFS environment variable is set up <para>Before continuing, make sure the LFS environment variable is set up
properly by executing the following:</para> properly by executing the following:</para>