From b08f4096533577934b885fa9df41d3881d141612 Mon Sep 17 00:00:00 2001 From: Gerard Beekmans Date: Thu, 15 Feb 2001 15:26:52 +0000 Subject: Initial XML commit git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@174 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter06/m4-inst.sgml | 57 -------------------------------------------------- 1 file changed, 57 deletions(-) delete mode 100644 chapter06/m4-inst.sgml (limited to 'chapter06/m4-inst.sgml') diff --git a/chapter06/m4-inst.sgml b/chapter06/m4-inst.sgml deleted file mode 100644 index ef29a5d65..000000000 --- a/chapter06/m4-inst.sgml +++ /dev/null @@ -1,57 +0,0 @@ - -Installation of M4 - - -Install M4 by running the following commands: - - -
- - ./configure --prefix=/usr && - make && - make install - -
- - -If you're base system is running a 2.0 kernel and your 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 you run kernel 2.0 you're 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 you any problems. - - - -To create a statically linked version of M4, execute the following -commands: - - -
- -logout -cd $LFS/usr/src/m4-1.4 -./configure --prefix=/usr --disable-nls -make LDFLAGS=-static -make prefix=$LFS/usr install - -
- - -Now you can re-enter the chroot'ed environment and continue with the -next package. If you wish to recompile M4 dynamically, you can do that -after you have rebooted into the LFS system rather than chroot'ed into it. - - -
- - chroot $LFS env -i HOME=/root bash --login - -
- - - -- cgit v1.2.3-54-g00ecf