source: chapter05/glibc.xml@ cfb8eea

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

Automatic merge of trunk into multilib

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