source: chapter05/glibc.xml@ 9218b05

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 7.10 7.10-rc1 7.9 7.9-rc2 8.0 8.0-rc1 8.1 8.1-rc1 8.1-rc2 8.2 8.2-rc1 8.3 8.3-rc1 8.3-rc2 8.4 8.4-rc1 9.0 9.0-rc1 9.1 9.1-rc1 BOOK.old cross-chap5 ml-11.0 multilib nosym old-trunk trunk xry111/git-transition xry111/glibc-2.34 xry111/tester-nohack xry111/usr-move
Last change on this file since 9218b05 was 9218b05, checked in by Bruce Dubbs <bdubbs@…>, 6 years ago

LFS-7.9-rc2 released.
Update to glibc-2.23.
Update to linux-4.4.2.

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

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