source: chapter05/introduction.xml@ fc5780a

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 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 xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/lfs-next xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/mips64el xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since fc5780a was 673b0d8, checked in by Matthew Burgess <matthew@…>, 20 years ago
  • Merged newxml into HEAD

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3435 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 3.2 KB
Line 
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-introduction">
7<title>Introduction</title>
8<?dbhtml filename="introduction.html"?>
9
10<para>In this chapter we will compile and install a minimal
11Linux system. This system will contain just enough tools to be able
12to start constructing the final LFS system in the next chapter and allow
13a working environment with a little more user convenience than a minimum
14environment.</para>
15
16<para>The building of this minimal system is done in two steps: first we
17build a brand-new and host-independent toolchain (compiler, assembler,
18linker, libraries, and a few useful utilities), and then use this to build all the other essential
19tools.</para>
20
21<para>The files compiled in this chapter will be installed under the
22<filename class="directory">$LFS/tools</filename> directory
23to keep them separate from the files installed in the next chapter and your host's production directories.
24Since the packages compiled here are merely temporary, we don't want
25them to pollute the soon-to-be LFS system.</para>
26
27<para>Before issuing the build instructions for a package, you are expected to
28have already unpacked it (explained shortly) as user <emphasis>lfs</emphasis>,
29and to have performed a <userinput>cd</userinput> into the created directory.
30The build instructions assume that you are using the <command>bash</command>
31shell.</para>
32
33<para>Several of the packages are patched before compilation, but only when
34the patch is needed to circumvent a problem. Often the patch is needed in
35both this and the next chapter, but sometimes in only one of them. Therefore,
36don't worry when instructions for a downloaded patch seem to be missing. Also,
37when applying a patch, you'll occasionally see warning messages about
38<emphasis>offset</emphasis> or <emphasis>fuzz</emphasis>. These warnings are
39nothing to worry about, as the patch was still successfully applied.</para>
40
41<para>During the compilation of most packages you will see many warnings
42scroll by on your screen. These are normal and can safely be ignored. They are
43just what they say they are: warnings -- mostly about deprecated, but not
44invalid, use of the C or C++ syntax. It's just that C standards have changed
45rather often and some packages still use the older standard, which is not
46really a problem.</para>
47
48<para>After installing each package you should delete its source and build
49directories, <emphasis>unless</emphasis> told otherwise. Deleting the sources
50saves space, but also prevents mis-configuration when the same package is
51reinstalled further on. Only for three packages you will need to keep the
52source and build directories around for a while, so their contents can be used
53by later commands. Do not miss the reminders.</para>
54
55<para>Now first check that your LFS environment variable is set up
56properly:</para>
57
58<screen><userinput>echo $LFS</userinput></screen>
59
60<para>Make sure the output shows the path to your LFS partition's mount
61point, which is <filename class="directory">/mnt/lfs</filename> if you
62followed our example.</para>
63
64</sect1>
Note: See TracBrowser for help on using the repository browser.