10.0
10.0-rc1
10.1
10.1-rc1
11.0
11.0-rc1
11.0-rc2
11.0-rc3
11.1
11.1-rc1
11.2
11.2-rc1
11.3
11.3-rc1
12.0
12.0-rc1
12.1
12.1-rc1
12.2
12.2-rc1
6.0
6.1
6.1.1
6.3
6.4
6.5
6.6
6.7
6.8
7.0
7.1
7.2
7.3
7.4
7.5
7.5-systemd
7.6
7.6-systemd
7.7
7.7-systemd
7.8
7.8-systemd
7.9
7.9-systemd
8.0
8.1
8.2
8.3
8.4
9.0
9.1
arm
bdubbs/gcc13
ml-11.0
multilib
renodr/libudev-from-systemd
s6-init
trunk
v5_0
v5_1
v5_1_1
xry111/arm64
xry111/arm64-12.0
xry111/clfs-ng
xry111/lfs-next
xry111/loongarch
xry111/loongarch-12.0
xry111/loongarch-12.1
xry111/loongarch-12.2
xry111/mips64el
xry111/multilib
xry111/pip3
xry111/rust-wip-20221008
xry111/update-glibc
Rev | Line | |
---|
[148bb04] | 1 | <sect1 id="ch05-creatingtoolsdir">
|
---|
| 2 | <title>Creating the $LFS/tools directory</title>
|
---|
| 3 | <?dbhtml filename="creatingtoolsdir.html" dir="chapter05"?>
|
---|
[bc82645e] | 4 |
|
---|
| 5 | <para>All programs compiled in this chapter will be installed under <filename
|
---|
[148bb04] | 6 | class="directory">$LFS/tools</filename> to keep them separate from the
|
---|
[bc82645e] | 7 | programs compiled in the next chapter. The programs compiled here are only
|
---|
| 8 | temporary tools and won't be a part of the final LFS system and by keeping them
|
---|
[148bb04] | 9 | in a separate directory, we can later easily throw them away.</para>
|
---|
[bc82645e] | 10 |
|
---|
[148bb04] | 11 | <para>If later you wish to search through the binaries of your system to see
|
---|
| 12 | what files they make use of or link against, then to make this searching easier
|
---|
| 13 | you may want to choose a unique name. Instead of the simple "tools" you could
|
---|
| 14 | use something like "tools-for-lfs".</para>
|
---|
[bc82645e] | 15 |
|
---|
[148bb04] | 16 | <para>Create the required directory by running the following:</para>
|
---|
| 17 |
|
---|
| 18 | <para><screen><userinput>mkdir $LFS/tools</userinput></screen></para>
|
---|
| 19 |
|
---|
| 20 | <para>The next step is to create a <filename>/tools</filename> symlink on
|
---|
[66e4325] | 21 | your host system. It will point to the directory we just created on the LFS
|
---|
| 22 | partition:</para>
|
---|
[bc82645e] | 23 |
|
---|
[148bb04] | 24 | <para><screen><userinput>ln -s $LFS/tools /</userinput></screen></para>
|
---|
[bc82645e] | 25 |
|
---|
[66e4325] | 26 | <para>This symlink enables us to compile our toolchain so that it always
|
---|
[148bb04] | 27 | refers to <filename>/tools</filename>, meaning that the compiler, assembler
|
---|
[503e1a6] | 28 | and linker will work both in this chapter (when we are still using some tools
|
---|
| 29 | from the host) <emphasis>and</emphasis> in the next (when we are chrooted to
|
---|
[66e4325] | 30 | the LFS partition).</para>
|
---|
[bc82645e] | 31 |
|
---|
| 32 | </sect1>
|
---|
| 33 |
|
---|
Note:
See
TracBrowser
for help on using the repository browser.