source: chapter05/glibc.xml@ 9c31d62

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

MultiLib: Merge changes from trunk

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/branches/multilib@11687 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
  • Property mode set to 100644
File size: 12.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="../chapter06/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-ch5-sbu;</seg>
37 <seg>&glibc-ch5-du;</seg>
38 </seglistitem>
39 </segmentedlist>
40
41 </sect2>
42
43 <sect2 role="installation">
44 <title>Installation of Glibc</title>
45
46 <para>The Glibc documentation recommends building Glibc
47 in a dedicated build directory:</para>
48
49<screen><userinput remap="pre">mkdir -v build
50cd build</userinput></screen>
51
52 <para>Next, prepare Glibc for compilation:</para>
53
54<screen arch="default"><userinput remap="configure">../configure \
55 --prefix=/tools \
56 --host=$LFS_TGT \
57 --build=$(../scripts/config.guess) \
58 --enable-kernel=&min-kernel; \
59 --with-headers=/tools/include</userinput></screen>
60<screen arch="ml_32,ml_x32,ml_all"><userinput remap="configure">../configure \
61 --prefix=/tools \
62 --host=$LFS_TGT \
63 --build=$(../scripts/config.guess) \
64 --enable-kernel=&min-kernel; \
65 --enable-multi-arch \
66 --with-headers=/tools/include</userinput></screen>
67<!--
68 libc_cv_forced_unwind=yes \
69 libc_cv_c_cleanup=yes</userinput></screen> -->
70
71 <variablelist>
72 <title>The meaning of the configure options:</title>
73
74 <varlistentry>
75 <term><parameter>--host=$LFS_TGT, --build=$(../scripts/config.guess)</parameter></term>
76 <listitem>
77 <para>The combined effect of these switches is that Glibc's build system
78 configures itself to cross-compile, using the cross-linker and
79 cross-compiler in <filename class="directory">/tools</filename>.</para>
80 </listitem>
81 </varlistentry>
82
83 <varlistentry>
84 <term><parameter>--enable-kernel=&min-kernel;</parameter></term>
85 <listitem>
86 <para>This tells Glibc to compile the library with support
87 for &min-kernel; and later Linux kernels. Workarounds for older
88 kernels are not enabled.</para>
89 </listitem>
90 </varlistentry>
91
92 <varlistentry arch="ml_32,ml_x32,ml_all">
93 <term><parameter>--enable-multi-arch</parameter></term>
94 <listitem>
95 <para>Enables glibc for multiarch environments.</para>
96 </listitem>
97 </varlistentry>
98
99 <varlistentry>
100 <term><parameter>--with-headers=/tools/include</parameter></term>
101 <listitem>
102 <para>This tells Glibc to compile itself against the headers recently
103 installed to the tools directory, so that it knows exactly what
104 features the kernel has and can optimize itself accordingly.</para>
105 </listitem>
106 </varlistentry>
107<!--
108 <varlistentry>
109 <term><parameter>libc_cv_forced_unwind=yes</parameter></term>
110 <listitem>
111 <para>The linker installed during
112 <xref linkend="ch-tools-binutils-pass1"/> was cross-compiled and as
113 such cannot be used until Glibc has been installed. This means that
114 the configure test for force-unwind support will fail, as it relies on
115 a working linker. The libc_cv_forced_unwind=yes variable is passed in
116 order to inform <command>configure</command> that force-unwind
117 support is available without it having to run the test.</para>
118 </listitem>
119 </varlistentry>
120 <varlistentry>
121 <term><parameter>libc_cv_c_cleanup=yes</parameter></term>
122 <listitem>
123 <para>Similarly, we pass libc_cv_c_cleanup=yes through to the
124 <command>configure</command> script so that the test is skipped and C
125 cleanup handling support is configured.</para>
126 </listitem>
127 </varlistentry>
128-->
129<!-- <varlistentry>
130 <term><parameter>libc_cv_ctors_header=yes</parameter></term>
131 <listitem>
132 <para>Similarly, we pass libc_cv_ctors_header=yes through to the
133 <command>configure</command> script so that the test is skipped and
134 gcc constructor support is configured.</para>
135 </listitem>
136 </varlistentry>-->
137
138 </variablelist>
139
140 <para>During this stage the following warning might appear:</para>
141
142 <blockquote>
143<screen><computeroutput>configure: WARNING:
144*** These auxiliary programs are missing or
145*** incompatible versions: msgfmt
146*** some features will be disabled.
147*** Check the INSTALL file for required versions.</computeroutput></screen>
148 </blockquote>
149
150 <para>The missing or incompatible <command>msgfmt</command> program is
151 generally harmless. This <command>msgfmt</command> program is part of the
152 Gettext package which the host distribution should provide.</para>
153
154 <note><para>There have been reports that this package may fail when
155 building as a "parallel make". If this occurs, rerun the make command
156 with a "-j1" option.</para></note>
157
158 <para>Compile the package:</para>
159
160<screen><userinput remap="make">make</userinput></screen>
161
162 <para>Install the package:</para>
163
164<screen><userinput remap="install">make install</userinput></screen>
165
166 <caution>
167 <para>At this point, it is imperative to stop and ensure that the basic
168 functions (compiling and linking) of the new toolchain are working as
169 expected. To perform a sanity check, run the following commands:</para>
170
171<screen><userinput>echo 'int main(){}' &gt; dummy.c
172$LFS_TGT-gcc dummy.c
173readelf -l a.out | grep ': /tools'</userinput></screen>
174
175 <para>If everything is working correctly, there should be no errors,
176 and the output of the last command will be of the form:</para>
177
178<screen><computeroutput>[Requesting program interpreter: /tools/lib64/ld-linux-x86-64.so.2]</computeroutput></screen>
179
180 <para>Note that for 32-bit machines, the interpreter name will be
181 <filename>/tools/lib/ld-linux.so.2</filename>.</para>
182
183 <para>If the output is not shown as above or there was no output at all,
184 then something is wrong. Investigate and retrace the steps to find out
185 where the problem is and correct it. This issue must be resolved before
186 continuing on.</para>
187
188 <para>Once all is well, clean up the test files:</para>
189
190<screen><userinput>rm -v dummy.c a.out</userinput></screen>
191
192 </caution>
193
194 <note><para>Building Binutils in the section after next will serve as an
195 additional check that the toolchain has been built properly. If Binutils
196 fails to build, it is an indication that something has gone wrong with the
197 previous Binutils, GCC, or Glibc installations.</para></note>
198
199 </sect2>
200
201 <sect2 arch="ml_32,ml_all" role="installation">
202 <title>Installation of Glibc 32-bit</title>
203
204 <para>Clean the build directory for redoing glibc for 32-bit:</para>
205<screen><userinput remap="pre">mkdir ../build32
206cd ../build32</userinput></screen>
207
208 <para>Rebuild glibc for 32-bit:</para>
209<screen><userinput remap="configure">echo slibdir=/tools/lib32 &gt; configparms
210BUILD_CC="gcc -m32" \
211CC="${LFS_TGT}-gcc -m32" \
212CXX="${LFS_TGT}-g++ -m32" \
213AR="${LFS_TGT}-ar" \
214RANLIB="${LFS_TGT}-ranlib" \
215../configure --prefix=/tools \
216 --build=$(../scripts/config.guess) \
217 --host=${LFS_TGT32} \
218 --enable-kernel=&min-kernel; \
219 --enable-multi-arch \
220 --libdir=/tools/lib32 \
221 --libexecdir=/tools/lib32 \
222 --with-headers=/tools/include \
223 --with-binutils=/tools/bin</userinput></screen>
224<!-- \
225 libc_cv_forced_unwind=yes \
226 libc_cv_c_cleanup=yes</userinput></screen> -->
227
228 <para>Now compile the 32-bit version of glibc:</para>
229<screen><userinput remap="make">make</userinput></screen>
230
231 <para>Install 32-bit version of glibc:</para>
232<screen><userinput remap="install">make install_root="${PWD}/DESTDIR" install
233install -vdm755 /tools/lib32
234cp -Rv DESTDIR/tools/lib32/* /tools/lib32
235install -vm644 DESTDIR/tools/include/gnu/{lib-names,stubs}-32.h \
236 /tools/include/gnu/
237ln -svf /tools/lib32/ld-linux.so.2 /tools/lib/
238cd ..</userinput></screen>
239
240 </sect2>
241
242 <sect2 arch="ml_x32,ml_all" role="installation">
243 <title>Installation of Glibc x32-bit</title>
244
245 <para>Create a build directory for redoing glibc for x32-bit:</para>
246<screen><userinput remap="pre">mkdir build32x
247cd build32x</userinput></screen>
248
249 <para>Rebuild glibc for x32-bit:</para>
250<screen><userinput remap="configure">echo slibdir=/tools/libx32 &gt; configparms
251BUILD_CC="gcc -mx32" \
252CC="${LFS_TGT}-gcc -mx32" \
253CXX="${LFS_TGT}-g++ -mx32" \
254AR="${LFS_TGT}-ar" \
255RANLIB="${LFS_TGT}-ranlib" \
256../configure --prefix=/tools \
257 --build=$(../scripts/config.guess) \
258 --host=${LFS_TGTX32} \
259 --enable-kernel=&min-kernel; \
260 --enable-multi-arch \
261 --libdir=/tools/libx32 \
262 --libexecdir=/tools/libx32 \
263 --with-headers=/tools/include \
264 --with-binutils=/tools/bin</userinput></screen>
265<!-- \
266 libc_cv_forced_unwind=yes \
267 libc_cv_c_cleanup=yes</userinput></screen> -->
268
269 <para>Now compile the x32-bit version of glibc:</para>
270<screen><userinput remap="make">make</userinput></screen>
271
272 <para>Install x32-bit version of glibc:</para>
273<screen><userinput remap="install">make install_root="${PWD}/DESTDIR" install
274install -vdm755 /tools/libx32
275cp -Rv DESTDIR/tools/libx32/* /tools/libx32
276install -vm644 DESTDIR/tools/include/gnu/lib-names-x32.h \
277 /tools/include/gnu/
278[ -e DESTDIR/tools/include/gnu/stubs-x32.h ] \
279 &amp;&amp; install -vm644 DESTDIR/tools/include/gnu/stubs-x32.h /tools/include/gnu/ \
280 || ln -v /tools/include/gnu/stubs-64.h /tools/include/gnu/stubs-x32.h
281ln -svf /tools/libx32/ld-linux-x32.so.2 /tools/lib/</userinput></screen>
282<!-- For whatever reason the stubs-x32.h doesn't get created. The 'ln' above is
283just a "brute force" workaraound - by copying the stubs-64.h file. -->
284
285 <caution>
286 <para>At this point, it is imperative to stop and ensure that the basic
287 functions (compiling and linking) of the new toolchain are working as
288 expected. To perform a sanity check, run the following commands:</para>
289
290<screen><userinput>echo 'int main(){}' &gt; dummy.c
291$LFS_TGT-gcc -m32 dummy.c
292readelf -l a.out | grep ': /tools'</userinput></screen>
293
294 <para>If everything is working correctly, there should be no errors,
295 and the output of the last command will be of the form:</para>
296
297<screen><computeroutput>[Requesting program interpreter: /tools/lib/ld-linux.so.2]</computeroutput></screen>
298
299 <para>Redo test for x32-ABI:</para>
300
301<screen><userinput>echo 'int main(){}' &gt; dummy.c
302$LFS_TGT-gcc -mx32 dummy.c
303readelf -l a.out | grep ': /tools'</userinput></screen>
304
305 <para>Output should be like:</para>
306
307<screen><computeroutput>[Requesting program interpreter: /tools/libx32/ld-linux-x32.so.2]</computeroutput></screen>
308
309 <para>If the output is not shown as above or there was no output at all,
310 then something is wrong. Investigate and retrace the steps to find out
311 where the problem is and correct it. This issue must be resolved before
312 continuing on.</para>
313
314 <para>Once all is well, clean up the test files:</para>
315
316<screen><userinput>rm -v dummy.c a.out</userinput></screen>
317
318 </caution>
319 </sect2>
320
321 <sect2 role="content">
322 <title/>
323
324 <para>Details on this package are located in
325 <xref linkend="contents-glibc" role="."/></para>
326
327 </sect2>
328
329</sect1>
Note: See TracBrowser for help on using the repository browser.