Changeset bc2e3fa for BOOK/final-preps


Ignore:
Timestamp:
Dec 7, 2006, 11:23:24 PM (17 years ago)
Author:
Jim Gifford <clfs@…>
Branches:
clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit
Children:
1e184e11
Parents:
8473983
Message:

Reverting of Sysroot Changes

Location:
BOOK/final-preps
Files:
1 added
3 edited

Legend:

Unmodified
Added
Removed

  • BOOK/final-preps/chapter.xml

    r8473983 rbc2e3fa  
    1414  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="aboutclfs.xml"/>
    1515  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="creatingtoolsdir.xml"/>
     16  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="creatingcrossdir.xml"/>
    1617  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="addinguser.xml"/>
    1718  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="settingenviron.xml"/>

  • BOOK/final-preps/creatingtoolsdir.xml

    r8473983 rbc2e3fa  
    99  <?dbhtml filename="creatingtoolsdir.html"?>
    1010
    11   <title>Creating the temporary tools directories</title>
     11  <title>Creating the ${CLFS}/tools Directory</title>
    1212
    13   <para>The cross-binutils and cross-compiler built in
    14   <xref linkend="chapter-cross-tools"/> will be installed under
    15   <filename class="directory">${CLFS}/cross-tools</filename> to keep them
    16   separate from the host programs. The programs compiled here are
    17   cross-tools and will not be a part of the final CLFS system or the
    18   temp-system. Similarly, all programs compiled in
    19   <xref linkend="chapter-temp-system"/> will be installed under
    20   <filename class="directory">${CLFS}/tools</filename> to keep them separate
    21   from the programs compiled in <xref linkend="chapter-building-system"/>.
    22   This also prevents these programs from ending up in the host production
    23   directories (easy to do by accident in <xref linkend="chapter-temp-system"/>).
    24   By keeping the cross-compile tools and temporary-system programs in separate
    25   directories, they can easily be discarded later after their use.</para>
     13  <para>All programs compiled in <xref linkend="chapter-temp-system"/>
     14  will be installed under <filename class="directory">${CLFS}/tools</filename>
     15  to keep them separate from the programs compiled in <xref
     16  linkend="chapter-building-system"/>. The programs compiled here are
     17  temporary tools and will not be a part of the final CLFS system. By keeping
     18  these programs in a separate directory, they can easily be discarded later
     19  after their use. This also prevents these programs from ending up in the
     20  host production directories (easy to do by accident in <xref
     21  linkend="chapter-temp-system"/>).</para>
    2622
    27   <para>Create the required directories by running the following as
     23  <para>Create the required directory by running the following as
    2824  <systemitem class="username">root</systemitem>:</para>
    2925
    30 <screen><userinput>install -dv ${CLFS}/{tools,cross-tools}</userinput></screen>
     26<screen><userinput>install -dv ${CLFS}/tools</userinput></screen>
     27
     28  <para>The next step is to create a <filename class="symlink">/tools</filename>
     29  symlink on the host system. This will point to the newly-created directory
     30  on the CLFS partition. Run this command as <systemitem
     31  class="username">root</systemitem> as well:</para>
     32
     33<screen><userinput>ln -sv ${CLFS}/tools /</userinput></screen>
     34
     35  <note>
     36    <para>The above command is correct. The <command>ln</command> command
     37    has a few syntactic variations, so be sure to check <command>info
     38    coreutils ln</command> and <filename>ln(1)</filename> before reporting
     39    what you may think is an error.</para>
     40  </note>
     41
     42  <para>The created symlink enables the toolchain to be compiled so that
     43  it always refers to <filename class="directory">/tools</filename>,
     44  meaning that the compiler, assembler, and linker will work. This will
     45  provide a common place for our temporary tools system.</para>
    3146
    3247</sect1>

  • BOOK/final-preps/settingenviron.xml

    r8473983 rbc2e3fa  
    4444CLFS=/mnt/clfs
    4545LC_ALL=POSIX
    46 PATH=${CLFS}/cross-tools/bin:/bin:/usr/bin
     46PATH=/cross-tools/bin:/bin:/usr/bin
    4747export CLFS LC_ALL PATH</literal>
    4848EOF</userinput></screen>
    … …  
    5656  the shell will always search the <envar>PATH</envar> when a program is to
    5757  be run. As such, the shell will find the newly compiled tools in
    58   <filename class="directory">${CLFS}/cross-tools</filename> as soon as they are
     58  <filename class="directory">/cross-tools</filename> as soon as they are
    5959  available without remembering a previous version of the same program in a
    6060  different location.</para>
    … …  
    7979  the chroot environment.</para>
    8080
    81   <para os="j">By putting <filename class="directory">${CLFS}/cross-tools/bin</filename>
     81  <para os="j">By putting <filename class="directory">/cross-tools/bin</filename>
    8282  at the beginning of the <envar>PATH</envar>, the cross-compiler
    8383  built in <xref linkend="chapter-cross-tools"/> will be picked up by
    … …  
    8585  may be installed on the host. This, combined with turning off
    8686  hashing, helps to ensure that you will be using the cross-compile
    87   tools to build the temp-system in ${CLFS}/tools.</para>
     87  tools to build the temp-system in /tools.</para>
    8888
    8989  <para os="k">Finally, to have the environment fully prepared for building the
Note: See TracChangeset for help on using the changeset viewer.