Changeset cc107b1 for chapter02/install.xml
- Timestamp:
- 04/12/2001 11:28:53 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, 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, 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/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- bb24243
- Parents:
- 280bcc8
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter02/install.xml
r280bcc8 rcc107b1 8 8 Tar'ed and gzip'ed archives have a .tar.gz or .tgz extension, for 9 9 example.) I'm not going to write down every time how to ungzip and how 10 to untar an archive. I will tellhow to do that once, in this section.10 to untar an archive. I will explain how to do that once, in this section. 11 11 There is also the possibility that a .tar.bz2 file could be downloaded. 12 12 Such a file would be tar'ed and compressed with the bzip2 program. … … 73 73 <para> 74 74 When the archive is unpacked, a new directory will be created under the 75 current directory (and this documentassumes that the archives are unpacked75 current directory (and this book assumes that the archives are unpacked 76 76 under the $LFS/usr/src directory). Please enter that new directory 77 77 before continuing with the installation instructions. Again, every time … … 109 109 After a package is installed, two things can be done with it: 110 110 either the directory that contains the sources can be deleted, 111 either it can be kept. If it is kept, that's fine with me, but if the111 or it can be kept. If it is kept, that's fine with me, but if the 112 112 same package is needed again in a later chapter, the directory 113 113 needs to be deleted first before using it again. If this is not done, 114 114 you might end up in trouble because old settings will be used (settings 115 that apply to the normal Linuxsystem but which don't always apply to115 that apply to the host system but which don't always apply to 116 116 the LFS system). Doing a simple make clean or make distclean does not 117 117 always guarantee a totally clean source tree. … … 119 119 120 120 <para> 121 There is one exception to that rule: don't remove the linux kernel source121 There is one exception to that rule: don't remove the Linux kernel source 122 122 tree. A lot of programs need the kernel headers, so that's the only 123 123 directory that should not be removed, unless no software is to be compiled
Note:
See TracChangeset
for help on using the changeset viewer.