source: chapter05/glibc.xml@ f33eca9

multilib xry111/multilib
Last change on this file since f33eca9 was f33eca9, checked in by Thomas Trepl <thomas@…>, 3 weeks ago

Linker name depends on target system, not host system

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