Changeset 8f75224 for chapter04


Ignore:
Timestamp:
10/15/2003 10:39:23 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:
f2243a5
Parents:
e3a72b1
Message:

Putting tarballs and patches in $LFS/sources.

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter04/chapter04.xml

    re3a72b1 r8f75224  
    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/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>
     35works well is to use <filename>$LFS/sources</filename> as the place to store
     36the tarballs and patches, <emphasis>and</emphasis> as a working directory.
     37This way everything you need will be located on the LFS partition and available
     38during all stages of the building process.</para>
     39
     40<para>So you may want to execute, as <emphasis>root</emphasis>, the following
     41command before starting your download session:</para>
     42
     43<screen><userinput>mkdir $LFS/sources</userinput></screen>
     44
     45<para>And make this directory writable (and sticky) for your normal user -- as
     46you won't do the downloading as <emphasis>root</emphasis>, we guess:</para>
     47
     48<screen><userinput>chmod a+wt $LFS/sources</userinput></screen>
    4549
    4650<!--
Note: See TracChangeset for help on using the changeset viewer.