Changeset b0dbcb6
- Timestamp:
- May 16, 2006, 8:14:55 PM (18 years ago)
- Branches:
- clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit
- Children:
- 802056d
- Parents:
- 576a66b
- Location:
- BOOK/final-preps
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
BOOK/final-preps/aboutlfs.xml
r576a66b rb0dbcb6 13 13 <para>Throughout this book, the environment variable <envar>LFS</envar> will 14 14 be used several times. It is paramount that this variable is always defined. 15 It should be set to the mount point chosen for the LFS partition.15 It should be set to the mount point chosen for the CLFS partition. 16 16 Check that the <envar>LFS</envar> variable is set up properly with:</para> 17 17 18 18 <screen><userinput>echo $LFS</userinput></screen> 19 19 20 <para>Make sure the output shows the path to the LFS partition's mount20 <para>Make sure the output shows the path to the CLFS partition's mount 21 21 point, which is <filename class="directory">/mnt/lfs</filename> if the 22 22 provided example was followed. If the output is incorrect, the -
BOOK/final-preps/creatingcrossdir.xml
r576a66b rb0dbcb6 11 11 <title>Creating the $LFS/cross-tools Directory</title> 12 12 13 <para>All programs compiled in <xref linkend="chapter-cross-tools"/> will 14 be installed under <filename class="directory">$LFS/cross-tools</filename> 15 to keep them separate from the host programs. The programs compiled here are 16 cross tools and will not be a part of the final LFS system. By keeping these 17 programs in a separate directory, they can easily be discarded later after 18 their use.</para> 13 <para>The cross-binutils and cross-compiler built in 14 <xref linkend="chapter-cross-tools"/> will be installed under 15 <filename class="directory">$LFS/cross-tools</filename> to keep them 16 separate from the host prograrms. The programs compiled here are 17 cross-tools and will not be a part of the final CLFS system or the 18 temp-system. By keeping these programs in a separate directory, they 19 can easily be discarded later after their use.</para> 19 20 20 21 <para>Create the required directory by running the following as … … 25 26 <para>The next step is to create a <filename 26 27 class="symlink">/cross-tools</filename> symlink on the host system. 27 This will point to the newly-created directory on the LFS partition.28 This will point to the newly-created directory on the CLFS partition. 28 29 Run this command as <systemitem class="username">root</systemitem> as well:</para> 29 30 … … 33 34 instructions do assume its existence), but is there mainly for 34 35 consistency (because /tools is also symlinked to $LFS/tools) and to 35 s omewhat simplify the installation of the cross-compile tools.</para>36 simplify the installation of the cross-compile tools.</para> 36 37 37 38 </sect1> -
BOOK/final-preps/creatingtoolsdir.xml
r576a66b rb0dbcb6 15 15 to keep them separate from the programs compiled in <xref 16 16 linkend="chapter-building-system"/>. The programs compiled here are 17 temporary tools and will not be a part of the final LFS system. By keeping17 temporary tools and will not be a part of the final CLFS system. By keeping 18 18 these programs in a separate directory, they can easily be discarded later 19 19 after their use. This also prevents these programs from ending up in the
Note:
See TracChangeset
for help on using the changeset viewer.