source: chapter05/glibc.xml@ 38de42d

ml-11.0 multilib
Last change on this file since 38de42d was 38de42d, checked in by Xℹ Ruoyao <xry111@…>, 3 years ago

Merge changes from trunk to multilib

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/branches/multilib@12072 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
  • 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 arch="default">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
58 <para arch="ml_32,ml_x32,ml_all">First, create symbolic links for LSB compliance
59 and compatibility symbolic links required for proper
60 operation of the dynamic library loader:</para>
61
62<!-- no ld-linux.so.2 here as multilib is based on x86_64, not on i686 -->
63<screen arch="ml_32,ml_x32,ml_all"><userinput remap="pre">ln -sfv ../lib/ld-linux-x86-64.so.2 $LFS/lib64
64ln -sfv ../lib/ld-linux-x86-64.so.2 $LFS/lib64/ld-lsb-x86-64.so.3</userinput></screen>
65
66 <para>Some of the Glibc programs use the non-FHS compliant
67 <filename class="directory">/var/db</filename> directory to store their
68 runtime data. Apply the following patch to make such programs store their
69 runtime data in the FHS-compliant locations:</para>
70
71<screen><userinput remap="pre">patch -Np1 -i ../glibc-&glibc-version;-fhs-1.patch</userinput></screen>
72
73 <para>The Glibc documentation recommends building Glibc
74 in a dedicated build directory:</para>
75
76<screen><userinput remap="pre">mkdir -v build
77cd build</userinput></screen>
78
79 <para>Next, prepare Glibc for compilation:</para>
80
81<screen arch="default"><userinput remap="configure">../configure \
82 --prefix=/usr \
83 --host=$LFS_TGT \
84 --build=$(../scripts/config.guess) \
85 --enable-kernel=&min-kernel; \
86 --with-headers=$LFS/usr/include \
87 libc_cv_slibdir=/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 --libdir=/usr/lib \
96 --libexecdir=/usr/lib \
97 libc_cv_slibdir=/lib</userinput></screen>
98<!--
99 libc_cv_forced_unwind=yes \
100 libc_cv_c_cleanup=yes</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=/lib</parameter></term>
135 <listitem>
136 <para>This ensures that the library is installed in /lib instead
137 of the default /lib64 on 64 bit machines.</para>
138 </listitem>
139 </varlistentry>
140
141 </variablelist>
142
143 <para>During this stage the following warning might appear:</para>
144
145 <blockquote>
146<screen><computeroutput>configure: WARNING:
147*** These auxiliary programs are missing or
148*** incompatible versions: msgfmt
149*** some features will be disabled.
150*** Check the INSTALL file for required versions.</computeroutput></screen>
151 </blockquote>
152
153 <para>The missing or incompatible <command>msgfmt</command> program is
154 generally harmless. This <command>msgfmt</command> program is part of the
155 Gettext package which the host distribution should provide.</para>
156
157 <note><para>There have been reports that this package may fail when
158 building as a "parallel make". If this occurs, rerun the make command
159 with a "-j1" option.</para></note>
160
161 <para>Compile the package:</para>
162
163<screen><userinput remap="make">make</userinput></screen>
164
165 <para>Install the package:</para>
166
167 <warning><para>If <envar>LFS</envar> is not properly set, and despite the
168 recommendations, you are building as
169 <systemitem class="username">root</systemitem>, the next command will
170 install the newly built glibc to your host system, which most likely
171 will render it unusable. So double check that the environment is
172 correctly set, before running the following command.</para></warning>
173
174<screen><userinput remap="install">make DESTDIR=$LFS install</userinput></screen>
175
176 <variablelist>
177 <title>The meaning of the <command>make install</command> option:</title>
178
179 <varlistentry>
180 <term><parameter>DESTDIR=$LFS</parameter></term>
181 <listitem>
182 <para>The <envar>DESTDIR</envar> make variable is used by almost all
183 packages to define the location where the package should be
184 installed. If it is not set, it defaults to the root (<filename
185 class="directory">/</filename>) directory. Here we specify that
186 the package be installed in <filename class="directory">$LFS
187 </filename>, which will become the root after <xref linkend=
188 "ch-tools-chroot"/>.</para>
189 </listitem>
190 </varlistentry>
191
192 </variablelist>
193
194 <caution>
195 <para>At this point, it is imperative to stop and ensure that the basic
196 functions (compiling and linking) of the new toolchain are working as
197 expected. To perform a sanity check, run the following commands:</para>
198
199<screen><userinput>echo 'int main(){}' &gt; dummy.c
200$LFS_TGT-gcc dummy.c
201readelf -l a.out | grep '/ld-linux'</userinput></screen>
202
203 <para>If everything is working correctly, there should be no errors,
204 and the output of the last command will be of the form:</para>
205
206<screen><computeroutput>[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]</computeroutput></screen>
207
208 <para arch="default">Note that for 32-bit machines, the interpreter name will be
209 <filename>/lib/ld-linux.so.2</filename>.</para>
210
211 <para>If the output is not shown as above or there was no output at all,
212 then something is wrong. Investigate and retrace the steps to find out
213 where the problem is and correct it. This issue must be resolved before
214 continuing on.</para>
215
216 <para>Once all is well, clean up the test files:</para>
217
218<screen><userinput>rm -v dummy.c a.out</userinput></screen>
219
220 </caution>
221
222 <note><para>Building packages in the next chapter will serve as an
223 additional check that the toolchain has been built properly. If some
224 package, especially binutils-pass2 or gcc-pass2, fails to build, it is
225 an indication that something has gone wrong with the
226 previous Binutils, GCC, or Glibc installations.</para></note>
227
228 <para>Now that our cross-toolchain is complete, finalize the installation
229 of the limits.h header. For doing so, run a utility provided by the GCC
230 developers:</para>
231
232<screen><userinput>$LFS/tools/libexec/gcc/$LFS_TGT/&gcc-version;/install-tools/mkheaders</userinput></screen>
233
234 </sect2>
235
236 <!-- - - - - - - - - - -->
237 <!-- Multilib - 32bit -->
238 <!-- - - - - - - - - - -->
239 <sect2 arch="ml_32,ml_all">
240 <title>Building Glibc - 32bit</title>
241
242 <para>Now recompile for m32. The extracted source can be
243 reused but needs to cleaned before installing the m32
244 version of Glibc.</para>
245
246 <para>Clear the build directory and remove artefacts from
247 previous build:</para>
248
249<screen><userinput remap="pre">make clean
250find .. -name "*.a" -delete</userinput></screen>
251
252 <para>Configure Glibc for m32 with the following commands:</para>
253
254<screen><userinput remap="configure">CC="$LFS_TGT-gcc -m32" \
255CXX="$LFS_TGT-g++ -m32" \
256../configure \
257 --prefix=/usr \
258 --host=$LFS_TGT32 \
259 --build=$(../scripts/config.guess) \
260 --enable-kernel=&min-kernel; \
261 --with-headers=$LFS/usr/include \
262 --enable-multi-arch \
263 --libdir=&usr-lib-m32; \
264 --libexecdir=&usr-lib-m32; \
265 libc_cv_slibdir=&lib-m32;</userinput></screen>
266
267 <para>Compile the package:</para>
268
269<screen><userinput remap="make">make</userinput></screen>
270
271 <para>Install the package:</para>
272
273<screen><userinput remap="install">make DESTDIR=$PWD/DESTDIR install
274cp -a DESTDIR&lib-m32;/* $LFS&lib-m32;/
275cp -a DESTDIR&usr-lib-m32; $LFS/usr/
276install -vm644 DESTDIR/usr/include/gnu/{lib-names,stubs}-32.h \
277 $LFS/usr/include/gnu/
278ln -svf ..&lib-m32;/ld-linux.so.2 $LFS/lib/ld-linux.so.2</userinput></screen>
279
280 <caution>
281 <para>At this point, it is imperative to stop and ensure that the basic
282 functions (compiling and linking) of the new toolchain are working as
283 expected. To perform a sanity check, run the following commands:</para>
284
285<screen><userinput>echo 'int main(){}' &gt; dummy.c
286$LFS_TGT-gcc -m32 dummy.c
287readelf -l a.out | grep '/ld-linux'</userinput></screen>
288
289 <para>If everything is working correctly, there should be no errors,
290 and the output of the last command will be of the form:</para>
291
292<screen><computeroutput>[Requesting program interpreter: /lib/ld-linux.so.2]</computeroutput></screen>
293
294 <para>If the output is not shown as above or there was no output at all,
295 then something is wrong. Investigate and retrace the steps to find out
296 where the problem is and correct it. This issue must be resolved before
297 continuing on.</para>
298
299 <para>Once all is well, clean up the test files:</para>
300
301<screen><userinput>rm -v dummy.c a.out</userinput></screen>
302
303 </caution>
304
305 </sect2><!-- m32 -->
306
307 <!-- - - - - - - - - - -->
308 <!-- Multilib - x32bit -->
309 <!-- - - - - - - - - - -->
310
311 <sect2 arch="ml_x32,ml_all">
312 <title>Building Glibc - x32bit</title>
313
314 <para>Now recompile for mx32. The extracted source can be
315 reused but needs to cleaned before installing the mx32
316 version of Glibc.</para>
317
318 <para>Clear the build directory and remove artefacts from
319 previous build:</para>
320
321<screen><userinput remap="pre">make clean
322find .. -name "*.a" -delete</userinput></screen>
323
324 <para>Configure Glibc for mx32 with the following commands:</para>
325
326<screen><userinput remap="configure">CC="$LFS_TGT-gcc -mx32" \
327CXX="$LFS_TGT-g++ -mx32" \
328../configure \
329 --prefix=/usr \
330 --host=$LFS_TGTX32 \
331 --build=$(../scripts/config.guess) \
332 --enable-kernel=&min-kernel; \
333 --with-headers=$LFS/usr/include \
334 --enable-multi-arch \
335 --libdir=&usr-lib-mx32; \
336 --libexecdir=&usr-lib-mx32; \
337 libc_cv_slibdir=&lib-mx32;</userinput></screen>
338
339 <para>Compile the package:</para>
340
341<screen><userinput remap="make">make</userinput></screen>
342
343 <para>Install the package:</para>
344
345<screen><userinput remap="install">make DESTDIR=$PWD/DESTDIR install
346cp -a DESTDIR&lib-mx32;/* $LFS&lib-mx32;/
347cp -a DESTDIR&usr-lib-mx32; $LFS/usr/
348install -vm644 DESTDIR/usr/include/gnu/{lib-names,stubs}-x32.h \
349 $LFS/usr/include/gnu/
350ln -svf ..&lib-mx32;/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.