- Timestamp:
- 08/28/2001 10:31: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, 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:
- df57973
- Parents:
- c54baff
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/m4-inst.xml
rc54baff r110969f 8 8 <userinput>make install</userinput></screen></para> 9 9 10 <para>If the base system is running a 2.0 kernel and the Glibc version is11 2.1 then you will most likely get problems executing M4 in the12 chroot'ed environment due to incompatibilities between the M4 program,13 Glibc-2.1 and the running 2.0 kernel. If you have problems executing the14 m4 program in the chroot'ed environment (for example when you install15 the autoconf and automake packages) you'll have to exit the chroot'ed16 environment and compile M4 statically. This way the binary is linked17 against Glibc 2.0 (if he runs kernel 2.0, Glibc version is 2.0 as18 well on a decent system. Kernel 2.0 and Glibc-2.1 don't mix very well)19 and won't give any problems.</para>20 21 <para>To create a statically linked version of M4, execute the following22 commands:</para>23 24 <para><screen><userinput>logout</userinput>25 <userinput>cd $LFS/usr/src/m4-1.4</userinput>26 <userinput>./configure --prefix=/usr</userinput>27 <userinput>make LDFLAGS=-static</userinput>28 <userinput>make prefix=$LFS/usr install</userinput></screen></para>29 30 <para>Now the chroot'ed environment can be re-entered and the31 next package an be installed. If M4 should be re-compiled dynamically,32 this can be done after having rebooted into the LFS system33 rather than chrooting into it.</para>34 35 <para><screen>&c6-chrootcmd;</screen></para>36 37 10 </sect2> 38 11
Note:
See TracChangeset
for help on using the changeset viewer.