1 | <sect2><title> </title><para> </para></sect2>
|
---|
2 |
|
---|
3 | <sect2>
|
---|
4 | <title>Glibc installation</title>
|
---|
5 |
|
---|
6 | <para>Before starting to install Glibc, you must <userinput>cd</userinput>
|
---|
7 | into the <filename>glibc-&glibc-version;</filename> directory and unpack
|
---|
8 | Glibc-linuxthreads in that directory, not in <filename>/usr/src</filename> as
|
---|
9 | you would normally do.</para>
|
---|
10 |
|
---|
11 | <para>This package is known to behave badly when you have changed its
|
---|
12 | default optimization flags (including the -march and -mcpu options).
|
---|
13 | Therefore, if you have defined any environment variables that override
|
---|
14 | default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
|
---|
15 | them when building Glibc.</para>
|
---|
16 |
|
---|
17 | <para>Basically, compiling Glibc in any other way than the book suggests
|
---|
18 | is putting the stability of your system at risk.</para>
|
---|
19 |
|
---|
20 | <para>Though it is a harmless message, the install stage of Glibc will
|
---|
21 | complain about the absence of <filename>/tools/etc/ld.so.conf</filename>.
|
---|
22 | Fix this annoying little error with:</para>
|
---|
23 |
|
---|
24 | <para><screen><userinput>mkdir /tools/etc
|
---|
25 | touch /tools/etc/ld.so.conf</userinput></screen></para>
|
---|
26 |
|
---|
27 | <para>Also, Glibc has a subtle problem when compiled with GCC 3.3.1.
|
---|
28 | Apply the following patch to fix this:</para>
|
---|
29 |
|
---|
30 | <para><screen><userinput>patch -Np1 -i ../glibc-2.3.2-sscanf-1.patch
|
---|
31 | </userinput></screen></para>
|
---|
32 |
|
---|
33 | <para>The documentation that comes with Glibc recommends to build the package
|
---|
34 | not in the source directory but in a separate, dedicated directory:</para>
|
---|
35 |
|
---|
36 | <para><screen><userinput>mkdir ../glibc-build
|
---|
37 | cd ../glibc-build</userinput></screen></para>
|
---|
38 |
|
---|
39 | <para>Next, prepare Glibc to be compiled:</para>
|
---|
40 |
|
---|
41 | <para><screen><userinput>../glibc-&glibc-version;/configure --prefix=/tools \
|
---|
42 | --disable-profile --enable-add-ons \
|
---|
43 | --with-headers=/tools/include \
|
---|
44 | --with-binutils=/tools/bin \
|
---|
45 | --without-gd</userinput></screen></para>
|
---|
46 |
|
---|
47 | <para>The meaning of the new configure options:</para>
|
---|
48 |
|
---|
49 | <itemizedlist>
|
---|
50 | <listitem><para><userinput>--disable-profile</userinput>: This disables the
|
---|
51 | building of the libraries with profiling information. Omit this option if you
|
---|
52 | plan to do profiling.</para></listitem>
|
---|
53 |
|
---|
54 | <listitem><para><userinput>--enable-add-ons</userinput>: This enables any
|
---|
55 | add-ons that were installed with Glibc, in our case Linuxthreads.</para></listitem>
|
---|
56 |
|
---|
57 | <listitem><para><userinput>--with-binutils=/tools/bin</userinput> and
|
---|
58 | <userinput>--with-headers=/tools/include</userinput>: Strictly speaking
|
---|
59 | these switches are not required. But they ensure nothing can go wrong with
|
---|
60 | regard to what kernel headers and Binutils programs get used during the
|
---|
61 | Glibc build.</para></listitem>
|
---|
62 |
|
---|
63 | <listitem><para><userinput> --without-gd</userinput>: This switch ensures
|
---|
64 | that we don't build the <userinput>memusagestat</userinput> program, which
|
---|
65 | strangely enough insists on linking against the host's libraries (libgd,
|
---|
66 | libpng, libz, and so forth).</para></listitem>
|
---|
67 | </itemizedlist>
|
---|
68 |
|
---|
69 | <para>During this stage you will see the following warning:</para>
|
---|
70 |
|
---|
71 | <blockquote><screen>configure: warning:
|
---|
72 | *** These auxiliary programs are missing or too old: msgfmt
|
---|
73 | *** some features will be disabled.
|
---|
74 | *** Check the INSTALL file for required versions.</screen></blockquote>
|
---|
75 |
|
---|
76 | <para>The missing <filename>msgfmt</filename> program (from the Gettext
|
---|
77 | package, which we'll install later) won't cause any problems. The
|
---|
78 | <filename>msgfmt</filename> is used to generate the binary translation
|
---|
79 | files that can make your system talk in a different language. Because these
|
---|
80 | translation files have already been generated for you, there is no need for
|
---|
81 | <filename>msgfmt</filename>. You'd only need the program if you change the
|
---|
82 | translation source files (the <filename>*.po</filename> files in the
|
---|
83 | <filename class="directory">po</filename> subdirectory), which
|
---|
84 | would require you to regenerate the binary files.</para>
|
---|
85 |
|
---|
86 | <para>Continue with compiling the package:</para>
|
---|
87 |
|
---|
88 | <para><screen><userinput>make
|
---|
89 | make check
|
---|
90 | make install</userinput></screen></para>
|
---|
91 |
|
---|
92 | <para>The glibc make check process is highly dependent on certain functions
|
---|
93 | of your host operating system. The most common is a host that fails to mount
|
---|
94 | a tmpfs filesystem at /dev/shm, which may cause glibc tests to fail.</para>
|
---|
95 |
|
---|
96 | <para>The locales (used by Glibc to make your Linux system respond in a
|
---|
97 | different language) weren't installed when you ran the previous command,
|
---|
98 | so we have to do that ourselves now:</para>
|
---|
99 |
|
---|
100 | <para><screen><userinput>make localedata/install-locales</userinput></screen></para>
|
---|
101 |
|
---|
102 | <para>An alternative to running the previous command is to install only
|
---|
103 | those locales which you need or want. This can be achieved by using the
|
---|
104 | <userinput>localedef</userinput> command. Information on this can be
|
---|
105 | found in the <filename>INSTALL</filename> file in the
|
---|
106 | <filename>glibc-&glibc-version;</filename> tree. However, there are a
|
---|
107 | number of locales that are essential for the tests of future packages
|
---|
108 | to pass correctly, in particular, the libstdc++ tests from GCC. The following
|
---|
109 | instructions, in place of the install-locales command above, will install
|
---|
110 | the minimum set of locales necessary for the tests to run successfully:</para>
|
---|
111 |
|
---|
112 | <para><screen><userinput>mkdir -p /tools/lib/locale
|
---|
113 | localedef -i de_DE -f ISO-8859-1 de_DE
|
---|
114 | localedef -i de_DE@euro -f ISO-8859-15 de_DE@euro
|
---|
115 | localedef -i en_HK -f ISO-8859-1 en_HK
|
---|
116 | localedef -i en_PH -f ISO-8859-1 en_PH
|
---|
117 | localedef -i en_US -f ISO-8859-1 en_US
|
---|
118 | localedef -i es_MX -f ISO-8859-1 es_MX
|
---|
119 | localedef -i fr_FR -f ISO-8859-1 fr_FR
|
---|
120 | localedef -i fr_FR@euro -f ISO-8859-15 fr_FR@euro
|
---|
121 | localedef -i it_IT -f ISO-8859-1 it_IT
|
---|
122 | localedef -i ja_JP -f EUC-JP ja_JP</userinput></screen></para>
|
---|
123 |
|
---|
124 | </sect2>
|
---|
125 |
|
---|