source: chapter06/glibc-inst.xml@ 7acb4c3

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 11.2 11.2-rc1 11.3 11.3-rc1 12.0 12.0-rc1 12.1 12.1-rc1 6.0 6.1 6.1.1 6.3 6.4 6.5 6.6 6.7 6.8 7.0 7.1 7.2 7.3 7.4 7.5 7.5-systemd 7.6 7.6-systemd 7.7 7.7-systemd 7.8 7.8-systemd 7.9 7.9-systemd 8.0 8.1 8.2 8.3 8.4 9.0 9.1 arm bdubbs/gcc13 ml-11.0 multilib renodr/libudev-from-systemd s6-init trunk v5_0 v5_1 v5_1_1 xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/lfs-next xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/mips64el xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since 7acb4c3 was 7acb4c3, checked in by Alex Gronenwoud <alex@…>, 21 years ago

Bringing order to the presentation of patches.

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

  • Property mode set to 100644
File size: 4.4 KB
RevLine 
[4595a37]1<sect2><title>&nbsp;</title><para>&nbsp;</para></sect2>
2
[6370fa6]3<sect2>
[b7cea6e]4<title>Glibc installation</title>
[6370fa6]5
[96e0ac7]6<para>The Glibc build system is very well self-contained and will install
[d1391f0]7perfectly, even though our compiler specs file and linker are still pointing
8at <filename>/tools</filename>. We cannot adjust the specs and linker before
9the Glibc install, because the Glibc autoconf tests would then give bogus
10results and thus defeat our goal of achieving a clean build.</para>
[96e0ac7]11
[ec0ce9c]12<note><para>The test suite for Glibc in this section is considered
13<emphasis>critical</emphasis>. Our advice is to not skip it under any
14circumstance.</para></note>
[1f53626]15
[a9939e0]16<para>Before starting to build Glibc, remember to unpack the Glibc-linuxthreads
17again inside the <filename>glibc-&glibc-version;</filename> directory, and to
18unset any environment variables that override the default optimization
19flags.</para>
20
21<para>Then apply the same patch we used previously:</para>
[73eac28]22
[7acb4c3]23<para><screen><userinput>patch -Np1 -i ../&glibc-sscanf-patch;</userinput></screen></para>
[73eac28]24
[677aef3]25<para>The Glibc documentation recommends building Glibc outside of the source
26directory in a dedicated build directory:</para>
[a9fb6a45]27
[4a7a683]28<para><screen><userinput>mkdir ../glibc-build
[ada6eeb]29cd ../glibc-build</userinput></screen></para>
[a9fb6a45]30
[96e0ac7]31<para>Now prepare Glibc for compilation:</para>
[a9fb6a45]32
[84a7dc2]33<para><screen><userinput>../glibc-&glibc-version;/configure --prefix=/usr \
[a9fb6a45]34&nbsp;&nbsp;&nbsp;&nbsp;--disable-profile --enable-add-ons \
[1179ee9]35&nbsp;&nbsp;&nbsp;&nbsp;--libexecdir=/usr/bin --with-headers=/usr/include</userinput></screen></para>
[3a3b76e]36
[aa49729]37<para>The meaning of the new configure options:</para>
[7bfad05]38
39<itemizedlist>
[e4b9338]40<listitem><para><userinput>--libexecdir=/usr/bin</userinput>: This will
[d3d229f]41cause the <filename>pt_chown</filename> program to be installed in the
42<filename>/usr/bin</filename> directory.</para></listitem>
[96e0ac7]43
44<listitem><para><userinput>--with-headers=/usr/include</userinput>: This
45ensures that the kernel headers in <filename>/usr/include</filename> are used
46for this build. If you don't pass this switch then the headers from
[148bb04]47<filename>/tools/include</filename> are used which of course is not ideal
[aa49729]48(although they should be identical). Using this switch has the advantage
[96e0ac7]49that you will be informed immediately should you have forgotten to install the
50kernel headers into <filename>/usr/include</filename>.</para></listitem>
[7bfad05]51</itemizedlist>
52
[96e0ac7]53<para>Compile the package:</para>
[7bfad05]54
55<para><screen><userinput>make</userinput></screen></para>
56
[89fcc34]57<para>Test the results:</para>
[a9fb6a45]58
[bc82645e]59<para><screen><userinput>make check</userinput></screen></para>
60
[f861982]61<para>The test suite notes from <xref linkend="ch05-glibc"/> are still very much
62appropriate here. Be sure to refer back there should you have any doubts.</para>
[5331519]63
[96e0ac7]64<para>And install the package:</para>
65
[7bfad05]66<para><screen><userinput>make install</userinput></screen></para>
[a9fb6a45]67
[96e0ac7]68<para>The locales that can make your system respond in a different language
69weren't installed by the above command. Do it with this:</para>
[a9fb6a45]70
71<para><screen><userinput>make localedata/install-locales</userinput></screen></para>
72
[d3d229f]73<para>An alternative to running the previous command is to install only those
[96e0ac7]74locales which you need or want. This can be achieved using the
75<userinput>localedef</userinput> command. Information on this can be found in
76the <filename>INSTALL</filename> file in the
[c825bdc]77<filename>glibc-&glibc-version;</filename> tree. However, there are a number
78of locales that are essential for the tests of future packages to pass
79correctly. The following instructions, in place of the install-locales
80command above, will install the minimum set of locales necessary for the
81tests to run successfully:</para>
82
[223504c]83<para><screen><userinput>mkdir -p /usr/lib/locale
[c825bdc]84localedef -i de_DE -f ISO-8859-1 de_DE
85localedef -i de_DE@euro -f ISO-8859-15 de_DE@euro
86localedef -i en_HK -f ISO-8859-1 en_HK
87localedef -i en_PH -f ISO-8859-1 en_PH
88localedef -i en_US -f ISO-8859-1 en_US
89localedef -i es_MX -f ISO-8859-1 es_MX
90localedef -i fr_FR -f ISO-8859-1 fr_FR
91localedef -i fr_FR@euro -f ISO-8859-15 fr_FR@euro
92localedef -i it_IT -f ISO-8859-1 it_IT
93localedef -i ja_JP -f EUC-JP ja_JP</userinput></screen></para>
[a9fb6a45]94
[96e0ac7]95<para>Finally, build the linuxthreads man pages:</para>
[41d1d0e]96
97<para><screen><userinput>make -C ../glibc-2.3.2/linuxthreads/man</userinput></screen></para>
98
[96e0ac7]99<para>And install these pages:</para>
[41d1d0e]100
101<para><screen><userinput>make -C ../glibc-2.3.2/linuxthreads/man install</userinput></screen></para>
102
[6370fa6]103</sect2>
104
Note: See TracBrowser for help on using the repository browser.