[673b0d8] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
| 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
|
---|
| 3 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
| 4 | %general-entities;
|
---|
| 5 | ]>
|
---|
[3be4d97] | 6 | <sect1 id="ch-tools-glibc">
|
---|
[673b0d8] | 7 | <title>Glibc-&glibc-version;</title>
|
---|
| 8 | <?dbhtml filename="glibc.html"?>
|
---|
[bc82645e] | 9 |
|
---|
[673b0d8] | 10 | <indexterm zone="ch-tools-glibc">
|
---|
| 11 | <primary sortas="a-Glibc">Glibc</primary>
|
---|
| 12 | <secondary>tools</secondary></indexterm>
|
---|
[bc82645e] | 13 |
|
---|
[673b0d8] | 14 | <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="../chapter06/glibc.xml" xpointer="xpointer(/sect1/para[1])"/>
|
---|
| 15 |
|
---|
| 16 | <screen>&buildtime; 11.8 SBU
|
---|
[2f2b6d6] | 17 | &diskspace; 734.2 MB</screen>
|
---|
[673b0d8] | 18 |
|
---|
| 19 | <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="../chapter06/glibc.xml" xpointer="xpointer(/sect1/para[2])"/>
|
---|
[73aedd1d] | 20 |
|
---|
| 21 |
|
---|
| 22 | <sect2>
|
---|
[5888299] | 23 | <title>Installation of Glibc</title>
|
---|
[73aedd1d] | 24 |
|
---|
[ede9b9b] | 25 | <para>This package is known to behave badly when you change its default
|
---|
| 26 | optimization flags (including the <emphasis>-march</emphasis> and
|
---|
| 27 | <emphasis>-mcpu</emphasis> options). Therefore, if you have defined any
|
---|
| 28 | environment variables that override default optimizations, such as CFLAGS and
|
---|
[673b0d8] | 29 | CXXFLAGS, we recommend un-setting them when building Glibc.</para>
|
---|
[73aedd1d] | 30 |
|
---|
| 31 | <para>Basically, compiling Glibc in any other way than the book suggests
|
---|
| 32 | is putting the stability of your system at risk.</para>
|
---|
| 33 |
|
---|
| 34 | <para>The Glibc documentation recommends building Glibc outside of the source
|
---|
| 35 | directory in a dedicated build directory:</para>
|
---|
| 36 |
|
---|
| 37 | <screen><userinput>mkdir ../glibc-build
|
---|
| 38 | cd ../glibc-build</userinput></screen>
|
---|
| 39 |
|
---|
[d27a27b] | 40 | <para>Next, prepare Glibc for compilation:</para>
|
---|
[73aedd1d] | 41 |
|
---|
[2f2b6d6] | 42 | <screen><userinput>../glibc-&glibc-version;/configure --prefix=/tools \
|
---|
[673b0d8] | 43 | --disable-profile --enable-add-ons=linuxthreads \
|
---|
| 44 | --with-binutils=/tools/bin --with-headers=/tools/include \
|
---|
| 45 | --without-gd --without-cvs</userinput></screen>
|
---|
[73aedd1d] | 46 |
|
---|
| 47 | <para>The meaning of the configure options:</para>
|
---|
| 48 |
|
---|
| 49 | <itemizedlist>
|
---|
[673b0d8] | 50 | <listitem><para><userinput>--disable-profile</userinput>: This
|
---|
| 51 | builds the libraries without profiling information. Omit this option if you
|
---|
[ede9b9b] | 52 | plan to do profiling on the temporary tools.</para></listitem>
|
---|
[73aedd1d] | 53 |
|
---|
[d0a6c4c] | 54 | <listitem><para><userinput>--enable-add-ons=linuxthreads</userinput>: This
|
---|
| 55 | tells Glibc to use the Linuxthreads add-on as its threading
|
---|
| 56 | library.</para></listitem>
|
---|
[73aedd1d] | 57 |
|
---|
| 58 | <listitem><para><userinput>--with-binutils=/tools/bin</userinput> and
|
---|
| 59 | <userinput>--with-headers=/tools/include</userinput>: Strictly speaking
|
---|
| 60 | these switches are not required. But they ensure nothing can go wrong with
|
---|
| 61 | regard to what kernel headers and Binutils programs get used during the
|
---|
| 62 | Glibc build.</para></listitem>
|
---|
| 63 |
|
---|
[673b0d8] | 64 | <listitem><para><userinput>--without-gd</userinput>: This prevents
|
---|
| 65 | the build of the <command>memusagestat</command> program, which
|
---|
[73aedd1d] | 66 | strangely enough insists on linking against the host's libraries (libgd,
|
---|
| 67 | libpng, libz, and so forth).</para></listitem>
|
---|
[d0a6c4c] | 68 |
|
---|
| 69 | <listitem><para><userinput>--without-cvs</userinput>: This is meant to prevent
|
---|
[c76accc] | 70 | the Makefiles from attempting automatic CVS checkouts when using a CVS
|
---|
| 71 | snapshot. But it's not actually needed these days. We use it because it
|
---|
| 72 | suppresses an annoying but harmless warning about a missing
|
---|
| 73 | <command>autoconf</command> program.</para></listitem>
|
---|
[73aedd1d] | 74 | </itemizedlist>
|
---|
| 75 |
|
---|
| 76 | <para>During this stage you might see the following warning:</para>
|
---|
| 77 |
|
---|
| 78 | <blockquote><screen>configure: WARNING:
|
---|
| 79 | *** These auxiliary programs are missing or incompatible versions: msgfmt
|
---|
| 80 | *** some features will be disabled.
|
---|
| 81 | *** Check the INSTALL file for required versions.</screen></blockquote>
|
---|
| 82 |
|
---|
[ede9b9b] | 83 | <para>The missing or incompatible <command>msgfmt</command> program is
|
---|
[73aedd1d] | 84 | generally harmless, but it's believed it can sometimes cause problems when
|
---|
| 85 | running the test suite.</para>
|
---|
| 86 |
|
---|
| 87 | <para>Compile the package:</para>
|
---|
| 88 |
|
---|
[7efb663] | 89 | <screen><userinput>make AUTOCONF=no</userinput></screen>
|
---|
[73aedd1d] | 90 |
|
---|
[ede9b9b] | 91 | <para>Compilation is now complete. As mentioned earlier, we don't recommend
|
---|
[443cace] | 92 | running the test suites for the temporary system here in this chapter. If you
|
---|
| 93 | still want to run the Glibc test suite anyway, the following command will do
|
---|
| 94 | so:</para>
|
---|
[73aedd1d] | 95 |
|
---|
| 96 | <screen><userinput>make check</userinput></screen>
|
---|
| 97 |
|
---|
| 98 | <para>The Glibc test suite is highly dependent on certain functions of your host
|
---|
| 99 | system, in particular the kernel. Additionally, here in this chapter some tests
|
---|
| 100 | can be adversely affected by existing tools or environmental issues on the host
|
---|
| 101 | system. Of course, these won't be a problem when we run the Glibc test suite
|
---|
[ede9b9b] | 102 | inside the chroot environment of <xref linkend="chapter-building-system"/>. In
|
---|
| 103 | general, the Glibc test suite is always expected to pass. However, as mentioned
|
---|
| 104 | above, in certain circumstances some failures are unavoidable. Here is a list
|
---|
| 105 | of the most common issues we are aware of:</para>
|
---|
[73aedd1d] | 106 |
|
---|
| 107 | <itemizedlist>
|
---|
| 108 | <listitem><para>The <emphasis>math</emphasis> tests sometimes fail when running
|
---|
| 109 | on systems where the CPU is not a relatively new genuine Intel or authentic AMD.
|
---|
| 110 | Certain optimization settings are also known to be a factor here.</para></listitem>
|
---|
| 111 |
|
---|
| 112 | <listitem><para>The <emphasis>gettext</emphasis> test sometimes fails due to
|
---|
| 113 | host system issues. The exact reasons are not yet clear.</para></listitem>
|
---|
| 114 |
|
---|
| 115 | <listitem><para>The <emphasis>atime</emphasis> test sometimes fails when the
|
---|
| 116 | LFS partition is mounted with the <emphasis>noatime</emphasis> option, or due
|
---|
| 117 | to other file system quirks.</para></listitem>
|
---|
| 118 |
|
---|
| 119 | <listitem><para>The <emphasis>shm</emphasis> test might fail when the host
|
---|
| 120 | system is running the devfs file system but doesn't have the tmpfs file system
|
---|
| 121 | mounted at <filename>/dev/shm</filename> due to lack of support for tmpfs in
|
---|
| 122 | the kernel.</para></listitem>
|
---|
| 123 |
|
---|
| 124 | <listitem><para>When running on older and slower hardware, some tests might
|
---|
| 125 | fail due to test timeouts being exceeded.</para></listitem>
|
---|
| 126 | </itemizedlist>
|
---|
| 127 |
|
---|
| 128 | <para>In summary, don't worry too much if you see Glibc test suite failures
|
---|
[ede9b9b] | 129 | here in this chapter. The Glibc in <xref linkend="chapter-building-system"/> is
|
---|
| 130 | the one we'll ultimately end up using, so that is the one we would really like
|
---|
| 131 | to see pass the tests (but even there some failures could still occur -- the
|
---|
| 132 | <emphasis>math</emphasis> tests, for example). When experiencing a failure,
|
---|
| 133 | make a note of it, then continue by reissuing the <command>make
|
---|
| 134 | check</command>. The test suite should pick up where it left off and continue.
|
---|
| 135 | You can circumvent this stop-start sequence by issuing a <command>make -k
|
---|
| 136 | check</command>. But if you do that, be sure to log the output so that you can
|
---|
| 137 | later peruse the log file and examine the total number of failures.</para>
|
---|
| 138 |
|
---|
| 139 | <para>Though it is a harmless message, the install stage of Glibc will at the
|
---|
| 140 | end complain about the absence of <filename>/tools/etc/ld.so.conf</filename>.
|
---|
| 141 | Prevent this confusing little warning with:</para>
|
---|
[1caa48e] | 142 |
|
---|
| 143 | <screen><userinput>mkdir /tools/etc
|
---|
| 144 | touch /tools/etc/ld.so.conf</userinput></screen>
|
---|
| 145 |
|
---|
[73aedd1d] | 146 | <para>Now install the package:</para>
|
---|
| 147 |
|
---|
| 148 | <screen><userinput>make install</userinput></screen>
|
---|
| 149 |
|
---|
| 150 | <para>Different countries and cultures have varying conventions for how to
|
---|
| 151 | communicate. These conventions range from very simple ones, such as the format
|
---|
| 152 | for representing dates and times, to very complex ones, such as the language
|
---|
[673b0d8] | 153 | spoken. The <quote>internationalization</quote> of GNU programs works by means
|
---|
| 154 | of <emphasis>locales</emphasis>.</para>
|
---|
[443cace] | 155 |
|
---|
| 156 | <note><para>If you are not running the test suites here in this chapter as per
|
---|
| 157 | our recommendation, there is little point in installing the locales now. We'll
|
---|
| 158 | be installing the locales in the next chapter.</para></note>
|
---|
| 159 |
|
---|
| 160 | <para>If you still want to install the Glibc locales anyway, the following
|
---|
| 161 | command will do so:</para>
|
---|
[73aedd1d] | 162 |
|
---|
| 163 | <screen><userinput>make localedata/install-locales</userinput></screen>
|
---|
| 164 |
|
---|
[d0a6c4c] | 165 | <para>An alternative to running the previous command is to install only those
|
---|
| 166 | locales which you need or want. This can be achieved by using the
|
---|
[90e3cb3] | 167 | <command>localedef</command> command. Information on this can be found in
|
---|
[d0a6c4c] | 168 | the <filename>INSTALL</filename> file in the Glibc source. However, there are
|
---|
| 169 | a number of locales that are essential for the tests of future packages to
|
---|
| 170 | pass, in particular, the <emphasis>libstdc++</emphasis> tests from GCC. The
|
---|
| 171 | following instructions, instead of the install-locales target above, will
|
---|
| 172 | install the minimum set of locales necessary for the tests to run
|
---|
| 173 | successfully:</para>
|
---|
[73aedd1d] | 174 |
|
---|
| 175 | <screen><userinput>mkdir -p /tools/lib/locale
|
---|
| 176 | localedef -i de_DE -f ISO-8859-1 de_DE
|
---|
| 177 | localedef -i de_DE@euro -f ISO-8859-15 de_DE@euro
|
---|
| 178 | localedef -i en_HK -f ISO-8859-1 en_HK
|
---|
| 179 | localedef -i en_PH -f ISO-8859-1 en_PH
|
---|
| 180 | localedef -i en_US -f ISO-8859-1 en_US
|
---|
| 181 | localedef -i es_MX -f ISO-8859-1 es_MX
|
---|
[efb32ca] | 182 | localedef -i fa_IR -f UTF-8 fa_IR
|
---|
[73aedd1d] | 183 | localedef -i fr_FR -f ISO-8859-1 fr_FR
|
---|
| 184 | localedef -i fr_FR@euro -f ISO-8859-15 fr_FR@euro
|
---|
| 185 | localedef -i it_IT -f ISO-8859-1 it_IT
|
---|
| 186 | localedef -i ja_JP -f EUC-JP ja_JP</userinput></screen>
|
---|
| 187 |
|
---|
| 188 | </sect2>
|
---|
[bc82645e] | 189 |
|
---|
[673b0d8] | 190 | <sect2><title> </title><para> </para>
|
---|
[5888299] | 191 | <para>The details on this package are found in <xref linkend="contents-glibc"/>.</para>
|
---|
[673b0d8] | 192 | <para> </para></sect2>
|
---|
[5888299] | 193 |
|
---|
[bc82645e] | 194 | </sect1>
|
---|