source: chapter05/glibc.xml@ 0ebda11

ml-11.0 multilib
Last change on this file since 0ebda11 was 0ebda11, checked in by Thomas Trepl (Moody) <thomas@…>, 7 months ago

Remove entities for multilib pathes
Add usage of libc_cv_rtlddir

  • Property mode set to 100644
File size: 16.3 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>Fix a build issue with gcc-11.1:</para>
69
70<screen><userinput remap="pre">sed 's/amx_/amx-/' -i sysdeps/x86/tst-cpu-features-supports.c</userinput></screen>
71
72 <para>The Glibc documentation recommends building Glibc
73 in a dedicated build directory:</para>
74
75<screen><userinput remap="pre">mkdir -v build
76cd build</userinput></screen>
77
78 <para>Next, prepare Glibc for compilation:</para>
79
80<screen arch="default"><userinput remap="configure">../configure \
81 --prefix=/usr \
82 --host=$LFS_TGT \
83 --build=$(../scripts/config.guess) \
84 --enable-kernel=&min-kernel; \
85 --with-headers=$LFS/usr/include \
86 libc_cv_slibdir=/usr/lib \
87 libc_cv_rtlddir=/usr/lib</userinput></screen>
88<screen arch="ml_32,ml_x32,ml_all"><userinput remap="configure">../configure \
89 --prefix=/usr \
90 --host=$LFS_TGT \
91 --build=$(../scripts/config.guess) \
92 --enable-kernel=&min-kernel; \
93 --with-headers=$LFS/usr/include \
94 --enable-multi-arch \
95 libc_cv_slibdir=/usr/lib \
96 libc_cv_rtlddir=/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 <varlistentry>
138 <term><parameter>libc_cv_rtlddir=/usr/lib</parameter></term>
139 <listitem>
140 <para>Fix hardcoded path to the executable loader in the
141 <command>ldd</command> script.</para>
142 </listitem>
143 </varlistentry>
144
145 <varlistentry>
146 <term><option>libc_cv_include_x86_isa_level=no</option></term>
147 <listitem>
148 <para>This disables <quote>x86 ISA needed</quote> property in
149 Glibc libraries. Use it <emphasis role="bold">if</emphasis>
150 you are building Glibc with <option>-march</option> option in
151 <envar>CFLAGS</envar>, to workaround an issue in Glibc-2.33
152 breaking it.</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 <note><para>There have been reports that this package may fail when
173 building as a "parallel make". If this occurs, rerun the make command
174 with a "-j1" option.</para></note>
175
176 <para>Compile the package:</para>
177
178<screen><userinput remap="make">make</userinput></screen>
179
180 <para>Install the package:</para>
181
182 <warning><para>If <envar>LFS</envar> is not properly set, and despite the
183 recommendations, you are building as
184 <systemitem class="username">root</systemitem>, the next command will
185 install the newly built glibc to your host system, which most likely
186 will render it unusable. So double check that the environment is
187 correctly set, before running the following command.</para></warning>
188
189<screen><userinput remap="install">make DESTDIR=$LFS install</userinput></screen>
190
191 <variablelist>
192 <title>The meaning of the <command>make install</command> option:</title>
193
194 <varlistentry>
195 <term><parameter>DESTDIR=$LFS</parameter></term>
196 <listitem>
197 <para>The <envar>DESTDIR</envar> make variable is used by almost all
198 packages to define the location where the package should be
199 installed. If it is not set, it defaults to the root (<filename
200 class="directory">/</filename>) directory. Here we specify that
201 the package be installed in <filename class="directory">$LFS
202 </filename>, which will become the root after <xref linkend=
203 "ch-tools-chroot"/>.</para>
204 </listitem>
205 </varlistentry>
206
207 </variablelist>
208
209 <!--
210 The /usr which gets removed from the RTLDLIST by the sed
211 below is set by the libc_cv_rtlddir=/usr/lib above. When
212 changing the libc_cv_rtlddir to /lib, the content of the
213 ldd script does not need to be patched, but some other
214 symlinks created by glibc itself will be not that correct
215 and needs to be fixed by other symlinks.
216
217 First setting /usr and than removing /usr seems strange,
218 but it looks like that libc_cv_rtlddir has more effect than
219 only the pathes in ldd (it has influence on which symlinks
220 to the loader are created where) and makes the handling
221 in a multilib environment much easier.
222 To me, it feels better to go the way with adding/removing
223 /usr than to introduce a symlink hell.
224
225 Another option to get ldd working properly is to set a
226 symlink as "ln -svf lib /usr/lib64" but it has been reported
227 that we used that already years ago but dropped it since
228 libtool will complain sometimes with "library has been moved"
229 warnings.
230 Don't know if this is still the case - if not, this one
231 symlink seems to be the cleanest way and the sed on ldd will
232 be obsolete.
233 -->
234 <para>Fix hardcoded path to the executable loader in
235 <command>ldd</command> script:</para>
236
237<screen><userinput remap="install">sed '/RTLDLIST=/s@/usr@@g' -i $LFS/usr/bin/ldd</userinput></screen>
238
239 <caution>
240 <para>At this point, it is imperative to stop and ensure that the basic
241 functions (compiling and linking) of the new toolchain are working as
242 expected. To perform a sanity check, run the following commands:</para>
243
244<screen><userinput>echo 'int main(){}' &gt; dummy.c
245$LFS_TGT-gcc dummy.c
246readelf -l a.out | grep '/ld-linux'</userinput></screen>
247
248 <para>If everything is working correctly, there should be no errors,
249 and the output of the last command will be of the form:</para>
250
251<screen><computeroutput>[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]</computeroutput></screen>
252
253 <para arch="default">Note that for 32-bit machines, the interpreter name will be
254 <filename>/lib/ld-linux.so.2</filename>.</para>
255
256 <para>If the output is not shown as above or there was no output at all,
257 then something is wrong. Investigate and retrace the steps to find out
258 where the problem is and correct it. This issue must be resolved before
259 continuing on.</para>
260
261 <para>Once all is well, clean up the test files:</para>
262
263<screen><userinput>rm -v dummy.c a.out</userinput></screen>
264
265 </caution>
266
267 <note><para>Building packages in the next chapter will serve as an
268 additional check that the toolchain has been built properly. If some
269 package, especially binutils-pass2 or gcc-pass2, fails to build, it is
270 an indication that something has gone wrong with the
271 previous Binutils, GCC, or Glibc installations.</para></note>
272
273 <para>Now that our cross-toolchain is complete, finalize the installation
274 of the limits.h header. For doing so, run a utility provided by the GCC
275 developers:</para>
276
277<screen><userinput>$LFS/tools/libexec/gcc/$LFS_TGT/&gcc-version;/install-tools/mkheaders</userinput></screen>
278
279 </sect2>
280
281 <!-- - - - - - - - - - -->
282 <!-- Multilib - 32bit -->
283 <!-- - - - - - - - - - -->
284 <sect2 arch="ml_32,ml_all">
285 <title>Building Glibc - 32bit</title>
286
287 <para>Now recompile for m32. The extracted source can be
288 reused but needs to be cleaned before installing the m32
289 version of Glibc.</para>
290
291 <para>Clear the build directory and remove artefacts from
292 previous build:</para>
293
294<screen><userinput remap="pre">make clean
295find .. -name "*.a" -delete</userinput></screen>
296
297 <para>Configure Glibc for m32 with the following commands:</para>
298
299<screen><userinput remap="configure">CC="$LFS_TGT-gcc -m32" \
300CXX="$LFS_TGT-g++ -m32" \
301../configure \
302 --prefix=/usr \
303 --host=$LFS_TGT32 \
304 --build=$(../scripts/config.guess) \
305 --enable-kernel=&min-kernel; \
306 --with-headers=$LFS/usr/include \
307 --enable-multi-arch \
308 --libdir=/usr/lib32 \
309 --libexecdir=/usr/lib32 \
310 libc_cv_slibdir=/usr/lib32 \
311 libc_cv_rtlddir=/usr/lib32</userinput></screen>
312
313 <para>Compile the package:</para>
314
315<screen><userinput remap="make">make</userinput></screen>
316
317 <para>Install the package:</para>
318
319<screen><userinput remap="install">make DESTDIR=$PWD/DESTDIR install
320cp -a DESTDIR/usr/lib32 $LFS/usr/
321install -vm644 DESTDIR/usr/include/gnu/{lib-names,stubs}-32.h \
322 $LFS/usr/include/gnu/
323ln -svf ../lib32/ld-linux.so.2 $LFS/lib/ld-linux.so.2</userinput></screen>
324
325
326 <caution>
327 <para>At this point, it is imperative to stop and ensure that the basic
328 functions (compiling and linking) of the new toolchain are working as
329 expected. To perform a sanity check, run the following commands:</para>
330
331<screen><userinput>echo 'int main(){}' &gt; dummy.c
332$LFS_TGT-gcc -m32 dummy.c
333readelf -l a.out | grep '/ld-linux'</userinput></screen>
334
335 <para>If everything is working correctly, there should be no errors,
336 and the output of the last command will be of the form:</para>
337
338<screen><computeroutput>[Requesting program interpreter: /lib/ld-linux.so.2]</computeroutput></screen>
339
340 <para>If the output is not shown as above or there was no output at all,
341 then something is wrong. Investigate and retrace the steps to find out
342 where the problem is and correct it. This issue must be resolved before
343 continuing on.</para>
344
345 <para>Once all is well, clean up the test files:</para>
346
347<screen><userinput>rm -v dummy.c a.out</userinput></screen>
348
349 </caution>
350
351 </sect2><!-- m32 -->
352
353 <!-- - - - - - - - - - -->
354 <!-- Multilib - x32bit -->
355 <!-- - - - - - - - - - -->
356
357 <sect2 arch="ml_x32,ml_all">
358 <title>Building Glibc - x32bit</title>
359
360 <para>Now recompile for mx32. The extracted source can be
361 reused but needs to be cleaned before installing the mx32
362 version of Glibc.</para>
363
364 <para>Clear the build directory and remove artefacts from
365 previous build:</para>
366
367<screen><userinput remap="pre">make clean
368find .. -name "*.a" -delete</userinput></screen>
369
370 <para>Configure Glibc for mx32 with the following commands:</para>
371
372<screen><userinput remap="configure">CC="$LFS_TGT-gcc -mx32" \
373CXX="$LFS_TGT-g++ -mx32" \
374../configure \
375 --prefix=/usr \
376 --host=$LFS_TGTX32 \
377 --build=$(../scripts/config.guess) \
378 --enable-kernel=&min-kernel; \
379 --with-headers=$LFS/usr/include \
380 --enable-multi-arch \
381 --libdir=/usr/libx32 \
382 --libexecdir=/usr/libx32 \
383 libc_cv_slibdir=/usr/libx32 \
384 libc_cv_rtlddir=/usr/libx32</userinput></screen>
385
386 <para>Compile the package:</para>
387
388<screen><userinput remap="make">make</userinput></screen>
389
390 <para>Install the package:</para>
391
392<screen><userinput remap="install">make DESTDIR=$PWD/DESTDIR install
393cp -a DESTDIR/usr/libx32 $LFS/usr/
394install -vm644 DESTDIR/usr/include/gnu/{lib-names,stubs}-x32.h \
395 $LFS/usr/include/gnu/
396ln -svf ../libx32/ld-linux-x32.so.2 $LFS/lib/ld-linux-x32.so.2</userinput></screen>
397
398 <caution>
399 <para>At this point, it is imperative to stop and ensure that the basic
400 functions (compiling and linking) of the new toolchain are working as
401 expected. To perform a sanity check, run the following commands:</para>
402
403<screen><userinput>echo 'int main(){}' &gt; dummy.c
404$LFS_TGT-gcc -mx32 dummy.c
405readelf -l a.out | grep '/ld-linux-x32'</userinput></screen>
406
407 <para>If everything is working correctly, there should be no errors,
408 and the output of the last command will be of the form:</para>
409
410<screen><computeroutput>[Requesting program interpreter: /libx32/ld-linux-x32.so.2]</computeroutput></screen>
411
412 <para>If the output is not shown as above or there was no output at all,
413 then something is wrong. Investigate and retrace the steps to find out
414 where the problem is and correct it. This issue must be resolved before
415 continuing on.</para>
416
417 <para>Once all is well, clean up the test files:</para>
418
419<screen><userinput>rm -v dummy.c a.out</userinput></screen>
420
421 </caution>
422
423 </sect2><!-- mx32 -->
424
425 <sect2 role="content">
426 <title/>
427
428 <para>Details on this package are located in
429 <xref linkend="contents-glibc" role="."/></para>
430
431 </sect2>
432
433</sect1>
Note: See TracBrowser for help on using the repository browser.