Changeset 72033583
- Timestamp:
- 03/18/2001 07:30:50 PM (23 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, 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, v3_0, v3_1, v3_2, v3_3, 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/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 137bd50
- Parents:
- ab8b352
- Files:
-
- 13 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/bash-exp.xml
rab8b352 r72033583 10 10 <userinput>--prefix=$LFS/usr:</userinput> This configure option installs 11 11 all of Bash's files under the $LFS/usr directory, which becomes the /usr 12 directory after you chroot into $LFS or when you reboot the system into LFS. 12 directory after the user chrooted into $LFS or when he rebooted 13 the system into LFS. 13 14 </para> 14 15 … … 16 17 <userinput>--bindir=$LFS/bin:</userinput> This installs the executable 17 18 files in $LFS/bin. We do this because we want bash to be in /bin, not in 18 /usr/bin. One reason being: your/usr partition might be on a seperate19 /usr/bin. One reason being: the /usr partition might be on a seperate 19 20 partition which has to be mounted at some point. Before that partition is 20 mounted you needand will want to have bash available (it will be hard to21 mounted a user needs and will want to have bash available (it will be hard to 21 22 execute the boot scripts without a shell for instance). 22 23 </para> … … 45 46 The <userinput>&&</userinput>'s at the end of every line cause 46 47 the next command only to be executed when the previous command exists 47 with a return value of 0 indicating success. In case you copy&paste 48 all of these commands on the shell you want to be ensured that if 48 with a return value of 0 indicating success. In case all of these 49 commands are copy&pasted 50 on the shell is is important to be ensured that if 49 51 ./configure fails, make isn't being executed and likewise if make fails 50 52 that make install isn't being executed, and so forth. -
chapter05/bash-inst.xml
rab8b352 r72033583 19 19 20 20 <para> 21 If you get errors when compiling bash that tell youabout not being able to22 find <quote>-lcurses</quote> run these two commandsto create the21 If a user gets errors when compiling bash that tell about not being able to 22 find <quote>-lcurses</quote> these two commands should be run to create the 23 23 missing symlink (so far we have not enountered one distribution that has 24 24 this libncurses symlink setup properly, except for LFS systems where it … … 35 35 <para> 36 36 Note: Normally the libncurses.a file resides in the /usr/lib directory 37 but it might reside in /lib (like it does on LFS systems). So check to 38 make sure whether you should run the ln command in /usr/lib or in /lib 37 but it might reside in /lib (like it does on LFS systems). A user needs 38 to check to 39 make sure whether the ln command has to be run in /usr/lib or in /lib. 39 40 </para> 40 41 -
chapter05/binutils-exp.xml
rab8b352 r72033583 19 19 $(exec_prefix)/$(target_alias) which expands into, for example, 20 20 /usr/i686-pc-linux-gnu. Since we only build for our own system we don't 21 need this target specific directory in $LFS/usr. You would use that22 setup if you use your system to cross-compile (for example you would 23 compil e a package on yourIntel machine that generates code that can be21 need this target specific directory in $LFS/usr. That setup would be used 22 if the system is used to cross-compile (for example 23 compiling a package on the Intel machine that generates code that can be 24 24 executed on Apple PowerPC machines). 25 25 </para> -
chapter05/bzip2-exp.xml
rab8b352 r72033583 13 13 is the last parameter of the sed command which indicates the file to 14 14 search and replace in. sed normally sends the modified file to stdout 15 (standard output) which will be yourconsole. With the construction we15 (standard output) which will be the console. With the construction we 16 16 use, sed's output will be piped to the make program. Normally when make 17 17 is started it tries to find a number of files like Makefile. But we have … … 25 25 <para> 26 26 <userinput>LDFLAGS=-static:</userinput> This is the second way we use to 27 link a package statically. This is also the most common way. As you'll28 notice, the -all-static value is only used with the binutils package and27 link a package statically. This is also the most common way. 28 The -all-static value is only used with the binutils package and 29 29 won't be used throughout the rest of this book. 30 30 </para> -
chapter05/gcc-exp.xml
rab8b352 r72033583 5 5 <userinput>--enable-languages=c,c++:</userinput> This only builds the C 6 6 and C++ compilers and not the other available compilers as they are, on 7 the average, not often used. If you do need those other compilers don't8 use the --enable-languages parameter.7 the average, not often used. If those other compilers are needed 8 the --enable-languages parameter can be omitted.. 9 9 </para> 10 10 -
chapter05/gcc-inst.xml
rab8b352 r72033583 3 3 4 4 <para> 5 After you unpacked the gcc-2.95.2.1 archive don't enter the newly created 6 gcc-2.95.2.1 directory but stay in the $LFS/usr/src directory. Install GCC by 5 After the gcc-2.95.2.1 archive was unpacked, the newly created 6 gcc-2.95.2.1 directory is not entered. The user should stay in the 7 $LFS/usr/src directory. GCC is installed by 7 8 running the following commands: 8 9 </para> -
chapter05/gzip-inst.xml
rab8b352 r72033583 3 3 4 4 <para> 5 Before you install Gzip you have to unpack the gzip patch file.5 Before Gzip is installed the the gzip patch file needs to be unpacked. 6 6 </para> 7 7 -
chapter05/installasroot.xml
rab8b352 r72033583 3 3 4 4 <para> 5 It's best if you login as root or suto root when installing these6 files. That way you areassured that all files are owned by user root,7 group root (and not owned by the userid of yournon-root user) and if a5 It's best if the user logins as root or su's to root when installing these 6 files. That way he is assured that all files are owned by user root, 7 group root (and not owned by the userid of the non-root user) and if a 8 8 package wants to set special permissions it can do so without problems 9 9 due to non-root access. … … 11 11 12 12 <para> 13 If you read the documentation that comes with Glibc, Gcc and other14 packages theyrecommend not to compile the packages as user root. We13 The documentation that comes with Glibc, Gcc and other 14 packages recommend not to compile the packages as user root. We 15 15 feel it's safe to ignore that recommendation and compile as user root 16 16 anyways. Hundreds of people using LFS have done so without any problems 17 17 whatsoever and we haven't encountered any bugs in the compile processes 18 18 that cause harm. So it's pretty safe (never can be 100% safe though, so 19 it's up to you what you endup doing).19 it's up to the user what he ends up doing). 20 20 </para> 21 21 -
chapter05/introduction.xml
rab8b352 r72033583 4 4 <para> 5 5 In the following chapters we will install all the software that belongs to 6 a basic Linux system. After you're done with this chapter you havea6 a basic Linux system. After a user is done with this chapter he has a 7 7 fully working Linux system. The remaining chapters deal with setting up 8 8 networking, creating the boot scripts and adding an entry to lilo.conf so 9 that you can boot your LFS system.9 that the LFS system can be booted. 10 10 </para> 11 11 … … 14 14 will be re-installed in the next chapter and linked dynamically. The 15 15 reason for the static version first is that there is a chance that our 16 normal Linux system and yourLFS system aren't using the same C16 normal Linux system and the LFS system aren't using the same C 17 17 Library versions. If the programs in the first part are linked against 18 18 an older C library version, those programs might not work well on the … … 22 22 <para> 23 23 The key to learn what makes Linux tick is to know exactly what packages 24 are used for and why youor the system needs them. Descriptions24 are used for and why a user or the system needs them. Descriptions 25 25 of the package content are provided after the Installation subsection of each 26 26 package and in Appendix A as well. … … 33 33 34 34 <para> 35 During the installation of various packages youwill most likely see36 compiler warnings scrolling by on yourscreen. These are normal and can35 During the installation of various packages the user will most likely see 36 compiler warnings scrolling by on the screen. These are normal and can 37 37 be safely ignored. They are just that, warnings (mostly about improper 38 38 use of the C or C++ syntax, but not illegal use. It's just that often C … … 42 42 43 43 <para> 44 Before we start, make sure you have the LFS environment variable setup 45 if you plan on using it, by running the following command: 44 Before we start, it should be made sure the LFS environment variable was 45 setup 46 if it was planned to be used, by running the following command: 46 47 </para> 47 48 -
preface/organpart1.xml
rab8b352 r72033583 3 3 4 4 <para> 5 Part One gives yougeneral information about this book (versions, where5 Part One gives general information about this book (versions, where 6 6 to get it, changelog, mailing lists, and how to get in touch with me). 7 It also explains a few important aspects you really want and needto8 read before you start buildingan LFS system.7 It also explains a few important aspects a user really wants and needs to 8 read before starting to build an LFS system. 9 9 </para> 10 10 -
preface/organpart2.xml
rab8b352 r72033583 3 3 4 4 <para> 5 Part Two guides youthrough the installation of the LFS system which will6 be the foundation for the rest of the system. Whatever you7 choose to do with yourbrand new LFS system, it will be built on the5 Part Two guides through the installation of the LFS system which will 6 be the foundation for the rest of the system. Whatever a user 7 chooses to do with his brand new LFS system, it will be built on the 8 8 foundation that's installed in this part. 9 9 </para> -
preface/whonotread.xml
rab8b352 r72033583 4 4 <para> 5 5 Users who don't want to build an entire Linux system from scratch 6 probably don't want to read this book. If you, however, do wantto learn6 probably don't want to read this book. If a user, however, wants to learn 7 7 more about what happens behind the scenes, in particular what happens 8 between turning on your computer and seeing the command prompt, you want8 between turning on the computer and seeing the command prompt, he wants 9 9 to read the <quote>From Power Up To Bash Prompt</quote> (P2B) HOWTO. 10 10 This HOWTO builds a bare system, in way similar to the one this book … … 14 14 15 15 <para> 16 To decide whether you want to read this book or the P2B HOWTO, youcould17 ask yourself this question: "Is my main objective to get a working Linux16 To decide whether to read this book or the P2B HOWTO, a user could 17 ask himself this question: "Is my main objective to get a working Linux 18 18 system that I'm going to build myself and, along the way, learn what 19 19 every component of a system is for, or is just the learning part my main 20 objective?" If you want to build and learn, read this book. If youjust21 want to learn, then the P2B HOWTO is probably better material to read.20 objective?" If he wants to build and learn, he reads this book. If he just 21 wants to learn, then the P2B HOWTO is probably better material to read. 22 22 </para> 23 23 -
preface/whoread.xml
rab8b352 r72033583 5 5 This book is intended for Linux users who want to setup their own 6 6 custom-built Linux system. Reasons for wanting to build such a system are 7 diverse. Perhaps you wantto get into more detail as to what8 happens behind the scenes. Perhaps you arefed up with distributions9 which are often bloated or perhaps you don't want to rely on pre-compiled10 binaries due to security concerns. There are many reasons why you may want11 a custom-built system, but if you areone of them, this book is meant12 for you.7 diverse. Perhaps a user wants to get into more detail as to what 8 happens behind the scenes. Perhaps he is fed up with distributions 9 which are often bloated or perhaps he doesn't want to rely on pre-compiled 10 binaries due to security concerns. There are many reasons why a user may wants 11 a custom-built system, but if it is one of them, this book is meant 12 for him. 13 13 </para> 14 14 15 15 <para> 16 The fruits of building yourown system are plentiful, but the labour may17 be hard. You have a long way ahead of you but in the end youwill be18 able to call yourself the proud owner of yourown Linux system,19 completely tailored after your needs. You dictatethe layout of16 The fruits of building an own system are plentiful, but the labour may 17 be hard. It is a long way ahead but in the end a user will be 18 able to call himself the proud owner of his own Linux system, 19 completely tailored after his needs. He dictates the layout of 20 20 bootscripts, the file system hierarchy, which programs are installed in 21 21 which directory, which versions of software to use, and more. Perhaps the 22 most important reason is t hat youknow exactly what is installed where,22 most important reason is to know exactly what is installed where, 23 23 why, and how. 24 24 </para>
Note:
See TracChangeset
for help on using the changeset viewer.