blob: 62335ac32595eed63a41380995628ef4383702dd (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
|
<sect2>
<title>Installation of Glibc</title>
<para>
Unpack the glibc-linuxthreads in the glibc-&glibc-version; directory, not in
/usr/src.
</para>
<para>
Install Glibc by running the following commands:
</para>
<para>
<screen>
<userinput>mknod -m 0666 /dev/null c 1 3 &&</userinput>
<userinput>touch /etc/ld.so.conf &&</userinput>
<userinput>mkdir /usr/src/glibc-build &&</userinput>
<userinput>cd /usr/src/glibc-build &&</userinput>
<userinput>sed s/"\$(PERL)"/"\/usr\/bin\/perl"/ \</userinput>
<userinput> ../glibc-&glibc-version;/malloc/Makefile > tmp~ &&</userinput>
<userinput>mv tmp~ ../glibc-&glibc-version;/malloc/Makefile &&</userinput>
<userinput>sed "s/root/0/" ../glibc-&glibc-version;/login/Makefile > tmp~ &&</userinput>
<userinput>mv tmp~ ../glibc-&glibc-version;/login/Makefile &&</userinput>
<userinput>../glibc-&glibc-version;/configure \</userinput>
<userinput> --prefix=/usr --enable-add-ons \</userinput>
<userinput> --libexecdir=/usr/bin &&</userinput>
<userinput>sed s/"cross-compiling = yes"/"cross-compiling = no"/ \</userinput>
<userinput> config.make > config.make~ &&</userinput>
<userinput>mv config.make~ config.make &&</userinput>
<userinput>make &&</userinput>
<userinput>make install &&</userinput>
<userinput>make localedata/install-locales</userinput>
</screen>
</para>
<para>
During the configure stage you will see the following warning:
</para>
<blockquote><screen>
configure: warning:
*** An auxiliary program is missing or too old;
*** some features will be disabled.
*** Check the INSTALL file for required versions.
</screen></blockquote>
<para>
This warning refers to the missing msgfmt program from the gettext
package. But there is nothing to worry about: Glib will still be
installed the same way as when msgfmt is present. It can safely be
ignored in our case.
</para>
<para>
By exiting the chroot'ed environment and re-entering it, you will be
able to get rid of the "I have no name!" message in the command prompt,
which is caused by bash's inability to resolve a userid to a username.
You don't have to exit and re-enter chroot, but it's highly recommended
to ensure a properly working bash.
</para>
<para>
Run the following commands to accomplish this:
</para>
<para>
<screen>
<userinput>logout</userinput>
&c6-chrootcmd;
</screen>
</para>
</sect2>
|