source: chapter05/glibc.xml@ 66bfc2b

ml-11.0 multilib
Last change on this file since 66bfc2b was 66bfc2b, checked in by Thomas Trepl (Moody) <thomas@…>, 3 years ago

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