- Timestamp:
- 10/11/2003 12:02:35 PM (21 years ago)
- 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:
- f27835d
- Parents:
- 1668d8e
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter04/chapter04.xml
r1668d8e r313e0960 33 33 that is conveniently available throughout the entire build. You'll also need a 34 34 working directory in which to unpack the sources and build them. A scheme that 35 works well is to use <filename>$LFS/ usr/src/packages</filename> for allthe36 downloaded files and <filename>$LFS/usr/src</filename> as the working 37 directory. In this way, everything will be on the LFS partition and available 38 during all stages of the building process.</para> 39 40 <!-- 41 <para>So you may want to execute the following command :</para>42 43 <screen><userinput>mkdir -p $LFS/usr/src/packages</userinput></screen> 44 -->35 works well is to use <filename>$LFS/tools/sources/packages</filename> for the 36 tarballs, and <filename>$LFS/tools/sources</filename> as the working directory 37 <emphasis>and</emphasis> as the place to store the patches. In this way, 38 everything will be on the LFS partition and available during all stages of the 39 building process.</para> 40 41 <para>So you may want to execute the following command before starting 42 your download session:</para> 43 44 <screen><userinput>mkdir -p $LFS/tools/sources/packages</userinput></screen> 45 45 46 46 <!--
Note:
See TracChangeset
for help on using the changeset viewer.