| 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
|---|
| 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/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 | <!--
|
|---|
| 11 | <para>All programs compiled in <xref 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 programs compiled here are only
|
|---|
| 14 | temporary tools and won't be a part of the final LFS system and by keeping them
|
|---|
| 15 | in a separate directory, we can later easily throw them away. This also
|
|---|
| 16 | helps prevent them from ending up in your host's production directories
|
|---|
| 17 | (easy to do in <xref linkend="chapter-temporary-tools"/>), which could be a very bad thing.</para>
|
|---|
| 18 |
|
|---|
| 19 | <para>Later on you might wish to search through the binaries of your system to
|
|---|
| 20 | see what files they make use of or link against. To make this searching easier
|
|---|
| 21 | you may want to choose a unique name for the directory in which the temporary
|
|---|
| 22 | tools are stored. Instead of the simple <quote>tools</quote> you could use
|
|---|
| 23 | something like <quote>tools-for-lfs</quote>. However, you'll need to be careful
|
|---|
| 24 | to adjust all references to <quote>tools</quote> throughout the book -
|
|---|
| 25 | including those in any patches, notably the GCC Specs Patch.</para>
|
|---|
| 26 |
|
|---|
| 27 | <para>Create the required directory by running the following:</para>
|
|---|
| 28 | -->
|
|---|
| 29 |
|
|---|
| 30 | <screen><userinput>mkdir $LFS/tools</userinput></screen>
|
|---|
| 31 |
|
|---|
| 32 | <!--
|
|---|
| 33 | <para>The next step is to create a <filename>/tools</filename> symlink on
|
|---|
| 34 | your <emphasis>host</emphasis> system. It will point to the directory we just created on the LFS
|
|---|
| 35 | partition:</para>
|
|---|
| 36 | -->
|
|---|
| 37 |
|
|---|
| 38 | <screen><userinput>ln -s $LFS/tools /</userinput></screen>
|
|---|
| 39 |
|
|---|
| 40 | <!--
|
|---|
| 41 | <note><para>The above command is correct. The <command>ln</command> command
|
|---|
| 42 | has a few syntactic variations, so be sure to check the info page before
|
|---|
| 43 | reporting what you may think is an error.</para></note>
|
|---|
| 44 |
|
|---|
| 45 | <para>The created symlink enables us to compile our toolchain so that it always
|
|---|
| 46 | refers to <filename class="directory">/tools</filename>, meaning that the compiler, assembler
|
|---|
| 47 | and linker will work both in this chapter (when we are still using some tools
|
|---|
| 48 | from the host) <emphasis>and</emphasis> in the next (when we are <quote>chrooted</quote> to
|
|---|
| 49 | the LFS partition).</para>
|
|---|
| 50 | -->
|
|---|
| 51 |
|
|---|
| 52 | </sect1>
|
|---|
