source: chapter05/glibc.xml@ a6307b6c

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

restore a note about ln command from LFS 9.x

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@12168 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 8.9 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 <note>
59 <para>
60 The above command is correct. The <command>ln</command> command has
61 a few syntactic versions, so be sure to check
62 <command>info coreutils ln</command> and <filename>ln(1)</filename>
63 before reporting what you may think is an error.
64 </para>
65 </note>
66
67 <para>Some of the Glibc programs use the non-FHS compliant
68 <filename class="directory">/var/db</filename> directory to store their
69 runtime data. Apply the following patch to make such programs store their
70 runtime data in the FHS-compliant locations:</para>
71
72<screen><userinput remap="pre">patch -Np1 -i ../glibc-&glibc-version;-fhs-1.patch</userinput></screen>
73
74 <para>The Glibc documentation recommends building Glibc
75 in a dedicated build directory:</para>
76
77<screen><userinput remap="pre">mkdir -v build
78cd build</userinput></screen>
79
80 <para>Next, prepare Glibc for compilation:</para>
81
82<screen><userinput remap="configure">../configure \
83 --prefix=/usr \
84 --host=$LFS_TGT \
85 --build=$(../scripts/config.guess) \
86 --enable-kernel=&min-kernel; \
87 --with-headers=$LFS/usr/include \
88 libc_cv_slibdir=/lib</userinput></screen>
89<!--
90 libc_cv_forced_unwind=yes \
91 libc_cv_c_cleanup=yes</userinput></screen> -->
92
93 <variablelist>
94 <title>The meaning of the configure options:</title>
95
96 <varlistentry>
97 <term><parameter>--host=$LFS_TGT, --build=$(../scripts/config.guess)</parameter></term>
98 <listitem>
99 <para>The combined effect of these switches is that Glibc's build system
100 configures itself to be cross-compiled, using the cross-linker and
101 cross-compiler in <filename class="directory">$LFS/tools</filename>.</para>
102 </listitem>
103 </varlistentry>
104
105 <varlistentry>
106 <term><parameter>--enable-kernel=&min-kernel;</parameter></term>
107 <listitem>
108 <para>This tells Glibc to compile the library with support
109 for &min-kernel; and later Linux kernels. Workarounds for older
110 kernels are not enabled.</para>
111 </listitem>
112 </varlistentry>
113
114 <varlistentry>
115 <term><parameter>--with-headers=$LFS/usr/include</parameter></term>
116 <listitem>
117 <para>This tells Glibc to compile itself against the headers
118 recently installed to the $LFS/usr/include directory, so that
119 it knows exactly what features the kernel has and can optimize
120 itself accordingly.</para>
121 </listitem>
122 </varlistentry>
123
124 <varlistentry>
125 <term><parameter>libc_cv_slibdir=/lib</parameter></term>
126 <listitem>
127 <para>This ensures that the library is installed in /lib instead
128 of the default /lib64 on 64 bit machines.</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 <caution>
197 <para>At this point, it is imperative to stop and ensure that the basic
198 functions (compiling and linking) of the new toolchain are working as
199 expected. To perform a sanity check, run the following commands:</para>
200
201<screen><userinput>echo 'int main(){}' &gt; dummy.c
202$LFS_TGT-gcc dummy.c
203readelf -l a.out | grep '/ld-linux'</userinput></screen>
204
205 <para>If everything is working correctly, there should be no errors,
206 and the output of the last command will be of the form:</para>
207
208<screen><computeroutput>[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]</computeroutput></screen>
209
210 <para>Note that for 32-bit machines, the interpreter name will be
211 <filename>/lib/ld-linux.so.2</filename>.</para>
212
213 <para>If the output is not shown as above or there was no output at all,
214 then something is wrong. Investigate and retrace the steps to find out
215 where the problem is and correct it. This issue must be resolved before
216 continuing on.</para>
217
218 <para>Once all is well, clean up the test files:</para>
219
220<screen><userinput>rm -v dummy.c a.out</userinput></screen>
221
222 </caution>
223
224 <note><para>Building packages in the next chapter will serve as an
225 additional check that the toolchain has been built properly. If some
226 package, especially binutils-pass2 or gcc-pass2, fails to build, it is
227 an indication that something has gone wrong with the
228 previous Binutils, GCC, or Glibc installations.</para></note>
229
230 <para>Now that our cross-toolchain is complete, finalize the installation
231 of the limits.h header. For doing so, run a utility provided by the GCC
232 developers:</para>
233
234<screen><userinput>$LFS/tools/libexec/gcc/$LFS_TGT/&gcc-version;/install-tools/mkheaders</userinput></screen>
235
236 </sect2>
237
238 <sect2 role="content">
239 <title/>
240
241 <para>Details on this package are located in
242 <xref linkend="contents-glibc" role="."/></para>
243
244 </sect2>
245
246</sect1>
Note: See TracBrowser for help on using the repository browser.