source: chapter05/glibc.xml@ 7f25c84

11.0 11.0-rc1 11.0-rc2 11.0-rc3 ml-11.0 multilib trunk xry111/glibc-2.34 xry111/tester-nohack
Last change on this file since 7f25c84 was 7f25c84, checked in by Xi Ruoyao <xry111@…>, 7 months ago

glibc: remove libc_cv_rtlddir override for now

Back to use the sed. Need to investigate later.

  • Property mode set to 100644
File size: 9.2 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><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>Some of the Glibc programs use the non-FHS compliant
59 <filename class="directory">/var/db</filename> directory to store their
60 runtime data. Apply the following patch to make such programs store their
61 runtime data in the FHS-compliant locations:</para>
62
63<screen><userinput remap="pre">patch -Np1 -i ../glibc-&glibc-version;-fhs-1.patch</userinput></screen>
64
65 <para>Fix a build issue with gcc-11.1:</para>
66
67<screen><userinput remap="pre">sed 's/amx_/amx-/' -i sysdeps/x86/tst-cpu-features-supports.c</userinput></screen>
68
69 <para>The Glibc documentation recommends building Glibc
70 in a dedicated build directory:</para>
71
72<screen><userinput remap="pre">mkdir -v build
73cd build</userinput></screen>
74
75 <para>Next, prepare Glibc for compilation:</para>
76
77<screen><userinput remap="configure">../configure \
78 --prefix=/usr \
79 --host=$LFS_TGT \
80 --build=$(../scripts/config.guess) \
81 --enable-kernel=&min-kernel; \
82 --with-headers=$LFS/usr/include \
83 libc_cv_slibdir=/usr/lib</userinput></screen>
84
85 <variablelist>
86 <title>The meaning of the configure options:</title>
87
88 <varlistentry>
89 <term><parameter>--host=$LFS_TGT, --build=$(../scripts/config.guess)</parameter></term>
90 <listitem>
91 <para>The combined effect of these switches is that Glibc's build system
92 configures itself to be cross-compiled, using the cross-linker and
93 cross-compiler in <filename class="directory">$LFS/tools</filename>.</para>
94 </listitem>
95 </varlistentry>
96
97 <varlistentry>
98 <term><parameter>--enable-kernel=&min-kernel;</parameter></term>
99 <listitem>
100 <para>This tells Glibc to compile the library with support
101 for &min-kernel; and later Linux kernels. Workarounds for older
102 kernels are not enabled.</para>
103 </listitem>
104 </varlistentry>
105
106 <varlistentry>
107 <term><parameter>--with-headers=$LFS/usr/include</parameter></term>
108 <listitem>
109 <para>This tells Glibc to compile itself against the headers
110 recently installed to the $LFS/usr/include directory, so that
111 it knows exactly what features the kernel has and can optimize
112 itself accordingly.</para>
113 </listitem>
114 </varlistentry>
115
116 <varlistentry>
117 <term><parameter>libc_cv_slibdir=/usr/lib</parameter></term>
118 <listitem>
119 <para>This ensures that the library is installed in /usr/lib instead
120 of the default /lib64 on 64 bit machines.</para>
121 </listitem>
122 </varlistentry>
123
124 <varlistentry>
125 <term><parameter>libc_cv_rtlddir=/usr/lib</parameter></term>
126 <listitem>
127 <para>Fix hardcoded path to the executable loader in the
128 <command>ldd</command> script.</para>
129 </listitem>
130 </varlistentry>
131
132 <varlistentry>
133 <term><option>libc_cv_include_x86_isa_level=no</option></term>
134 <listitem>
135 <para>This disables <quote>x86 ISA needed</quote> property in
136 Glibc libraries. Use it <emphasis role="bold">if</emphasis>
137 you are building Glibc with <option>-march</option> option in
138 <envar>CFLAGS</envar>, to workaround an issue in Glibc-2.33
139 breaking it.</para>
140 </listitem>
141 </varlistentry>
142
143 </variablelist>
144
145 <para>During this stage the following warning might appear:</para>
146
147 <blockquote>
148<screen><computeroutput>configure: WARNING:
149*** These auxiliary programs are missing or
150*** incompatible versions: msgfmt
151*** some features will be disabled.
152*** Check the INSTALL file for required versions.</computeroutput></screen>
153 </blockquote>
154
155 <para>The missing or incompatible <command>msgfmt</command> program is
156 generally harmless. This <command>msgfmt</command> program is part of the
157 Gettext package which the host distribution should provide.</para>
158
159 <note><para>There have been reports that this package may fail when
160 building as a "parallel make". If this occurs, rerun the make command
161 with a "-j1" option.</para></note>
162
163 <para>Compile the package:</para>
164
165<screen><userinput remap="make">make</userinput></screen>
166
167 <para>Install the package:</para>
168
169 <warning><para>If <envar>LFS</envar> is not properly set, and despite the
170 recommendations, you are building as
171 <systemitem class="username">root</systemitem>, the next command will
172 install the newly built glibc to your host system, which most likely
173 will render it unusable. So double check that the environment is
174 correctly set, before running the following command.</para></warning>
175
176<screen><userinput remap="install">make DESTDIR=$LFS install</userinput></screen>
177
178 <variablelist>
179 <title>The meaning of the <command>make install</command> option:</title>
180
181 <varlistentry>
182 <term><parameter>DESTDIR=$LFS</parameter></term>
183 <listitem>
184 <para>The <envar>DESTDIR</envar> make variable is used by almost all
185 packages to define the location where the package should be
186 installed. If it is not set, it defaults to the root (<filename
187 class="directory">/</filename>) directory. Here we specify that
188 the package be installed in <filename class="directory">$LFS
189 </filename>, which will become the root after <xref linkend=
190 "ch-tools-chroot"/>.</para>
191 </listitem>
192 </varlistentry>
193
194 </variablelist>
195
196 <para>Fix hardcoded path to the executable loader in
197 <command>ldd</command> script:</para>
198
199<screen><userinput remap="install">sed '/RTLDLIST=/s@/usr@@g' -i $LFS/usr/bin/ldd</userinput></screen>
200
201 <caution>
202 <para>At this point, it is imperative to stop and ensure that the basic
203 functions (compiling and linking) of the new toolchain are working as
204 expected. To perform a sanity check, run the following commands:</para>
205
206<screen><userinput>echo 'int main(){}' &gt; dummy.c
207$LFS_TGT-gcc dummy.c
208readelf -l a.out | grep '/ld-linux'</userinput></screen>
209
210 <para>If everything is working correctly, there should be no errors,
211 and the output of the last command will be of the form:</para>
212
213<screen><computeroutput>[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]</computeroutput></screen>
214
215 <para>Note that for 32-bit machines, the interpreter name will be
216 <filename>/lib/ld-linux.so.2</filename>.</para>
217
218 <para>If the output is not shown as above or there was no output at all,
219 then something is wrong. Investigate and retrace the steps to find out
220 where the problem is and correct it. This issue must be resolved before
221 continuing on.</para>
222
223 <para>Once all is well, clean up the test files:</para>
224
225<screen><userinput>rm -v dummy.c a.out</userinput></screen>
226
227 </caution>
228
229 <note><para>Building packages in the next chapter will serve as an
230 additional check that the toolchain has been built properly. If some
231 package, especially binutils-pass2 or gcc-pass2, fails to build, it is
232 an indication that something has gone wrong with the
233 previous Binutils, GCC, or Glibc installations.</para></note>
234
235 <para>Now that our cross-toolchain is complete, finalize the installation
236 of the limits.h header. For doing so, run a utility provided by the GCC
237 developers:</para>
238
239<screen><userinput>$LFS/tools/libexec/gcc/$LFS_TGT/&gcc-version;/install-tools/mkheaders</userinput></screen>
240
241 </sect2>
242
243 <sect2 role="content">
244 <title/>
245
246 <para>Details on this package are located in
247 <xref linkend="contents-glibc" role="."/></para>
248
249 </sect2>
250
251</sect1>
Note: See TracBrowser for help on using the repository browser.