| 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
|---|
| 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
|
|---|
| 3 | "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
|---|
| 4 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
|---|
| 5 | %general-entities;
|
|---|
| 6 | ]>
|
|---|
| 7 |
|
|---|
| 8 | <sect1 id="ch-final-preps-creatingtoolsdir">
|
|---|
| 9 | <?dbhtml filename="creatingtoolsdir.html"?>
|
|---|
| 10 |
|
|---|
| 11 | <title>Creating the $CLFS/tools Directory</title>
|
|---|
| 12 |
|
|---|
| 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>
|
|---|
| 22 |
|
|---|
| 23 | <para>Create the required directory by running the following as
|
|---|
| 24 | <systemitem class="username">root</systemitem>:</para>
|
|---|
| 25 |
|
|---|
| 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>
|
|---|
| 46 |
|
|---|
| 47 | </sect1>
|
|---|
