source: chapter05/glibc.xml@ 051c160

multilib
Last change on this file since 051c160 was 051c160, checked in by Thomas Trepl (Moody) <thomas@…>, 2 years ago

Automatic merge of trunk into multilib

  • Property mode set to 100644
File size: 14.7 KB
Line 
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="../chapter08/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-tmp-sbu;</seg>
37 <seg>&glibc-tmp-du;</seg>
38 </seglistitem>
39 </segmentedlist>
40
41 </sect2>
42
43 <sect2 role="installation">
44 <title>Installation of Glibc</title>
45
46 <para>First, create a symbolic link for LSB compliance. Additionally,
47 for x86_64, create a compatibility symbolic link required for proper
48 operation of the dynamic library loader:</para>
49
50<screen arch="default"><userinput remap="pre">case $(uname -m) in
51 i?86) ln -sfv ld-linux.so.2 $LFS/lib/ld-lsb.so.3
52 ;;
53 x86_64) ln -sfv ../lib/ld-linux-x86-64.so.2 $LFS/lib64
54 ln -sfv ../lib/ld-linux-x86-64.so.2 $LFS/lib64/ld-lsb-x86-64.so.3
55 ;;
56esac</userinput></screen>
57<!-- no ld-linux.so.2 here as multilib is based on x86_64, not on i686 -->
58<screen arch="ml_32,ml_x32,ml_all"><userinput remap="pre">ln -sfv ../lib/ld-linux-x86-64.so.2 $LFS/lib64
59ln -sfv ../lib/ld-linux-x86-64.so.2 $LFS/lib64/ld-lsb-x86-64.so.3</userinput></screen>
60
61 <note>
62 <para>
63 The above command is correct. The <command>ln</command> command has
64 a few syntactic versions, so be sure to check
65 <command>info coreutils ln</command> and <filename>ln(1)</filename>
66 before reporting what you may think is an error.
67 </para>
68 </note>
69
70 <para>Some of the Glibc programs use the non-FHS compliant
71 <filename class="directory">/var/db</filename> directory to store their
72 runtime data. Apply the following patch to make such programs store their
73 runtime data in the FHS-compliant locations:</para>
74
75<screen><userinput remap="pre">patch -Np1 -i ../glibc-&glibc-version;-fhs-1.patch</userinput></screen>
76
77 <para>The Glibc documentation recommends building Glibc
78 in a dedicated build directory:</para>
79
80<screen><userinput remap="pre">mkdir -v build
81cd build</userinput></screen>
82
83 <para>Ensure that the <command>ldconfig</command> and <command>sln</command>
84 utilities are installed into
85 <filename class="directory">/usr/sbin</filename>:</para>
86
87<screen><userinput remap="pre">echo "rootsbindir=/usr/sbin" &gt; configparms</userinput></screen>
88
89 <para>Next, prepare Glibc for compilation:</para>
90
91<screen arch="default"><userinput remap="configure">../configure \
92 --prefix=/usr \
93 --host=$LFS_TGT \
94 --build=$(../scripts/config.guess) \
95 --enable-kernel=&min-kernel; \
96 --with-headers=$LFS/usr/include \
97 libc_cv_slibdir=/usr/lib</userinput></screen>
98<screen arch="ml_32,ml_x32,ml_all"><userinput remap="configure">../configure \
99 --prefix=/usr \
100 --host=$LFS_TGT \
101 --build=$(../scripts/config.guess) \
102 --enable-kernel=&min-kernel; \
103 --with-headers=$LFS/usr/include \
104 --enable-multi-arch \
105 libc_cv_slibdir=/usr/lib</userinput></screen>
106
107 <variablelist>
108 <title>The meaning of the configure options:</title>
109
110 <varlistentry>
111 <term><parameter>--host=$LFS_TGT, --build=$(../scripts/config.guess)</parameter></term>
112 <listitem>
113 <para>The combined effect of these switches is that Glibc's build system
114 configures itself to be cross-compiled, using the cross-linker and
115 cross-compiler in <filename class="directory">$LFS/tools</filename>.</para>
116 </listitem>
117 </varlistentry>
118
119 <varlistentry>
120 <term><parameter>--enable-kernel=&min-kernel;</parameter></term>
121 <listitem>
122 <para>This tells Glibc to compile the library with support
123 for &min-kernel; and later Linux kernels. Workarounds for older
124 kernels are not enabled.</para>
125 </listitem>
126 </varlistentry>
127
128 <varlistentry>
129 <term><parameter>--with-headers=$LFS/usr/include</parameter></term>
130 <listitem>
131 <para>This tells Glibc to compile itself against the headers
132 recently installed to the $LFS/usr/include directory, so that
133 it knows exactly what features the kernel has and can optimize
134 itself accordingly.</para>
135 </listitem>
136 </varlistentry>
137
138 <varlistentry>
139 <term><parameter>libc_cv_slibdir=/usr/lib</parameter></term>
140 <listitem>
141 <para>This ensures that the library is installed in /usr/lib instead
142 of the default /lib64 on 64 bit machines.</para>
143 </listitem>
144 </varlistentry>
145
146 </variablelist>
147
148 <para>During this stage the following warning might appear:</para>
149
150 <blockquote>
151<screen><computeroutput>configure: WARNING:
152*** These auxiliary programs are missing or
153*** incompatible versions: msgfmt
154*** some features will be disabled.
155*** Check the INSTALL file for required versions.</computeroutput></screen>
156 </blockquote>
157
158 <para>The missing or incompatible <command>msgfmt</command> program is
159 generally harmless. This <command>msgfmt</command> program is part of the
160 Gettext package which the host distribution should provide.</para>
161
162 <note><para>There have been reports that this package may fail when
163 building as a "parallel make". If this occurs, rerun the make command
164 with a "-j1" option.</para></note>
165
166 <para>Compile the package:</para>
167
168<screen><userinput remap="make">make</userinput></screen>
169
170 <para>Install the package:</para>
171
172 <warning><para>If <envar>LFS</envar> is not properly set, and despite the
173 recommendations, you are building as
174 <systemitem class="username">root</systemitem>, the next command will
175 install the newly built glibc to your host system, which most likely
176 will render it unusable. So double check that the environment is
177 correctly set, before running the following command.</para></warning>
178
179<screen><userinput remap="install">make DESTDIR=$LFS install</userinput></screen>
180
181 <variablelist>
182 <title>The meaning of the <command>make install</command> option:</title>
183
184 <varlistentry>
185 <term><parameter>DESTDIR=$LFS</parameter></term>
186 <listitem>
187 <para>The <envar>DESTDIR</envar> make variable is used by almost all
188 packages to define the location where the package should be
189 installed. If it is not set, it defaults to the root (<filename
190 class="directory">/</filename>) directory. Here we specify that
191 the package be installed in <filename class="directory">$LFS
192 </filename>, which will become the root after <xref linkend=
193 "ch-tools-chroot"/>.</para>
194 </listitem>
195 </varlistentry>
196
197 </variablelist>
198
199 <para>Fix hardcoded path to the executable loader in
200 <command>ldd</command> script:</para>
201
202<screen><userinput remap="install">sed '/RTLDLIST=/s@/usr@@g' -i $LFS/usr/bin/ldd</userinput></screen>
203
204 <caution>
205 <para>At this point, it is imperative to stop and ensure that the basic
206 functions (compiling and linking) of the new toolchain are working as
207 expected. To perform a sanity check, run the following commands:</para>
208
209<screen><userinput>echo 'int main(){}' &gt; dummy.c
210$LFS_TGT-gcc dummy.c
211readelf -l a.out | grep '/ld-linux'</userinput></screen>
212
213 <para>If everything is working correctly, there should be no errors,
214 and the output of the last command will be of the form:</para>
215
216<screen><computeroutput>[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]</computeroutput></screen>
217
218 <para arch="default">Note that for 32-bit machines, the interpreter name will be
219 <filename>/lib/ld-linux.so.2</filename>.</para>
220
221 <para>If the output is not shown as above or there was no output at all,
222 then something is wrong. Investigate and retrace the steps to find out
223 where the problem is and correct it. This issue must be resolved before
224 continuing on.</para>
225
226 <para>Once all is well, clean up the test files:</para>
227
228<screen><userinput>rm -v dummy.c a.out</userinput></screen>
229
230 </caution>
231
232 <note><para>Building packages in the next chapter will serve as an
233 additional check that the toolchain has been built properly. If some
234 package, especially binutils-pass2 or gcc-pass2, fails to build, it is
235 an indication that something has gone wrong with the
236 previous Binutils, GCC, or Glibc installations.</para></note>
237
238 <para>Now that our cross-toolchain is complete, finalize the installation
239 of the limits.h header. For doing so, run a utility provided by the GCC
240 developers:</para>
241
242<screen><userinput>$LFS/tools/libexec/gcc/$LFS_TGT/&gcc-version;/install-tools/mkheaders</userinput></screen>
243
244 </sect2>
245
246 <!-- - - - - - - - - - -->
247 <!-- Multilib - 32bit -->
248 <!-- - - - - - - - - - -->
249 <sect2 arch="ml_32,ml_all">
250 <title>Building Glibc - 32bit</title>
251
252 <para>Now recompile for m32. The extracted source can be
253 reused but needs to be cleaned before installing the m32
254 version of Glibc.</para>
255
256 <para>Clear the build directory and remove artefacts from
257 previous build:</para>
258
259<screen><userinput remap="pre">make clean
260find .. -name "*.a" -delete</userinput></screen>
261
262 <para>Configure Glibc for m32 with the following commands:</para>
263
264<screen><userinput remap="configure">CC="$LFS_TGT-gcc -m32" \
265CXX="$LFS_TGT-g++ -m32" \
266../configure \
267 --prefix=/usr \
268 --host=$LFS_TGT32 \
269 --build=$(../scripts/config.guess) \
270 --enable-kernel=&min-kernel; \
271 --with-headers=$LFS/usr/include \
272 --enable-multi-arch \
273 --libdir=/usr/lib32 \
274 --libexecdir=/usr/lib32 \
275 libc_cv_slibdir=/usr/lib32</userinput></screen>
276
277 <para>Compile the package:</para>
278
279<screen><userinput remap="make">make</userinput></screen>
280
281 <para>Install the package:</para>
282
283<screen><userinput remap="install">make DESTDIR=$PWD/DESTDIR install
284cp -a DESTDIR/usr/lib32 $LFS/usr/
285install -vm644 DESTDIR/usr/include/gnu/{lib-names,stubs}-32.h \
286 $LFS/usr/include/gnu/
287ln -svf ../lib32/ld-linux.so.2 $LFS/lib/ld-linux.so.2</userinput></screen>
288
289
290 <caution>
291 <para>At this point, it is imperative to stop and ensure that the basic
292 functions (compiling and linking) of the new toolchain are working as
293 expected. To perform a sanity check, run the following commands:</para>
294
295<screen><userinput>echo 'int main(){}' &gt; dummy.c
296$LFS_TGT-gcc -m32 dummy.c
297readelf -l a.out | grep '/ld-linux'</userinput></screen>
298
299 <para>If everything is working correctly, there should be no errors,
300 and the output of the last command will be of the form:</para>
301
302<screen><computeroutput>[Requesting program interpreter: /lib/ld-linux.so.2]</computeroutput></screen>
303
304 <para>If the output is not shown as above or there was no output at all,
305 then something is wrong. Investigate and retrace the steps to find out
306 where the problem is and correct it. This issue must be resolved before
307 continuing on.</para>
308
309 <para>Once all is well, clean up the test files:</para>
310
311<screen><userinput>rm -v dummy.c a.out</userinput></screen>
312
313 </caution>
314
315 </sect2><!-- m32 -->
316
317 <!-- - - - - - - - - - -->
318 <!-- Multilib - x32bit -->
319 <!-- - - - - - - - - - -->
320
321 <sect2 arch="ml_x32,ml_all">
322 <title>Building Glibc - x32bit</title>
323
324 <para>Now recompile for mx32. The extracted source can be
325 reused but needs to be cleaned before installing the mx32
326 version of Glibc.</para>
327
328 <para>Clear the build directory and remove artefacts from
329 previous build:</para>
330
331<screen><userinput remap="pre">make clean
332find .. -name "*.a" -delete</userinput></screen>
333
334 <para>Configure Glibc for mx32 with the following commands:</para>
335
336<screen><userinput remap="configure">CC="$LFS_TGT-gcc -mx32" \
337CXX="$LFS_TGT-g++ -mx32" \
338../configure \
339 --prefix=/usr \
340 --host=$LFS_TGTX32 \
341 --build=$(../scripts/config.guess) \
342 --enable-kernel=&min-kernel; \
343 --with-headers=$LFS/usr/include \
344 --enable-multi-arch \
345 --libdir=/usr/libx32 \
346 --libexecdir=/usr/libx32 \
347 libc_cv_slibdir=/usr/libx32</userinput></screen>
348
349 <para>Compile the package:</para>
350
351<screen><userinput remap="make">make</userinput></screen>
352
353 <para>Install the package:</para>
354
355<screen><userinput remap="install">make DESTDIR=$PWD/DESTDIR install
356cp -a DESTDIR/usr/libx32 $LFS/usr/
357install -vm644 DESTDIR/usr/include/gnu/{lib-names,stubs}-x32.h \
358 $LFS/usr/include/gnu/
359ln -svf ../libx32/ld-linux-x32.so.2 $LFS/lib/ld-linux-x32.so.2</userinput></screen>
360
361 <caution>
362 <para>At this point, it is imperative to stop and ensure that the basic
363 functions (compiling and linking) of the new toolchain are working as
364 expected. To perform a sanity check, run the following commands:</para>
365
366<screen><userinput>echo 'int main(){}' &gt; dummy.c
367$LFS_TGT-gcc -mx32 dummy.c
368readelf -l a.out | grep '/ld-linux-x32'</userinput></screen>
369
370 <para>If everything is working correctly, there should be no errors,
371 and the output of the last command will be of the form:</para>
372
373<screen><computeroutput>[Requesting program interpreter: /libx32/ld-linux-x32.so.2]</computeroutput></screen>
374
375 <para>If the output is not shown as above or there was no output at all,
376 then something is wrong. Investigate and retrace the steps to find out
377 where the problem is and correct it. This issue must be resolved before
378 continuing on.</para>
379
380 <para>Once all is well, clean up the test files:</para>
381
382<screen><userinput>rm -v dummy.c a.out</userinput></screen>
383
384 </caution>
385
386 </sect2><!-- mx32 -->
387
388 <sect2 role="content">
389 <title/>
390
391 <para>Details on this package are located in
392 <xref linkend="contents-glibc" role="."/></para>
393
394 </sect2>
395
396</sect1>
Note: See TracBrowser for help on using the repository browser.