Changeset 110969f

Timestamp:

08/28/2001 10:31:24 PM (23 years ago)

Author:

Gerard Beekmans <gerard@…>

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:

df57973

Parents:

c54baff

Message:

Removed the note to link m4 statically outside of chroot. We don't know
if this is still true with the current Glibc-2.2.4 we're using.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1094 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:

• chapter06/m4-inst.xml (modified) (1 diff)

chapter06/m4-inst.xml

@@ -8 +8 @@
 <userinput>make install</userinput></screen></para>
 
-<para>If the base system is running a 2.0 kernel and the Glibc version is
-2.1 then you will most likely get problems executing M4 in the
-chroot'ed environment due to incompatibilities between the M4 program,
-Glibc-2.1 and the running 2.0 kernel. If you have problems executing the 
-m4 program in the chroot'ed environment (for example when you install 
-the autoconf and automake packages) you'll have to exit the chroot'ed 
-environment and compile M4 statically. This way the binary is linked 
-against Glibc 2.0 (if he runs kernel 2.0, Glibc version is 2.0 as 
-well on a decent system. Kernel 2.0 and Glibc-2.1 don't mix very well) 
-and won't give any problems.</para>
-
-<para>To create a statically linked version of M4, execute the following
-commands:</para>
-
-<para><screen><userinput>logout</userinput>
-<userinput>cd $LFS/usr/src/m4-1.4</userinput>
-<userinput>./configure --prefix=/usr</userinput>
-<userinput>make LDFLAGS=-static</userinput>
-<userinput>make prefix=$LFS/usr install</userinput></screen></para>
-
-<para>Now the chroot'ed environment can be re-entered and the
-next package an be installed. If M4 should be re-compiled dynamically,
-this can be done after having rebooted into the LFS system 
-rather than chrooting into it.</para>
-
-<para><screen>&c6-chrootcmd;</screen></para>
-
 </sect2>