[673b0d8] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
[b06ca36] | 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
---|
| 3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
---|
[673b0d8] | 4 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
| 5 | %general-entities;
|
---|
| 6 | ]>
|
---|
[1f7ca93] | 7 |
|
---|
[9652249] | 8 | <sect1 id="ch-tools-glibc" role="wrap">
|
---|
[1f7ca93] | 9 | <?dbhtml filename="glibc.html"?>
|
---|
| 10 |
|
---|
[e747759] | 11 | <sect1info condition="script">
|
---|
| 12 | <productname>glibc</productname>
|
---|
| 13 | <productnumber>&glibc-version;</productnumber>
|
---|
| 14 | <address>&glibc-url;</address>
|
---|
| 15 | </sect1info>
|
---|
| 16 |
|
---|
[1f7ca93] | 17 | <title>Glibc-&glibc-version;</title>
|
---|
| 18 |
|
---|
| 19 | <indexterm zone="ch-tools-glibc">
|
---|
| 20 | <primary sortas="a-Glibc">Glibc</primary>
|
---|
| 21 | <secondary>tools</secondary>
|
---|
| 22 | </indexterm>
|
---|
| 23 |
|
---|
| 24 | <sect2 role="package">
|
---|
| 25 | <title/>
|
---|
[bc82645e] | 26 |
|
---|
[d9441360] | 27 | <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
|
---|
[1f7ca93] | 28 | href="../chapter06/glibc.xml"
|
---|
| 29 | xpointer="xpointer(/sect1/sect2[1]/para[1])"/>
|
---|
[81fd230] | 30 |
|
---|
[1f7ca93] | 31 | <segmentedlist>
|
---|
| 32 | <segtitle>&buildtime;</segtitle>
|
---|
| 33 | <segtitle>&diskspace;</segtitle>
|
---|
[673b0d8] | 34 |
|
---|
[1f7ca93] | 35 | <seglistitem>
|
---|
[e4a5635] | 36 | <seg>&glibc-ch5-sbu;</seg>
|
---|
| 37 | <seg>&glibc-ch5-du;</seg>
|
---|
[1f7ca93] | 38 | </seglistitem>
|
---|
| 39 | </segmentedlist>
|
---|
[673b0d8] | 40 |
|
---|
[1f7ca93] | 41 | </sect2>
|
---|
[73aedd1d] | 42 |
|
---|
[1f7ca93] | 43 | <sect2 role="installation">
|
---|
| 44 | <title>Installation of Glibc</title>
|
---|
[73aedd1d] | 45 |
|
---|
[0fe6ccd8] | 46 | <para>In some cases, particularly LFS 7.1, the rpc headers were not
|
---|
| 47 | installed properly. Test to see if they are installed in the host system
|
---|
| 48 | and install if they are not:</para>
|
---|
| 49 |
|
---|
[2ca8941] | 50 | <screen><userinput remap="pre">if [ ! -r /usr/include/rpc/types.h ]; then
|
---|
[0fe6ccd8] | 51 | su -c 'mkdir -p /usr/include/rpc'
|
---|
| 52 | su -c 'cp -v sunrpc/rpc/*.h /usr/include/rpc'
|
---|
| 53 | fi</userinput></screen>
|
---|
| 54 |
|
---|
[20dd334] | 55 | <para>An upstream change needs to be reverted:</para>
|
---|
| 56 |
|
---|
| 57 | <screen><userinput remap="pre">sed -i -e 's/static __m128i/inline &/' sysdeps/x86_64/multiarch/strstr.c</userinput></screen>
|
---|
| 58 |
|
---|
[9bda40d] | 59 | <para>The Glibc documentation recommends building Glibc outside of the source
|
---|
| 60 | directory in a dedicated build directory:</para>
|
---|
| 61 |
|
---|
[0445a3d] | 62 | <screen><userinput remap="pre">mkdir -v ../glibc-build
|
---|
[73aedd1d] | 63 | cd ../glibc-build</userinput></screen>
|
---|
[d9c836bb] | 64 | <!--
|
---|
[2a7ac34] | 65 | <para>Because Glibc no longer supports i386, its developers say to use the
|
---|
| 66 | compiler flag <parameter>-march=i486</parameter> when building it for x86
|
---|
| 67 | machines. There are several ways to accomplish that, but testing shows that
|
---|
| 68 | the flag is best placed inside the build variable <quote>CFLAGS</quote>.
|
---|
| 69 | Instead of overriding completely what Glibc's internal build system uses
|
---|
| 70 | for CFLAGS, append the new flag to the existing contents of CFLAGS by
|
---|
[1c6f1c1] | 71 | making use of the special file <filename>configparms</filename>. The
|
---|
| 72 | -mtune=native flag is also necessary to reset a reasonable value for -mtune
|
---|
| 73 | that is changed when setting -march.</para>
|
---|
[2a7ac34] | 74 |
|
---|
[6e88633] | 75 | <screen><userinput remap="configure">case `uname -m` in
|
---|
| 76 | i?86) echo "CFLAGS += -march=i486 -mtune=native" > configparms ;;
|
---|
| 77 | esac</userinput></screen>
|
---|
[d9c836bb] | 78 | -->
|
---|
[f1c177f] | 79 |
|
---|
[1f7ca93] | 80 | <para>Next, prepare Glibc for compilation:</para>
|
---|
[73aedd1d] | 81 |
|
---|
[9f5aaf7] | 82 | <screen><userinput remap="configure">../glibc-&glibc-version;/configure \
|
---|
[6458e31] | 83 | --prefix=/tools \
|
---|
| 84 | --host=$LFS_TGT \
|
---|
[9f5aaf7] | 85 | --build=$(../glibc-&glibc-version;/scripts/config.guess) \
|
---|
[6458e31] | 86 | --disable-profile \
|
---|
[a93258d] | 87 | --enable-kernel=&min-kernel; \
|
---|
[6458e31] | 88 | --with-headers=/tools/include \
|
---|
| 89 | libc_cv_forced_unwind=yes \
|
---|
| 90 | libc_cv_ctors_header=yes \
|
---|
[9f5aaf7] | 91 | libc_cv_c_cleanup=yes</userinput></screen>
|
---|
[73aedd1d] | 92 |
|
---|
[1f7ca93] | 93 | <variablelist>
|
---|
| 94 | <title>The meaning of the configure options:</title>
|
---|
| 95 |
|
---|
[4e82d47] | 96 | <varlistentry>
|
---|
| 97 | <term><parameter>--host=$LFS_TGT, --build=$(../glibc-&glibc-version;/scripts/config.guess)</parameter></term>
|
---|
| 98 | <listitem>
|
---|
| 99 | <para>The combined effect of these switches is that Glibc's build system
|
---|
| 100 | configures itself to cross-compile, using the cross-linker and
|
---|
| 101 | cross-compiler in <filename class="directory">/tools</filename>.</para>
|
---|
| 102 | </listitem>
|
---|
| 103 | </varlistentry>
|
---|
| 104 |
|
---|
[1f7ca93] | 105 | <varlistentry>
|
---|
| 106 | <term><parameter>--disable-profile</parameter></term>
|
---|
| 107 | <listitem>
|
---|
| 108 | <para>This builds the libraries without profiling information. Omit
|
---|
| 109 | this option if profiling on the temporary tools is necessary.</para>
|
---|
| 110 | </listitem>
|
---|
| 111 | </varlistentry>
|
---|
| 112 |
|
---|
| 113 | <varlistentry>
|
---|
[70cd9f32] | 114 | <term><parameter>--enable-kernel=&min-kernel;</parameter></term>
|
---|
[1f7ca93] | 115 | <listitem>
|
---|
| 116 | <para>This tells Glibc to compile the library with support
|
---|
[70cd9f32] | 117 | for &min-kernel; and later Linux kernels. Workarounds for older
|
---|
[3532721] | 118 | kernels are not enabled.</para>
|
---|
[1f7ca93] | 119 | </listitem>
|
---|
| 120 | </varlistentry>
|
---|
| 121 |
|
---|
| 122 | <varlistentry>
|
---|
| 123 | <term><parameter>--with-headers=/tools/include</parameter></term>
|
---|
| 124 | <listitem>
|
---|
| 125 | <para>This tells Glibc to compile itself against the headers recently
|
---|
| 126 | installed to the tools directory, so that it knows exactly what
|
---|
| 127 | features the kernel has and can optimize itself accordingly.</para>
|
---|
| 128 | </listitem>
|
---|
| 129 | </varlistentry>
|
---|
| 130 |
|
---|
| 131 | <varlistentry>
|
---|
[4e82d47] | 132 | <term><parameter>libc_cv_forced_unwind=yes</parameter></term>
|
---|
[1f7ca93] | 133 | <listitem>
|
---|
[ff9fa3c0] | 134 | <para>The linker installed during
|
---|
| 135 | <xref linkend="ch-tools-binutils-pass1"/> was cross-compiled and as
|
---|
| 136 | such cannot be used until Glibc has been installed. This means that
|
---|
| 137 | the configure test for force-unwind support will fail, as it relies on
|
---|
| 138 | a working linker. The libc_cv_forced_unwind=yes variable is passed in
|
---|
| 139 | order to inform <command>configure</command> that force-unwind
|
---|
| 140 | support is available without it having to run the test.</para>
|
---|
[4e82d47] | 141 | </listitem>
|
---|
| 142 | </varlistentry>
|
---|
| 143 | <varlistentry>
|
---|
| 144 | <term><parameter>libc_cv_c_cleanup=yes</parameter></term>
|
---|
| 145 | <listitem>
|
---|
[ff9fa3c0] | 146 | <para>Simlarly, we pass libc_cv_c_cleanup=yes through to the
|
---|
| 147 | <command>configure</command> script so that the test is skipped and C
|
---|
| 148 | cleanup handling support is configured.</para>
|
---|
[1f7ca93] | 149 | </listitem>
|
---|
| 150 | </varlistentry>
|
---|
[0c0d7c1] | 151 | <varlistentry>
|
---|
| 152 | <term><parameter>libc_cv_ctors_header=yes</parameter></term>
|
---|
| 153 | <listitem>
|
---|
| 154 | <para>Simlarly, we pass libc_cv_ctors_header=yes through to the
|
---|
| 155 | <command>configure</command> script so that the test is skipped and
|
---|
| 156 | gcc constructor support is configured.</para>
|
---|
| 157 | </listitem>
|
---|
| 158 | </varlistentry>
|
---|
[1f7ca93] | 159 |
|
---|
| 160 | </variablelist>
|
---|
| 161 |
|
---|
| 162 | <para>During this stage the following warning might appear:</para>
|
---|
| 163 |
|
---|
| 164 | <blockquote>
|
---|
| 165 | <screen><computeroutput>configure: WARNING:
|
---|
| 166 | *** These auxiliary programs are missing or
|
---|
[81fd230] | 167 | *** incompatible versions: msgfmt
|
---|
| 168 | *** some features will be disabled.
|
---|
[1f7ca93] | 169 | *** Check the INSTALL file for required versions.</computeroutput></screen>
|
---|
| 170 | </blockquote>
|
---|
[81fd230] | 171 |
|
---|
[1f7ca93] | 172 | <para>The missing or incompatible <command>msgfmt</command> program is
|
---|
[5f7456b] | 173 | generally harmless. This <command>msgfmt</command> program is part of the
|
---|
| 174 | Gettext package which the host distribution should provide.</para>
|
---|
[81fd230] | 175 |
|
---|
[1f7ca93] | 176 | <para>Compile the package:</para>
|
---|
[73aedd1d] | 177 |
|
---|
[0445a3d] | 178 | <screen><userinput remap="make">make</userinput></screen>
|
---|
[73aedd1d] | 179 |
|
---|
[0abc697] | 180 | <para>This package does come with a test suite, however, it cannot be
|
---|
| 181 | run at this time because we do not have a C++ compiler yet.</para>
|
---|
[81fd230] | 182 |
|
---|
[ca2f862e] | 183 | <note>
|
---|
| 184 | <para>The test suite also requires locale data to be installed in order to run
|
---|
[90674770] | 185 | successfully. Locale data provides information to the system regarding
|
---|
[ca2f862e] | 186 | such things as the date, time, and currency formats accepted and output by
|
---|
| 187 | system utilities. If the test suites are not being run in this chapter
|
---|
| 188 | (as per the recommendation), there is no need to install the locales now.
|
---|
| 189 | The appropriate locales will be installed in the next chapter. To install
|
---|
| 190 | the Glibc locales anyway, use instructions from <xref
|
---|
| 191 | linkend="ch-system-glibc" role="."/></para>
|
---|
| 192 | </note>
|
---|
| 193 |
|
---|
[1f7ca93] | 194 | <para>Install the package:</para>
|
---|
[73aedd1d] | 195 |
|
---|
[0445a3d] | 196 | <screen><userinput remap="install">make install</userinput></screen>
|
---|
[73aedd1d] | 197 |
|
---|
[1a3e6a3] | 198 | <caution>
|
---|
| 199 | <para>At this point, it is imperative to stop and ensure that the basic
|
---|
| 200 | functions (compiling and linking) of the new toolchain are working as
|
---|
| 201 | expected. To perform a sanity check, run the following commands:</para>
|
---|
| 202 |
|
---|
| 203 | <screen><userinput>echo 'main(){}' > dummy.c
|
---|
| 204 | $LFS_TGT-gcc dummy.c
|
---|
| 205 | readelf -l a.out | grep ': /tools'</userinput></screen>
|
---|
| 206 |
|
---|
| 207 | <para>If everything is working correctly, there should be no errors,
|
---|
| 208 | and the output of the last command will be of the form:</para>
|
---|
| 209 |
|
---|
| 210 | <screen><computeroutput>[Requesting program interpreter: /tools/lib/ld-linux.so.2]</computeroutput></screen>
|
---|
| 211 |
|
---|
| 212 | <para>Note that <filename class="directory">/tools/lib</filename>, or
|
---|
| 213 | <filename class="directory">/tools/lib64</filename> for 64-bit machines
|
---|
| 214 | appears as the prefix of the dynamic linker.</para>
|
---|
| 215 |
|
---|
| 216 | <para>If the output is not shown as above or there was no output at all,
|
---|
| 217 | then something is wrong. Investigate and retrace the steps to find out
|
---|
| 218 | where the problem is and correct it. This issue must be resolved before
|
---|
[1c47f33] | 219 | continuing on.</para>
|
---|
[1a3e6a3] | 220 |
|
---|
| 221 | <para>Once all is well, clean up the test files:</para>
|
---|
| 222 |
|
---|
| 223 | <screen><userinput>rm -v dummy.c a.out</userinput></screen>
|
---|
| 224 |
|
---|
| 225 | </caution>
|
---|
| 226 |
|
---|
[e6ae50d] | 227 | <note><para>Building Binutils in the section after next will serve as an
|
---|
| 228 | additional check that the toolchain has been built properly. If Binutils
|
---|
| 229 | fails to build, it is an indication that something has gone wrong with the
|
---|
| 230 | previous Binutils, GCC, or Glibc installations.</para></note>
|
---|
[1a3e6a3] | 231 |
|
---|
[1f7ca93] | 232 | </sect2>
|
---|
[bc82645e] | 233 |
|
---|
[1f7ca93] | 234 | <sect2 role="content">
|
---|
| 235 | <title/>
|
---|
[81fd230] | 236 |
|
---|
[1f7ca93] | 237 | <para>Details on this package are located in
|
---|
| 238 | <xref linkend="contents-glibc" role="."/></para>
|
---|
| 239 |
|
---|
| 240 | </sect2>
|
---|
[81fd230] | 241 |
|
---|
[1f7ca93] | 242 | </sect1>
|
---|