source: chapter05/glibc.xml@ b17c6b2b

multilib
Last change on this file since b17c6b2b was d8c9a43f, checked in by Thomas Trepl (Moody) <thomas@…>, 21 months ago

Automatic merge of trunk into multilib

  • Property mode set to 100644
File size: 14.6 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(){}' | gcc -xc -
210readelf -l a.out | grep ld-linux</userinput></screen>
211
212 <para>If everything is working correctly, there should be no errors,
213 and the output of the last command will be of the form:</para>
214
215<screen><computeroutput>[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]</computeroutput></screen>
216
217 <para arch="default">Note that for 32-bit machines, the interpreter name will be
218 <filename>/lib/ld-linux.so.2</filename>.</para>
219
220 <para>If the output is not shown as above or there was no output at all,
221 then something is wrong. Investigate and retrace the steps to find out
222 where the problem is and correct it. This issue must be resolved before
223 continuing on.</para>
224
225 <para>Once all is well, clean up the test file:</para>
226
227<screen><userinput>rm -v a.out</userinput></screen>
228
229 </caution>
230
231 <note><para>Building packages in the next chapter will serve as an
232 additional check that the toolchain has been built properly. If some
233 package, especially binutils-pass2 or gcc-pass2, fails to build, it is
234 an indication that something has gone wrong with the
235 previous Binutils, GCC, or Glibc installations.</para></note>
236
237 <para>Now that our cross-toolchain is complete, finalize the installation
238 of the limits.h header. For doing so, run a utility provided by the GCC
239 developers:</para>
240
241<screen><userinput>$LFS/tools/libexec/gcc/$LFS_TGT/&gcc-version;/install-tools/mkheaders</userinput></screen>
242
243 </sect2>
244
245 <!-- - - - - - - - - - -->
246 <!-- Multilib - 32bit -->
247 <!-- - - - - - - - - - -->
248 <sect2 arch="ml_32,ml_all">
249 <title>Building Glibc - 32bit</title>
250
251 <para>Now recompile for m32. The extracted source can be
252 reused but needs to be cleaned before installing the m32
253 version of Glibc.</para>
254
255 <para>Clear the build directory and remove artefacts from
256 previous build:</para>
257
258<screen><userinput remap="pre">make clean
259find .. -name "*.a" -delete</userinput></screen>
260
261 <para>Configure Glibc for m32 with the following commands:</para>
262
263<screen><userinput remap="configure">CC="$LFS_TGT-gcc -m32" \
264CXX="$LFS_TGT-g++ -m32" \
265../configure \
266 --prefix=/usr \
267 --host=$LFS_TGT32 \
268 --build=$(../scripts/config.guess) \
269 --enable-kernel=&min-kernel; \
270 --with-headers=$LFS/usr/include \
271 --enable-multi-arch \
272 --libdir=/usr/lib32 \
273 --libexecdir=/usr/lib32 \
274 libc_cv_slibdir=/usr/lib32</userinput></screen>
275
276 <para>Compile the package:</para>
277
278<screen><userinput remap="make">make</userinput></screen>
279
280 <para>Install the package:</para>
281
282<screen><userinput remap="install">make DESTDIR=$PWD/DESTDIR install
283cp -a DESTDIR/usr/lib32 $LFS/usr/
284install -vm644 DESTDIR/usr/include/gnu/{lib-names,stubs}-32.h \
285 $LFS/usr/include/gnu/
286ln -svf ../lib32/ld-linux.so.2 $LFS/lib/ld-linux.so.2</userinput></screen>
287
288
289 <caution>
290 <para>At this point, it is imperative to stop and ensure that the basic
291 functions (compiling and linking) of the new toolchain are working as
292 expected. To perform a sanity check, run the following commands:</para>
293
294<screen><userinput>echo 'int main(){}' &gt; dummy.c
295$LFS_TGT-gcc -m32 dummy.c
296readelf -l a.out | grep '/ld-linux'</userinput></screen>
297
298 <para>If everything is working correctly, there should be no errors,
299 and the output of the last command will be of the form:</para>
300
301<screen><computeroutput>[Requesting program interpreter: /lib/ld-linux.so.2]</computeroutput></screen>
302
303 <para>If the output is not shown as above or there was no output at all,
304 then something is wrong. Investigate and retrace the steps to find out
305 where the problem is and correct it. This issue must be resolved before
306 continuing on.</para>
307
308 <para>Once all is well, clean up the test files:</para>
309
310<screen><userinput>rm -v dummy.c a.out</userinput></screen>
311
312 </caution>
313
314 </sect2><!-- m32 -->
315
316 <!-- - - - - - - - - - -->
317 <!-- Multilib - x32bit -->
318 <!-- - - - - - - - - - -->
319
320 <sect2 arch="ml_x32,ml_all">
321 <title>Building Glibc - x32bit</title>
322
323 <para>Now recompile for mx32. The extracted source can be
324 reused but needs to be cleaned before installing the mx32
325 version of Glibc.</para>
326
327 <para>Clear the build directory and remove artefacts from
328 previous build:</para>
329
330<screen><userinput remap="pre">make clean
331find .. -name "*.a" -delete</userinput></screen>
332
333 <para>Configure Glibc for mx32 with the following commands:</para>
334
335<screen><userinput remap="configure">CC="$LFS_TGT-gcc -mx32" \
336CXX="$LFS_TGT-g++ -mx32" \
337../configure \
338 --prefix=/usr \
339 --host=$LFS_TGTX32 \
340 --build=$(../scripts/config.guess) \
341 --enable-kernel=&min-kernel; \
342 --with-headers=$LFS/usr/include \
343 --enable-multi-arch \
344 --libdir=/usr/libx32 \
345 --libexecdir=/usr/libx32 \
346 libc_cv_slibdir=/usr/libx32</userinput></screen>
347
348 <para>Compile the package:</para>
349
350<screen><userinput remap="make">make</userinput></screen>
351
352 <para>Install the package:</para>
353
354<screen><userinput remap="install">make DESTDIR=$PWD/DESTDIR install
355cp -a DESTDIR/usr/libx32 $LFS/usr/
356install -vm644 DESTDIR/usr/include/gnu/{lib-names,stubs}-x32.h \
357 $LFS/usr/include/gnu/
358ln -svf ../libx32/ld-linux-x32.so.2 $LFS/lib/ld-linux-x32.so.2</userinput></screen>
359
360 <caution>
361 <para>At this point, it is imperative to stop and ensure that the basic
362 functions (compiling and linking) of the new toolchain are working as
363 expected. To perform a sanity check, run the following commands:</para>
364
365<screen><userinput>echo 'int main(){}' &gt; dummy.c
366$LFS_TGT-gcc -mx32 dummy.c
367readelf -l a.out | grep '/ld-linux-x32'</userinput></screen>
368
369 <para>If everything is working correctly, there should be no errors,
370 and the output of the last command will be of the form:</para>
371
372<screen><computeroutput>[Requesting program interpreter: /libx32/ld-linux-x32.so.2]</computeroutput></screen>
373
374 <para>If the output is not shown as above or there was no output at all,
375 then something is wrong. Investigate and retrace the steps to find out
376 where the problem is and correct it. This issue must be resolved before
377 continuing on.</para>
378
379 <para>Once all is well, clean up the test files:</para>
380
381<screen><userinput>rm -v dummy.c a.out</userinput></screen>
382
383 </caution>
384
385 </sect2><!-- mx32 -->
386
387 <sect2 role="content">
388 <title/>
389
390 <para>Details on this package are located in
391 <xref linkend="contents-glibc" role="."/></para>
392
393 </sect2>
394
395</sect1>
Note: See TracBrowser for help on using the repository browser.