diff options
| author | Simon Perreault <nomis80@videotron.ca> | 2001-05-13 22:07:24 +0000 |
|---|---|---|
| committer | Simon Perreault <nomis80@videotron.ca> | 2001-05-13 22:07:24 +0000 |
| commit | 9e4e34c05027fbcda217a3744ebe91a541ee093a (patch) | |
| tree | 46ce76510c2bbf0aeb47d99fbb84e5a647f1ed3e /chapter06/m4-inst.xml | |
| parent | 0c4eb2c99a6005a262108a18fc460161c6d22783 (diff) | |
he -> you
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@635 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter06/m4-inst.xml')
| -rw-r--r-- | chapter06/m4-inst.xml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/chapter06/m4-inst.xml b/chapter06/m4-inst.xml index 6985745fe..e43aeece3 100644 --- a/chapter06/m4-inst.xml +++ b/chapter06/m4-inst.xml @@ -13,11 +13,11 @@ Install M4 by running the following commands: <para> If the base system is running a 2.0 kernel and the Glibc version is -2.1 then a user will most likely get problems executing M4 in the +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 he has problems executing the -m4 program in the chroot'ed environment (for example when he installs -the autoconf and automake packages) he'll have to exit the chroot'ed +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) |