| 1 | <sect2>
|
|---|
| 2 | <title>Installation of M4</title>
|
|---|
| 3 |
|
|---|
| 4 | <para>
|
|---|
| 5 | Install M4 by running the following commands:
|
|---|
| 6 | </para>
|
|---|
| 7 |
|
|---|
| 8 | <blockquote><literallayout>
|
|---|
| 9 | <userinput>./configure --prefix=/usr &&</userinput>
|
|---|
| 10 | <userinput>make &&</userinput>
|
|---|
| 11 | <userinput>make install</userinput>
|
|---|
| 12 | </literallayout></blockquote>
|
|---|
| 13 |
|
|---|
| 14 | <para>
|
|---|
| 15 | If the base system is running a 2.0 kernel and the Glibc version is
|
|---|
| 16 | 2.1 then a user will most likely get problems executing M4 in the
|
|---|
| 17 | chroot'ed environment due to incompatibilities between the M4 program,
|
|---|
| 18 | Glibc-2.1 and the running 2.0 kernel. If he has problems executing the
|
|---|
| 19 | m4 program in the chroot'ed environment (for example when he installs
|
|---|
| 20 | the autoconf and automake packages) he'll have to exit the chroot'ed
|
|---|
| 21 | environment and compile M4 statically. This way the binary is linked
|
|---|
| 22 | against Glibc 2.0 (if he runs kernel 2.0, Glibc version is 2.0 as
|
|---|
| 23 | well on a decent system. Kernel 2.0 and Glibc-2.1 don't mix very well)
|
|---|
| 24 | and won't give any problems.
|
|---|
| 25 | </para>
|
|---|
| 26 |
|
|---|
| 27 | <para>
|
|---|
| 28 | To create a statically linked version of M4, execute the following
|
|---|
| 29 | commands:
|
|---|
| 30 | </para>
|
|---|
| 31 |
|
|---|
| 32 | <blockquote><literallayout>
|
|---|
| 33 | <userinput>logout</userinput>
|
|---|
| 34 | <userinput>cd $LFS/usr/src/m4-1.4</userinput>
|
|---|
| 35 | <userinput>./configure --prefix=/usr</userinput>
|
|---|
| 36 | <userinput>make LDFLAGS=-static</userinput>
|
|---|
| 37 | <userinput>make prefix=$LFS/usr install</userinput>
|
|---|
| 38 | </literallayout></blockquote>
|
|---|
| 39 |
|
|---|
| 40 | <para>
|
|---|
| 41 | Now the chroot'ed environment can be re-entered and the
|
|---|
| 42 | next package an be installed. If M4 should be re-compiled dynamically,
|
|---|
| 43 | this can be done
|
|---|
| 44 | after having rebooted into the LFS system rather than chrooting into it.
|
|---|
| 45 | </para>
|
|---|
| 46 |
|
|---|
| 47 | <blockquote><literallayout>
|
|---|
| 48 | <userinput>chroot $LFS env -i HOME=/root bash --login</userinput>
|
|---|
| 49 | </literallayout></blockquote>
|
|---|
| 50 |
|
|---|
| 51 | </sect2>
|
|---|
| 52 |
|
|---|
