Changeset 9531391
- Timestamp:
- Feb 21, 2006, 1:36:57 AM (19 years ago)
- Children:
- 29dec28
- Parents:
- 87ead03
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
final-preps/addinguser.xml
r87ead03 r9531391 79 79 80 80 <para>Grant <systemitem class="username">lfs</systemitem> full access to 81 <filename class="directory">$LFS</filename> and <filename 82 class="directory">$LFS/tools</filename> by making <systemitem 81 <filename class="directory">$LFS</filename>, 82 <filename class="directory">$LFS/cross-tools</filename>, 83 and <filename class="directory">$LFS/tools</filename> by making <systemitem 83 84 class="username">lfs</systemitem> the directories owner:</para> 84 85 85 86 <screen><userinput>chown lfs $LFS 86 chown lfs $LFS/tools</userinput></screen> 87 chown lfs $LFS/tools 88 chown lfs $LFS/cross-tools</userinput></screen> 87 89 88 90 <para>If a separate working directory was created as suggested, we will -
final-preps/creatingcrossdir.xml
r87ead03 r9531391 9 9 <?dbhtml filename="creatingcrossdir.html"?> 10 10 11 <title>Creating the $ HOME/cross-tools Directory</title>11 <title>Creating the $LFS/cross-tools Directory</title> 12 12 13 13 <para>All programs compiled in <xref linkend="chapter-cross-tools"/> will 14 be installed under <filename class="directory">$ HOME/cross-tools</filename>14 be installed under <filename class="directory">$LFS/cross-tools</filename> 15 15 to keep them separate from the host programs. The programs compiled here are 16 16 cross tools and will not be a part of the final LFS system. By keeping these … … 21 21 the <systemitem class="username">lfs</systemitem> user:</para> 22 22 23 <screen><userinput>install -d $ HOME/cross-tools</userinput></screen>23 <screen><userinput>install -d $LFS/cross-tools</userinput></screen> 24 24 25 25 <para>The next step is to create a <filename … … 30 30 <systemitem class="username">root</systemitem>:</para> 31 31 32 <screen><userinput>exit 33 LFSHOME=`echo ~lfs` 34 ln -s $LFSHOME/cross-tools / 35 unset LFSHOME 36 su - lfs</userinput></screen> 32 <screen><userinput>ln -s $LFS/cross-tools /</userinput></screen> 37 33 38 <para>TO BE REWRITTEN - The created symlink enables the toolchain to be 39 compiled so that 34 <para>The created symlink enables the toolchain to be compiled so that 40 35 it always refers to <filename class="directory">/cross-tools</filename>, 41 meaning that the compiler, assembler, and linker will work both in 42 this chapter and this host architecture and in the next (when we are 43 <quote>chrooted</quote> to the LFS partition).</para> 36 meaning that the compiler, assembler, and linker will be avaialble for 37 use later if some unforseen circumstances happen.</para> 44 38 45 39 </sect1> -
final-preps/creatingtoolsdir.xml
r87ead03 r9531391 40 40 </note> 41 41 42 <para>TO BE REWRiTTEN - The created symlink enables the toolchain to be 43 compiled so that 42 <para>The created symlink enables the toolchain to be compiled so that 44 43 it always refers to <filename class="directory">/tools</filename>, 45 meaning that the compiler, assembler, and linker will work both in 46 this chapter (when we are still using some tools from the host) and in 47 the next (when we are <quote>chrooted</quote> to the LFS 48 partition).</para> 44 meaning that the compiler, assembler, and linker will work. This will 45 provide a common place for our temporary tools system.</para> 49 46 50 47 </sect1> -
introduction/common/changelog.xml
r87ead03 r9531391 53 53 correct the date in changelog.</para> 54 54 </listitem> 55 <listitem> 56 <para>[jim] - Moved Cross-tools from $HOME to LFS. This provide a easy way 57 for livecd builders to not loose valueable build time, if something goes 58 wrong.</para> 59 </listitem> 55 60 </itemizedlist> 56 61 </listitem>
Note:
See TracChangeset
for help on using the changeset viewer.