Changeset 9e4e34c
- Timestamp:
- 05/13/2001 10:07:24 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:
- 016a86b
- Parents:
- 0c4eb2c
- Location:
- chapter06
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/lilo-inst.xml
r0c4eb2c r9e4e34c 20 20 <para> 21 21 It appears that compilation of this package fails on certain machines 22 when the -g compiler flag is being used. If a usercan't compile Lilo at23 all, heshould try to remove the -g value from the CFLAGS variable in the22 when the -g compiler flag is being used. If you can't compile Lilo at 23 all, you should try to remove the -g value from the CFLAGS variable in the 24 24 <filename>Makefile</filename> file. 25 25 </para> -
chapter06/m4-inst.xml
r0c4eb2c r9e4e34c 14 14 <para> 15 15 If the base system is running a 2.0 kernel and the Glibc version is 16 2.1 then a userwill most likely get problems executing M4 in the16 2.1 then you will most likely get problems executing M4 in the 17 17 chroot'ed environment due to incompatibilities between the M4 program, 18 Glibc-2.1 and the running 2.0 kernel. If he hasproblems executing the19 m4 program in the chroot'ed environment (for example when he installs20 the autoconf and automake packages) he'll have to exit the chroot'ed18 Glibc-2.1 and the running 2.0 kernel. If you have problems executing the 19 m4 program in the chroot'ed environment (for example when you install 20 the autoconf and automake packages) you'll have to exit the chroot'ed 21 21 environment and compile M4 statically. This way the binary is linked 22 22 against Glibc 2.0 (if he runs kernel 2.0, Glibc version is 2.0 as -
chapter06/tar-inst.xml
r0c4eb2c r9e4e34c 3 3 4 4 <para> 5 If a user wants to be able to directly use bzip2 files with tar, hecan5 If you want to be able to directly use bzip2 files with tar, you can 6 6 use the tar 7 7 patch available from the LFS FTP site. This patch will add the -y option -
chapter06/vim-inst.xml
r0c4eb2c r9e4e34c 26 26 27 27 <para> 28 If you plan on installing the X Window system on hisLFS29 system, you might want to re-compile Vim after he hasinstalled X. Vim28 If you plan on installing the X Window system on your LFS 29 system, you might want to re-compile Vim after you have installed X. Vim 30 30 comes with a nice GUI version of the editor which requires X and a few 31 31 other libraries to be installed. For more information read the Vim
Note:
See TracChangeset
for help on using the changeset viewer.