| 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
|---|
| 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
|---|
| 3 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
|---|
| 4 | %general-entities;
|
|---|
| 5 | ]>
|
|---|
| 6 | <sect1 id="ch-tools-creatingtoolsdir">
|
|---|
| 7 | <title>Creating the $LFS/tools Directory</title>
|
|---|
| 8 | <?dbhtml filename="creatingtoolsdir.html"?>
|
|---|
| 9 |
|
|---|
| 10 | <para>All programs compiled in <xref
|
|---|
| 11 | linkend="chapter-temporary-tools"/> will be installed under <filename
|
|---|
| 12 | class="directory">$LFS/tools</filename> to keep them separate from the
|
|---|
| 13 | programs compiled in <xref linkend="chapter-building-system"/>. The
|
|---|
| 14 | programs compiled here are temporary tools and will not be a part of
|
|---|
| 15 | the final LFS system. By keeping these programs in a separate
|
|---|
| 16 | directory, they can easily be discarded later after their use. This
|
|---|
| 17 | also prevents these programs from ending up in the host production
|
|---|
| 18 | directories (easy to do by accident in <xref
|
|---|
| 19 | linkend="chapter-temporary-tools"/>).</para>
|
|---|
| 20 |
|
|---|
| 21 | <para>Create the required directory by running the following as
|
|---|
| 22 | <emphasis>root</emphasis>:</para>
|
|---|
| 23 |
|
|---|
| 24 | <screen><userinput>mkdir -v $LFS/tools</userinput></screen>
|
|---|
| 25 |
|
|---|
| 26 | <para>The next step is to create a <filename class="symlink">/tools</filename>
|
|---|
| 27 | symlink on the host system. This will point to the newly-created directory on
|
|---|
| 28 | the LFS partition. Run this command as <emphasis>root</emphasis> as
|
|---|
| 29 | well:</para>
|
|---|
| 30 |
|
|---|
| 31 | <screen><userinput>ln -sv $LFS/tools /</userinput></screen>
|
|---|
| 32 |
|
|---|
| 33 | <note><para>The above command is correct. The <command>ln</command> command has
|
|---|
| 34 | a few syntactic variations, so be sure to check <command>info coreutils ln</command> and
|
|---|
| 35 | <filename>ln(1)</filename> before reporting what you may think is an
|
|---|
| 36 | error.</para></note>
|
|---|
| 37 |
|
|---|
| 38 | <para>The created symlink enables the toolchain to be compiled so that
|
|---|
| 39 | it always refers to <filename class="directory">/tools</filename>,
|
|---|
| 40 | meaning that the compiler, assembler, and linker will work both in
|
|---|
| 41 | this chapter (when we are still using some tools from the host) and in
|
|---|
| 42 | the next (when we are <quote>chrooted</quote> to the LFS
|
|---|
| 43 | partition).</para>
|
|---|
| 44 |
|
|---|
| 45 | </sect1>
|
|---|
| 46 |
|
|---|
