clfs-1.2
clfs-2.1
clfs-3.0.0-systemd
clfs-3.0.0-sysvinit
systemd
sysvinit
Last change
on this file since 34f53b7 was 80605b0, checked in by Jim Gifford <clfs@…>, 19 years ago |
r3222@server (orig r1500): chris | 2006-05-01 14:32:20 -0700
Rewrote the description of why the /cross-tools symlink is created
|
-
Property mode
set to
100644
|
File size:
1.6 KB
|
Line | |
---|
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-creatingcrossdir">
|
---|
9 | <?dbhtml filename="creatingcrossdir.html"?>
|
---|
10 |
|
---|
11 | <title>Creating the $LFS/cross-tools Directory</title>
|
---|
12 |
|
---|
13 | <para>All programs compiled in <xref linkend="chapter-cross-tools"/> will
|
---|
14 | be installed under <filename class="directory">$LFS/cross-tools</filename>
|
---|
15 | to keep them separate from the host programs. The programs compiled here are
|
---|
16 | cross tools and will not be a part of the final LFS system. By keeping these
|
---|
17 | programs in a separate directory, they can easily be discarded later after
|
---|
18 | their use.</para>
|
---|
19 |
|
---|
20 | <para>Create the required directory by running the following as
|
---|
21 | <systemitem class="username">root</systemitem>:</para>
|
---|
22 |
|
---|
23 | <screen><userinput>install -dv $LFS/cross-tools</userinput></screen>
|
---|
24 |
|
---|
25 | <para>The next step is to create a <filename
|
---|
26 | class="symlink">/cross-tools</filename> symlink on the host system.
|
---|
27 | This will point to the newly-created directory on the LFS partition.
|
---|
28 | Run this command as <systemitem class="username">root</systemitem> as well:</para>
|
---|
29 |
|
---|
30 | <screen><userinput>ln -sv $LFS/cross-tools /</userinput></screen>
|
---|
31 |
|
---|
32 | <para>The symlink isn't technically necessary (though the book's
|
---|
33 | instructions do assume its existence), but is there mainly for
|
---|
34 | consistency (because /tools is also symlinked to $LFS/tools) and to
|
---|
35 | somewhat simplify the installation of the cross-compile tools.</para>
|
---|
36 |
|
---|
37 | </sect1>
|
---|
Note:
See
TracBrowser
for help on using the repository browser.