source: chapter05/glibc.xml@ c10c983

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 11.1 11.1-rc1 8.4 8.4-rc1 9.0 9.0-rc1 9.1 9.1-rc1 arm cross-chap5 ml-11.0 multilib old-trunk trunk xry111/clfs-ng xry111/git-transition xry111/glibc-2.34 xry111/lfs-next xry111/tester-nohack xry111/usr-move
Last change on this file since c10c983 was c10c983, checked in by Bruce Dubbs <bdubbs@…>, 3 years ago

Simlify instructions for glibc in Chapter 5

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

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