source: chapter05/introduction.xml@ a3f6e124

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.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/mips64el xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since a3f6e124 was 21ba4e3, checked in by Greg Schafer <greg@…>, 21 years ago

Internal markup reworking to fix the extraneous whitespace problem in the "tidy generated" web site pages. Essentially replace all ocurrences of <para><screen> with <screen> (and of course the matching closing tags).

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

  • Property mode set to 100644
File size: 2.5 KB
Line 
1<sect1 id="ch05-introduction">
2<title>Introduction</title>
3<?dbhtml filename="introduction.html" dir="chapter05"?>
4
5<para>In this chapter we will compile and install a minimal
6Linux system. This system will contain just enough tools to be able
7to start constructing the final LFS system in the next chapter.</para>
8
9<para>The building of this minimal system is done in two steps: first we
10build a brand-new and host-independent toolchain (compiler, assembler,
11linker and libraries), and then use this to build all the other essential
12tools.</para>
13
14<para>The files compiled in this chapter will be installed under the
15<filename class="directory">$LFS/tools</filename> directory
16to keep them separate from the files installed in the next chapter.
17Since the packages compiled here are merely temporary, we don't want
18them to pollute the soon-to-be LFS system.</para>
19
20<para>The key to learning what makes a Linux system work is to know
21what each package is used for and why the user or the system needs it.
22For this purpose a short summary of the content of each package is given
23before the actual installation instructions. For a short description of
24each program in a package, please refer to the corresponding section in
25<xref linkend="appendixa"/>.</para>
26
27<para>Several of the packages are patched before compilation, but only when
28the patch is needed to circumvent a problem. Often the patch is needed in
29both this and the next chapter, but sometimes in only one of them. Therefore,
30don't worry when instructions for a downloaded patch seem to be missing.</para>
31
32<para>During the installation of most packages you will
33see all kinds of compiler warnings scroll by on your screen. These are
34normal and can be safely ignored. They are just what they say they are:
35warnings -- mostly about deprecated, but not invalid, use of the C or C++
36syntax. It's just that C standards have changed rather often and some
37packages still use the older standard, which is not really a problem.</para>
38
39<para><emphasis>Unless</emphasis> told not to, you should normally delete the
40source and build directories after installing each package -- for cleanness
41sake and to save space.</para>
42
43<para>Before continuing, make sure the LFS environment variable is set up
44properly by executing the following:</para>
45
46<screen><userinput>echo $LFS</userinput></screen>
47
48<para>Make sure the output shows the path to your LFS partition's mount
49point, which is <filename class="directory">/mnt/lfs</filename> if you
50followed our example.</para>
51
52</sect1>
53
Note: See TracBrowser for help on using the repository browser.