Changeset 5756284
- Timestamp:
- 05/30/2002 11:43:04 PM (22 years ago)
- Branches:
- 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, v4_0, v4_1, 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
- Children:
- 0230a11
- Parents:
- f64f4b5
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/introduction.xml
rf64f4b5 r5756284 3 3 <?dbhtml filename="introduction.html" dir="chapter05"?> 4 4 5 <para>In the following chapters we will install all the software that belongs 6 to a basic Linux system. After you're done with this and the next chapter, 7 you'll have a fully working Linux system. The remaining chapters deal 8 with creating the boot scripts, making the LFS system bootable and 9 setting up basic networking.</para> 5 <para>In this chapter we will compile and install a minimal 6 Linux system. This system will contain just enough tools to be able 7 to start constructing the final LFS system in the next chapter.</para> 10 8 11 <para>The software in this chapter will be linked statically and will be 12 reinstalled in the next chapter and linked dynamically. The 13 reason for the static version first is that there is a chance that our 14 normal Linux system and the LFS system aren't using the same C 15 Library versions. If the programs in the first part are linked against 16 an older C library version, those programs might not work well on the 17 LFS system. Another reason is to resolve circular dependencies. An 18 example of such a dependency is that you need a compiler to install a 19 compiler, and you're going to need a shell to install a shell and that 20 compiler.</para> 9 <para>The software in this chapter will be linked statically, because 10 there is a possibility that your host Linux system uses a different 11 version of the C library than the version you downloaded for 12 use in your LFS system. If we were to link the programs in this 13 chapter against that older C library, these programs might work 14 incorrectly, or not at all, when we change to the LFS system.</para> 21 15 22 <para> All the files from this chapter will be installed under the <filename23 class="directory">$LFS/static</filename> directory. By doing it this way,24 we keep the installation from this chapter separate from the final 25 installation in the next chapter. Everything done here is only temporarily 26 so we don't want itto pollute the to-be LFS system.</para>16 <para>The files compiled in this chapter will be installed under the 17 <filename class="directory">$LFS/static</filename> directory, 18 to keep them separate from the files installed in the next chapter. 19 As everything done here is only temporarily, we don't want 20 these files to pollute the to-be LFS system.</para> 27 21 28 <para>The key to learning what makes Linux tick is to know exactly what packages29 are used for and why a user or the system needs them. Descriptions 30 of the package content are provided after the Installation subsectionof each31 package and in Appendix A as well.</para>22 <para>The key to learning what makes a Linux system work is to know 23 exactly what each package is used for, and why the user or the system 24 needs it. For this purpose a short description of the content of each 25 package is given right after the installation instructions.</para> 32 26 33 <para>During the installation of various packages, you will more than likely see34 all kinds of compiler warnings scrolling by on the screen. These are 35 normal and can be safely ignored. They are just that, warnings (mostly36 about improper use of the C or C++ syntax, but not illegal use. It's just 37 that, often, C standards changed and packages still use the old standard 38 which is not a problem).</para>27 <para>During the installation of several packages you will probably 28 see all kinds of compiler warnings scroll by on your screen. These are 29 normal and can be safely ignored. They are just what they say they are: 30 warnings -- mostly about improper, but not illegal, use of the C or C++ 31 syntax. It's just that C standards have changed rather often and some 32 packages still use the older standard, which is not really a problem.</para> 39 33 40 <para>Before westart, make sure the LFS environment variable is set up34 <para>Before you start, make sure the LFS environment variable is set up 41 35 properly if you decided to make use of it. Run the following:</para> 42 36 -
chapter06/introduction.xml
rf64f4b5 r5756284 2 2 <title>Introduction</title> 3 3 <?dbhtml filename="introduction.html" dir="chapter06"?> 4 5 <para>In this chapter we enter the building site, and start 6 constructing our LFS system in earnest. That is, we chroot into 7 our temporary mini Linux system, create some auxiliary things, 8 and then start installing all the packages, one by one.</para> 4 9 5 10 <para>The installation of all the software is pretty straightforward, and … … 11 16 possible confusion and errors.</para> 12 17 13 <para> Now would be a good time to take a look at the optimization hint14 at <ulink url="&hints-root;optimization.txt"/> if you plan to use15 compiler optimization for the packages 16 installed in this chapter.Compiler optimization can make a program run18 <para>If you plan to use compiler optimization for the packages 19 installed in this chapter, take a look at the optimization hint 20 at <ulink url="&hints-root;optimization.txt"/>. 21 Compiler optimization can make a program run 17 22 faster, but may also cause compilation problems. If you run into problems 18 23 when using optimization, always try it without optimization to see if
Note:
See TracChangeset
for help on using the changeset viewer.