source: chapter05/glibc.xml@ cb518e0

xry111/clfs-ng
Last change on this file since cb518e0 was cb518e0, checked in by Xi Ruoyao <xry111@…>, 9 months ago

cross-ng: remove kernel from hostreqs

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