source: chapter05/glibc.xml@ 83528c7

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 7.10 7.10-rc1 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 arm cross-chap5 ml-11.0 multilib nosym 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 83528c7 was 83528c7, checked in by Bruce Dubbs <bdubbs@…>, 6 years ago

Update to binutils-2.27

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

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