source: chapter05/glibc.xml@ a1ad522

multilib-10.1
Last change on this file since a1ad522 was a1ad522, checked in by Thomas Trepl <thomas@…>, 4 years ago

Merge changes from trunk to multilib

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