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 the directory where you usually
|
---|
9 | unpack all the sources.</para>
|
---|
10 |
|
---|
11 | <note><para>We are going to run the test suite for Glibc in this chapter.
|
---|
12 | However, it's worth pointing out that the Glibc test suite we run in this
|
---|
13 | section is considered not as important as the one we run in Chapter 6.</para></note>
|
---|
14 |
|
---|
15 | <para>This package is known to behave badly when you have changed its
|
---|
16 | default optimization flags (including the -march and -mcpu options).
|
---|
17 | Therefore, if you have defined any environment variables that override
|
---|
18 | default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting
|
---|
19 | them when building Glibc.</para>
|
---|
20 |
|
---|
21 | <para>Basically, compiling Glibc in any other way than the book suggests
|
---|
22 | is putting the stability of your system at risk.</para>
|
---|
23 |
|
---|
24 | <para>Though it is a harmless message, the install stage of Glibc will
|
---|
25 | complain about the absence of <filename>/tools/etc/ld.so.conf</filename>.
|
---|
26 | Fix this annoying little error with:</para>
|
---|
27 |
|
---|
28 | <para><screen><userinput>mkdir /tools/etc
|
---|
29 | touch /tools/etc/ld.so.conf</userinput></screen></para>
|
---|
30 |
|
---|
31 | <para>Also, Glibc has a subtle problem when compiled with GCC 3.3.1.
|
---|
32 | Apply the following patch to fix this:</para>
|
---|
33 |
|
---|
34 | <para><screen><userinput>patch -Np1 -i ../&glibc-sscanf-patch;</userinput></screen></para>
|
---|
35 |
|
---|
36 | <para>The Glibc documentation recommends building Glibc outside of the source
|
---|
37 | directory in a dedicated build directory:</para>
|
---|
38 |
|
---|
39 | <para><screen><userinput>mkdir ../glibc-build
|
---|
40 | cd ../glibc-build</userinput></screen></para>
|
---|
41 |
|
---|
42 | <para>Next, prepare Glibc to be compiled:</para>
|
---|
43 |
|
---|
44 | <para><screen><userinput>../glibc-&glibc-version;/configure --prefix=/tools \
|
---|
45 | --disable-profile --enable-add-ons \
|
---|
46 | --with-headers=/tools/include \
|
---|
47 | --with-binutils=/tools/bin \
|
---|
48 | --without-gd</userinput></screen></para>
|
---|
49 |
|
---|
50 | <para>The meaning of the configure options:</para>
|
---|
51 |
|
---|
52 | <itemizedlist>
|
---|
53 | <listitem><para><userinput>--disable-profile</userinput>: This disables the
|
---|
54 | building of the libraries with profiling information. Omit this option if you
|
---|
55 | plan to do profiling.</para></listitem>
|
---|
56 |
|
---|
57 | <listitem><para><userinput>--enable-add-ons</userinput>: This enables any
|
---|
58 | add-ons that were installed with Glibc, in our case Linuxthreads.</para></listitem>
|
---|
59 |
|
---|
60 | <listitem><para><userinput>--with-binutils=/tools/bin</userinput> and
|
---|
61 | <userinput>--with-headers=/tools/include</userinput>: Strictly speaking
|
---|
62 | these switches are not required. But they ensure nothing can go wrong with
|
---|
63 | regard to what kernel headers and Binutils programs get used during the
|
---|
64 | Glibc build.</para></listitem>
|
---|
65 |
|
---|
66 | <listitem><para><userinput> --without-gd</userinput>: This switch ensures
|
---|
67 | that we don't build the <userinput>memusagestat</userinput> program, which
|
---|
68 | strangely enough insists on linking against the host's libraries (libgd,
|
---|
69 | libpng, libz, and so forth).</para></listitem>
|
---|
70 | </itemizedlist>
|
---|
71 |
|
---|
72 | <para>During this stage you might see the following warning:</para>
|
---|
73 |
|
---|
74 | <blockquote><screen>configure: WARNING:
|
---|
75 | *** These auxiliary programs are missing or incompatible versions: msgfmt
|
---|
76 | *** some features will be disabled.
|
---|
77 | *** Check the INSTALL file for required versions.</screen></blockquote>
|
---|
78 |
|
---|
79 | <para>The missing or incompatible <filename>msgfmt</filename> program is
|
---|
80 | generally harmless, but it's believed it can sometimes cause problems when
|
---|
81 | running the test suite.</para>
|
---|
82 |
|
---|
83 | <para>Compile the package:</para>
|
---|
84 |
|
---|
85 | <para><screen><userinput>make</userinput></screen></para>
|
---|
86 |
|
---|
87 | <para>Run the test suite:</para>
|
---|
88 |
|
---|
89 | <para><screen><userinput>make check</userinput></screen></para>
|
---|
90 |
|
---|
91 | <para>The Glibc test suite is highly dependent on certain functions of your host
|
---|
92 | system, in particular the kernel. Additionally, here in Chapter 5, some tests
|
---|
93 | can be adversely affected by existing tools or environmental issues on the host
|
---|
94 | system. Of course, these won't be a problem when we run the Glibc test suite
|
---|
95 | inside the chroot environment of Chapter 6. In general, the Glibc test suite is
|
---|
96 | always expected to pass. However, as mentioned above, some failures are
|
---|
97 | unavoidable in certain circumstances. Here is a list of the most common issues
|
---|
98 | we are aware of:</para>
|
---|
99 |
|
---|
100 | <itemizedlist>
|
---|
101 | <listitem><para>The math tests sometimes fail when running on systems where the
|
---|
102 | CPU is not a relatively new genuine Intel or genuine AMD. Certain optimization
|
---|
103 | settings are also known to be a factor here.</para></listitem>
|
---|
104 |
|
---|
105 | <listitem><para>The gettext test sometimes fails due to host system issues. The
|
---|
106 | exact reasons are not yet clear.</para></listitem>
|
---|
107 |
|
---|
108 | <listitem><para>The atime test sometimes fails when the LFS partition is mounted
|
---|
109 | with the noatime option or due to other file system quirks.</para></listitem>
|
---|
110 |
|
---|
111 | <listitem><para>In general, when running on slower hardware, some tests might
|
---|
112 | fail due to test timeouts being exceeded.</para></listitem>
|
---|
113 |
|
---|
114 | <listitem><para>The shm test might fail in the circumstances of the host system
|
---|
115 | running the devfs file system but not having the tmpfs file system mounted at
|
---|
116 | /dev/shm due to lack of support for tmpfs in the kernel.</para></listitem>
|
---|
117 | </itemizedlist>
|
---|
118 |
|
---|
119 | <para>In summary, don't worry too much if you see Glibc test suite failures here
|
---|
120 | in Chapter 5. The Glibc in Chapter 6 is the one we'll ultimately end up using so
|
---|
121 | that is the one we would really like to see pass. But please keep in mind, even
|
---|
122 | in Chapter 6 some failures could still occur, the math tests for example. When
|
---|
123 | experiencing a failure, note the failure then continue on by reissuing the
|
---|
124 | <userinput>make check</userinput>. The test suite should pick up where it left
|
---|
125 | off and continue on. You can circumvent this stop-start sequence by issuing a
|
---|
126 | <userinput>make -k check</userinput>. But If you do that, be sure to log the
|
---|
127 | output so that you can later on peruse the log file and examine the total number
|
---|
128 | of failures.</para>
|
---|
129 |
|
---|
130 | <para>Now install the package:</para>
|
---|
131 |
|
---|
132 | <para><screen><userinput>make install</userinput></screen></para>
|
---|
133 |
|
---|
134 | <para>Different countries and cultures have varying conventions for how to
|
---|
135 | communicate. These conventions range from very simple ones, such as the format
|
---|
136 | for representing dates and times, to very complex ones, such as the language
|
---|
137 | spoken. This "internationalization" works by means of locales. We'll install the
|
---|
138 | Glibc locales now:</para>
|
---|
139 |
|
---|
140 | <para><screen><userinput>make localedata/install-locales</userinput></screen></para>
|
---|
141 |
|
---|
142 | <para>An alternative to running the previous command is to install only
|
---|
143 | those locales which you need or want. This can be achieved by using the
|
---|
144 | <userinput>localedef</userinput> command. Information on this can be
|
---|
145 | found in the <filename>INSTALL</filename> file in the
|
---|
146 | <filename>glibc-&glibc-version;</filename> source. However, there are a
|
---|
147 | number of locales that are essential for the tests of future packages
|
---|
148 | to pass correctly, in particular, the libstdc++ tests from GCC. The following
|
---|
149 | instructions, instead of the install-locales command above, will install
|
---|
150 | the minimum set of locales necessary for the tests to run successfully:</para>
|
---|
151 |
|
---|
152 | <para><screen><userinput>mkdir -p /tools/lib/locale
|
---|
153 | localedef -i de_DE -f ISO-8859-1 de_DE
|
---|
154 | localedef -i de_DE@euro -f ISO-8859-15 de_DE@euro
|
---|
155 | localedef -i en_HK -f ISO-8859-1 en_HK
|
---|
156 | localedef -i en_PH -f ISO-8859-1 en_PH
|
---|
157 | localedef -i en_US -f ISO-8859-1 en_US
|
---|
158 | localedef -i es_MX -f ISO-8859-1 es_MX
|
---|
159 | localedef -i fr_FR -f ISO-8859-1 fr_FR
|
---|
160 | localedef -i fr_FR@euro -f ISO-8859-15 fr_FR@euro
|
---|
161 | localedef -i it_IT -f ISO-8859-1 it_IT
|
---|
162 | localedef -i ja_JP -f EUC-JP ja_JP</userinput></screen></para>
|
---|
163 |
|
---|
164 | </sect2>
|
---|
165 |
|
---|