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