Changeset 617bacd


Ignore:
Timestamp:
10/07/2003 10:22:28 PM (21 years ago)
Author:
Alex Gronenwoud <alex@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
7acb4c3
Parents:
51c41b1
Message:

Small fish.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2937 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Files:
2 edited

Legend:

Unmodified
Added
Removed
  • chapter04/chapter04.xml

    r51c41b1 r617bacd  
    2828<ulink url="http://linuxfromscratch.org/lfs/print/"/> or try
    2929the alternative means of downloading given at
    30 <ulink url="http://linuxfromscratch.org/lfs/packages.html"/></para>
     30<ulink url="http://linuxfromscratch.org/lfs/packages.html"/>.</para>
    3131
    3232<para>You'll need to store all the downloaded packages and patches somewhere
    3333that is conveniently available throughout the entire build. You'll also need a
    3434working directory in which to unpack the sources and build them. A scheme that
    35 works well is to use <filename>$LFS/tools/src/packages</filename> for all the
    36 downloaded files and <filename>$LFS/tools/src</filename> for the working
    37 directory. In this way, everything will be on the LFS partition and always
    38 available.</para>
    39  
    40 <para>Ater each package installation you should normally delete the source and
    41 build directories (for cleanness sake and to save space),
    42 <emphasis>unless</emphasis> instructed to do otherwise.</para>
     35works well is to use <filename>$LFS/usr/src/packages</filename> for all the
     36downloaded files and <filename>$LFS/usr/src</filename> as the working
     37directory. In this way, everything will be on the LFS partition and available
     38during all stages of the building process.</para>
     39
     40<!--
     41<para>So you may want to execute the following command:</para>
     42
     43<para><screen><userinput>mkdir -p $LFS/usr/src/packages</userinput></screen></para>
     44-->
    4345
    4446<!--
  • chapter05/introduction.xml

    r51c41b1 r617bacd  
    3737packages still use the older standard, which is not really a problem.</para>
    3838
     39<para><emphasis>Unless</emphasis> told not to, you should normally delete the
     40source and build directories after installing each package -- for cleanness
     41sake and to save space.</para>
     42
    3943<para>Before continuing, make sure the LFS environment variable is set up
    4044properly by executing the following:</para>
Note: See TracChangeset for help on using the changeset viewer.