source: chapter05/glibc.xml@ 9c7598c

11.0 11.0-rc1 11.0-rc2 11.0-rc3 11.1 11.1-rc1 arm ml-11.0 multilib trunk xry111/clfs-ng xry111/lfs-next
Last change on this file since 9c7598c was 9c7598c, checked in by Bruce Dubbs <bdubbs@…>, 11 months ago

Package updates.
Update to glibc-2.34.
Update to diffutils-3.8.
Update to libcap-2.52.

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