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