source: chapter05/glibc.xml@ f77b95f

7.8-systemd 7.9-systemd 7.9-systemd-rc1 7.9-systemd-rc2 systemd
Last change on this file since f77b95f was f77b95f, checked in by Douglas R. Reno <renodr@…>, 6 years ago

Update to binutils-2.25.1
Update to check-0.10.0
Update to procps-ng-3.3.11
Update to man-pages-4.02
Update to glibc-2.22
Update to linux-4.1.5
Update to tzdata2015f
XML Cleanups
Add a workaround for ncurses in Chapter 5 to not use mawk if found
Document some test suite failures

git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/systemd@10940 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • 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="../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 outside of the source
47 directory in a dedicated build directory:</para>
48
49<screen><userinput remap="pre">mkdir -v ../glibc-build
50cd ../glibc-build</userinput></screen>
51
52 <para>Next, prepare Glibc for compilation:</para>
53
54<screen><userinput remap="configure">../glibc-&glibc-version;/configure \
55 --prefix=/tools \
56 --host=$LFS_TGT \
57 --build=$(../glibc-&glibc-version;/scripts/config.guess) \
58 --disable-profile \
59 --enable-kernel=&min-kernel; \
60 --enable-obsolete-rpc \
61 --with-headers=/tools/include \
62 libc_cv_forced_unwind=yes \
63 libc_cv_ctors_header=yes \
64 libc_cv_c_cleanup=yes</userinput></screen>
65
66 <variablelist>
67 <title>The meaning of the configure options:</title>
68
69 <varlistentry>
70 <term><parameter>--host=$LFS_TGT, --build=$(../glibc-&glibc-version;/scripts/config.guess)</parameter></term>
71 <listitem>
72 <para>The combined effect of these switches is that Glibc's build system
73 configures itself to cross-compile, using the cross-linker and
74 cross-compiler in <filename class="directory">/tools</filename>.</para>
75 </listitem>
76 </varlistentry>
77
78 <varlistentry>
79 <term><parameter>--disable-profile</parameter></term>
80 <listitem>
81 <para>This builds the libraries without profiling information. Omit
82 this option if profiling on the temporary tools is necessary.</para>
83 </listitem>
84 </varlistentry>
85
86 <varlistentry>
87 <term><parameter>--enable-kernel=&min-kernel;</parameter></term>
88 <listitem>
89 <para>This tells Glibc to compile the library with support
90 for &min-kernel; and later Linux kernels. Workarounds for older
91 kernels are not enabled.</para>
92 </listitem>
93 </varlistentry>
94
95 <varlistentry>
96 <term><parameter>--enable-obsolete-rpc</parameter></term>
97 <listitem>
98 <para>This installs NIS and RPC related headers that are not
99 installed by default. They are required to build GCC and by
100 several BLFS packages.</para>
101 </listitem>
102 </varlistentry>
103
104 <varlistentry>
105 <term><parameter>--with-headers=/tools/include</parameter></term>
106 <listitem>
107 <para>This tells Glibc to compile itself against the headers recently
108 installed to the tools directory, so that it knows exactly what
109 features the kernel has and can optimize itself accordingly.</para>
110 </listitem>
111 </varlistentry>
112
113 <varlistentry>
114 <term><parameter>libc_cv_forced_unwind=yes</parameter></term>
115 <listitem>
116 <para>The linker installed during
117 <xref linkend="ch-tools-binutils-pass1"/> was cross-compiled and as
118 such cannot be used until Glibc has been installed. This means that
119 the configure test for force-unwind support will fail, as it relies on
120 a working linker. The libc_cv_forced_unwind=yes variable is passed in
121 order to inform <command>configure</command> that force-unwind
122 support is available without it having to run the test.</para>
123 </listitem>
124 </varlistentry>
125 <varlistentry>
126 <term><parameter>libc_cv_c_cleanup=yes</parameter></term>
127 <listitem>
128 <para>Simlarly, we pass libc_cv_c_cleanup=yes through to the
129 <command>configure</command> script so that the test is skipped and C
130 cleanup handling support is configured.</para>
131 </listitem>
132 </varlistentry>
133 <varlistentry>
134 <term><parameter>libc_cv_ctors_header=yes</parameter></term>
135 <listitem>
136 <para>Simlarly, we pass libc_cv_ctors_header=yes through to the
137 <command>configure</command> script so that the test is skipped and
138 gcc constructor support is configured.</para>
139 </listitem>
140 </varlistentry>
141
142 </variablelist>
143
144 <para>During this stage the following warning might appear:</para>
145
146 <blockquote>
147<screen><computeroutput>configure: WARNING:
148*** These auxiliary programs are missing or
149*** incompatible versions: msgfmt
150*** some features will be disabled.
151*** Check the INSTALL file for required versions.</computeroutput></screen>
152 </blockquote>
153
154 <para>The missing or incompatible <command>msgfmt</command> program is
155 generally harmless. This <command>msgfmt</command> program is part of the
156 Gettext package which the host distribution should provide.</para>
157
158 <note><para>There have been reports that this package may fail when
159 building as a "parallel make". If this occurs, rerun the make command
160 with a "-j1" option.</para></note>
161
162 <para>Compile the package:</para>
163
164<screen><userinput remap="make">make</userinput></screen>
165
166<!--
167 <para>This package does come with a test suite, however, it cannot be
168 run at this time because we do not have a C++ compiler yet.</para>
169
170 <note>
171 <para>The test suite also requires locale data to be installed in order to run
172 successfully. Locale data provides information to the system regarding
173 such things as the date, time, and currency formats accepted and output by
174 system utilities. If the test suites are not being run in this chapter
175 (as per the recommendation), there is no need to install the locales now.
176 The appropriate locales will be installed in the next chapter. To install
177 the Glibc locales anyway, use instructions from <xref
178 linkend="ch-system-glibc" role="."/></para>
179 </note>
180-->
181 <para>Install the package:</para>
182
183<screen><userinput remap="install">make install</userinput></screen>
184
185 <caution>
186 <para>At this point, it is imperative to stop and ensure that the basic
187 functions (compiling and linking) of the new toolchain are working as
188 expected. To perform a sanity check, run the following commands:</para>
189
190<screen><userinput>echo 'main(){}' &gt; dummy.c
191$LFS_TGT-gcc dummy.c
192readelf -l a.out | grep ': /tools'</userinput></screen>
193
194 <para>If everything is working correctly, there should be no errors,
195 and the output of the last command will be of the form:</para>
196
197<screen><computeroutput>[Requesting program interpreter: /tools/lib/ld-linux.so.2]</computeroutput></screen>
198
199 <para>Note that <filename class="directory">/tools/lib</filename>, or
200 <filename class="directory">/tools/lib64</filename> for 64-bit machines
201 appears as the prefix of the dynamic linker.</para>
202
203 <para>If the output is not shown as above or there was no output at all,
204 then something is wrong. Investigate and retrace the steps to find out
205 where the problem is and correct it. This issue must be resolved before
206 continuing on.</para>
207
208 <para>Once all is well, clean up the test files:</para>
209
210<screen><userinput>rm -v dummy.c a.out</userinput></screen>
211
212 </caution>
213
214 <note><para>Building Binutils in the section after next will serve as an
215 additional check that the toolchain has been built properly. If Binutils
216 fails to build, it is an indication that something has gone wrong with the
217 previous Binutils, GCC, or Glibc installations.</para></note>
218
219 </sect2>
220
221 <sect2 role="content">
222 <title/>
223
224 <para>Details on this package are located in
225 <xref linkend="contents-glibc" role="."/></para>
226
227 </sect2>
228
229</sect1>
Note: See TracBrowser for help on using the repository browser.