| 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="../chapter08/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-tmp-sbu;</seg>
|
|---|
| 37 | <seg>&glibc-tmp-du;</seg>
|
|---|
| 38 | </seglistitem>
|
|---|
| 39 | </segmentedlist>
|
|---|
| 40 |
|
|---|
| 41 | </sect2>
|
|---|
| 42 |
|
|---|
| 43 | <sect2 role="installation">
|
|---|
| 44 | <title>Installation of Glibc</title>
|
|---|
| 45 |
|
|---|
| 46 | <para>First, create a symbolic link for LSB compliance. Additionally,
|
|---|
| 47 | for x86_64, create a compatibility symbolic link required for proper
|
|---|
| 48 | operation of the dynamic library loader:</para>
|
|---|
| 49 |
|
|---|
| 50 | <screen arch="default"><userinput remap="pre">case $(uname -m) in
|
|---|
| 51 | i?86) ln -sfv ld-linux.so.2 $LFS/lib/ld-lsb.so.3
|
|---|
| 52 | ;;
|
|---|
| 53 | x86_64) ln -sfv ../lib/ld-linux-x86-64.so.2 $LFS/lib64
|
|---|
| 54 | ln -sfv ../lib/ld-linux-x86-64.so.2 $LFS/lib64/ld-lsb-x86-64.so.3
|
|---|
| 55 | ;;
|
|---|
| 56 | esac</userinput></screen>
|
|---|
| 57 | <!-- no ld-linux.so.2 here as multilib is based on x86_64, not on i686 -->
|
|---|
| 58 | <screen arch="ml_32,ml_x32,ml_all"><userinput remap="pre">ln -sfv ../lib/ld-linux-x86-64.so.2 $LFS/lib64
|
|---|
| 59 | ln -sfv ../lib/ld-linux-x86-64.so.2 $LFS/lib64/ld-lsb-x86-64.so.3</userinput></screen>
|
|---|
| 60 |
|
|---|
| 61 | <para>Some of the Glibc programs use the non-FHS compliant
|
|---|
| 62 | <filename class="directory">/var/db</filename> directory to store their
|
|---|
| 63 | runtime data. Apply the following patch to make such programs store their
|
|---|
| 64 | runtime data in the FHS-compliant locations:</para>
|
|---|
| 65 |
|
|---|
| 66 | <screen><userinput remap="pre">patch -Np1 -i ../glibc-&glibc-version;-fhs-1.patch</userinput></screen>
|
|---|
| 67 |
|
|---|
| 68 | <para>Fix a build issue with gcc-11.1:</para>
|
|---|
| 69 |
|
|---|
| 70 | <screen><userinput remap="pre">sed 's/amx_/amx-/' -i sysdeps/x86/tst-cpu-features-supports.c</userinput></screen>
|
|---|
| 71 |
|
|---|
| 72 | <para>The Glibc documentation recommends building Glibc
|
|---|
| 73 | in a dedicated build directory:</para>
|
|---|
| 74 |
|
|---|
| 75 | <screen><userinput remap="pre">mkdir -v build
|
|---|
| 76 | cd build</userinput></screen>
|
|---|
| 77 |
|
|---|
| 78 | <para>Next, prepare Glibc for compilation:</para>
|
|---|
| 79 |
|
|---|
| 80 | <screen arch="default"><userinput remap="configure">../configure \
|
|---|
| 81 | --prefix=/usr \
|
|---|
| 82 | --host=$LFS_TGT \
|
|---|
| 83 | --build=$(../scripts/config.guess) \
|
|---|
| 84 | --enable-kernel=&min-kernel; \
|
|---|
| 85 | --with-headers=$LFS/usr/include \
|
|---|
| 86 | libc_cv_slibdir=/usr/lib</userinput></screen>
|
|---|
| 87 | <screen arch="ml_32,ml_x32,ml_all"><userinput remap="configure">../configure \
|
|---|
| 88 | --prefix=/usr \
|
|---|
| 89 | --host=$LFS_TGT \
|
|---|
| 90 | --build=$(../scripts/config.guess) \
|
|---|
| 91 | --enable-kernel=&min-kernel; \
|
|---|
| 92 | --with-headers=$LFS/usr/include \
|
|---|
| 93 | --enable-multi-arch \
|
|---|
| 94 | libc_cv_slibdir=/usr/lib</userinput></screen>
|
|---|
| 95 |
|
|---|
| 96 | <variablelist>
|
|---|
| 97 | <title>The meaning of the configure options:</title>
|
|---|
| 98 |
|
|---|
| 99 | <varlistentry>
|
|---|
| 100 | <term><parameter>--host=$LFS_TGT, --build=$(../scripts/config.guess)</parameter></term>
|
|---|
| 101 | <listitem>
|
|---|
| 102 | <para>The combined effect of these switches is that Glibc's build system
|
|---|
| 103 | configures itself to be cross-compiled, using the cross-linker and
|
|---|
| 104 | cross-compiler in <filename class="directory">$LFS/tools</filename>.</para>
|
|---|
| 105 | </listitem>
|
|---|
| 106 | </varlistentry>
|
|---|
| 107 |
|
|---|
| 108 | <varlistentry>
|
|---|
| 109 | <term><parameter>--enable-kernel=&min-kernel;</parameter></term>
|
|---|
| 110 | <listitem>
|
|---|
| 111 | <para>This tells Glibc to compile the library with support
|
|---|
| 112 | for &min-kernel; and later Linux kernels. Workarounds for older
|
|---|
| 113 | kernels are not enabled.</para>
|
|---|
| 114 | </listitem>
|
|---|
| 115 | </varlistentry>
|
|---|
| 116 |
|
|---|
| 117 | <varlistentry>
|
|---|
| 118 | <term><parameter>--with-headers=$LFS/usr/include</parameter></term>
|
|---|
| 119 | <listitem>
|
|---|
| 120 | <para>This tells Glibc to compile itself against the headers
|
|---|
| 121 | recently installed to the $LFS/usr/include directory, so that
|
|---|
| 122 | it knows exactly what features the kernel has and can optimize
|
|---|
| 123 | itself accordingly.</para>
|
|---|
| 124 | </listitem>
|
|---|
| 125 | </varlistentry>
|
|---|
| 126 |
|
|---|
| 127 | <varlistentry>
|
|---|
| 128 | <term><parameter>libc_cv_slibdir=/usr/lib</parameter></term>
|
|---|
| 129 | <listitem>
|
|---|
| 130 | <para>This ensures that the library is installed in /usr/lib instead
|
|---|
| 131 | of the default /lib64 on 64 bit machines.</para>
|
|---|
| 132 | </listitem>
|
|---|
| 133 | </varlistentry>
|
|---|
| 134 |
|
|---|
| 135 | <varlistentry>
|
|---|
| 136 | <term><option>libc_cv_include_x86_isa_level=no</option></term>
|
|---|
| 137 | <listitem>
|
|---|
| 138 | <para>This disables <quote>x86 ISA needed</quote> property in
|
|---|
| 139 | Glibc libraries. Use it <emphasis role="bold">if</emphasis>
|
|---|
| 140 | you are building Glibc with <option>-march</option> option in
|
|---|
| 141 | <envar>CFLAGS</envar>, to workaround an issue in Glibc-2.33
|
|---|
| 142 | breaking it.</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 | <para>Install the package:</para>
|
|---|
| 171 |
|
|---|
| 172 | <warning><para>If <envar>LFS</envar> is not properly set, and despite the
|
|---|
| 173 | recommendations, you are building as
|
|---|
| 174 | <systemitem class="username">root</systemitem>, the next command will
|
|---|
| 175 | install the newly built glibc to your host system, which most likely
|
|---|
| 176 | will render it unusable. So double check that the environment is
|
|---|
| 177 | correctly set, before running the following command.</para></warning>
|
|---|
| 178 |
|
|---|
| 179 | <screen><userinput remap="install">make DESTDIR=$LFS install</userinput></screen>
|
|---|
| 180 |
|
|---|
| 181 | <variablelist>
|
|---|
| 182 | <title>The meaning of the <command>make install</command> option:</title>
|
|---|
| 183 |
|
|---|
| 184 | <varlistentry>
|
|---|
| 185 | <term><parameter>DESTDIR=$LFS</parameter></term>
|
|---|
| 186 | <listitem>
|
|---|
| 187 | <para>The <envar>DESTDIR</envar> make variable is used by almost all
|
|---|
| 188 | packages to define the location where the package should be
|
|---|
| 189 | installed. If it is not set, it defaults to the root (<filename
|
|---|
| 190 | class="directory">/</filename>) directory. Here we specify that
|
|---|
| 191 | the package be installed in <filename class="directory">$LFS
|
|---|
| 192 | </filename>, which will become the root after <xref linkend=
|
|---|
| 193 | "ch-tools-chroot"/>.</para>
|
|---|
| 194 | </listitem>
|
|---|
| 195 | </varlistentry>
|
|---|
| 196 |
|
|---|
| 197 | </variablelist>
|
|---|
| 198 |
|
|---|
| 199 | <caution>
|
|---|
| 200 | <para>At this point, it is imperative to stop and ensure that the basic
|
|---|
| 201 | functions (compiling and linking) of the new toolchain are working as
|
|---|
| 202 | expected. To perform a sanity check, run the following commands:</para>
|
|---|
| 203 |
|
|---|
| 204 | <screen><userinput>echo 'int main(){}' > dummy.c
|
|---|
| 205 | $LFS_TGT-gcc dummy.c
|
|---|
| 206 | readelf -l a.out | grep '/ld-linux'</userinput></screen>
|
|---|
| 207 |
|
|---|
| 208 | <para>If everything is working correctly, there should be no errors,
|
|---|
| 209 | and the output of the last command will be of the form:</para>
|
|---|
| 210 |
|
|---|
| 211 | <screen><computeroutput>[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]</computeroutput></screen>
|
|---|
| 212 |
|
|---|
| 213 | <para arch="default">Note that for 32-bit machines, the interpreter name will be
|
|---|
| 214 | <filename>/lib/ld-linux.so.2</filename>.</para>
|
|---|
| 215 |
|
|---|
| 216 | <para>If the output is not shown as above or there was no output at all,
|
|---|
| 217 | then something is wrong. Investigate and retrace the steps to find out
|
|---|
| 218 | where the problem is and correct it. This issue must be resolved before
|
|---|
| 219 | continuing on.</para>
|
|---|
| 220 |
|
|---|
| 221 | <para>Once all is well, clean up the test files:</para>
|
|---|
| 222 |
|
|---|
| 223 | <screen><userinput>rm -v dummy.c a.out</userinput></screen>
|
|---|
| 224 |
|
|---|
| 225 | </caution>
|
|---|
| 226 |
|
|---|
| 227 | <note><para>Building packages in the next chapter will serve as an
|
|---|
| 228 | additional check that the toolchain has been built properly. If some
|
|---|
| 229 | package, especially binutils-pass2 or gcc-pass2, fails to build, it is
|
|---|
| 230 | an indication that something has gone wrong with the
|
|---|
| 231 | previous Binutils, GCC, or Glibc installations.</para></note>
|
|---|
| 232 |
|
|---|
| 233 | <para>Now that our cross-toolchain is complete, finalize the installation
|
|---|
| 234 | of the limits.h header. For doing so, run a utility provided by the GCC
|
|---|
| 235 | developers:</para>
|
|---|
| 236 |
|
|---|
| 237 | <screen><userinput>$LFS/tools/libexec/gcc/$LFS_TGT/&gcc-version;/install-tools/mkheaders</userinput></screen>
|
|---|
| 238 |
|
|---|
| 239 | </sect2>
|
|---|
| 240 |
|
|---|
| 241 | <!-- - - - - - - - - - -->
|
|---|
| 242 | <!-- Multilib - 32bit -->
|
|---|
| 243 | <!-- - - - - - - - - - -->
|
|---|
| 244 | <sect2 arch="ml_32,ml_all">
|
|---|
| 245 | <title>Building Glibc - 32bit</title>
|
|---|
| 246 |
|
|---|
| 247 | <para>Now recompile for m32. The extracted source can be
|
|---|
| 248 | reused but needs to cleaned before installing the m32
|
|---|
| 249 | version of Glibc.</para>
|
|---|
| 250 |
|
|---|
| 251 | <para>Clear the build directory and remove artefacts from
|
|---|
| 252 | previous build:</para>
|
|---|
| 253 |
|
|---|
| 254 | <screen><userinput remap="pre">make clean
|
|---|
| 255 | find .. -name "*.a" -delete</userinput></screen>
|
|---|
| 256 |
|
|---|
| 257 | <para>Configure Glibc for m32 with the following commands:</para>
|
|---|
| 258 |
|
|---|
| 259 | <screen><userinput remap="configure">CC="$LFS_TGT-gcc -m32" \
|
|---|
| 260 | CXX="$LFS_TGT-g++ -m32" \
|
|---|
| 261 | ../configure \
|
|---|
| 262 | --prefix=/usr \
|
|---|
| 263 | --host=$LFS_TGT32 \
|
|---|
| 264 | --build=$(../scripts/config.guess) \
|
|---|
| 265 | --enable-kernel=&min-kernel; \
|
|---|
| 266 | --with-headers=$LFS/usr/include \
|
|---|
| 267 | --enable-multi-arch \
|
|---|
| 268 | --libdir=&usr-lib-m32; \
|
|---|
| 269 | --libexecdir=&usr-lib-m32; \
|
|---|
| 270 | libc_cv_slibdir=&usr-lib-m32;</userinput></screen>
|
|---|
| 271 |
|
|---|
| 272 | <para>Compile the package:</para>
|
|---|
| 273 |
|
|---|
| 274 | <screen><userinput remap="make">make</userinput></screen>
|
|---|
| 275 |
|
|---|
| 276 | <para>Install the package:</para>
|
|---|
| 277 |
|
|---|
| 278 | <screen><userinput remap="install">make DESTDIR=$PWD/DESTDIR install
|
|---|
| 279 | cp -a DESTDIR&lib-m32;/* $LFS&lib-m32;/
|
|---|
| 280 | cp -a DESTDIR&usr-lib-m32; $LFS/usr/
|
|---|
| 281 | install -vm644 DESTDIR/usr/include/gnu/{lib-names,stubs}-32.h \
|
|---|
| 282 | $LFS/usr/include/gnu/
|
|---|
| 283 | ln -svf ..&lib-m32;/ld-linux.so.2 $LFS/lib/ld-linux.so.2</userinput></screen>
|
|---|
| 284 |
|
|---|
| 285 | <caution>
|
|---|
| 286 | <para>At this point, it is imperative to stop and ensure that the basic
|
|---|
| 287 | functions (compiling and linking) of the new toolchain are working as
|
|---|
| 288 | expected. To perform a sanity check, run the following commands:</para>
|
|---|
| 289 |
|
|---|
| 290 | <screen><userinput>echo 'int main(){}' > dummy.c
|
|---|
| 291 | $LFS_TGT-gcc -m32 dummy.c
|
|---|
| 292 | readelf -l a.out | grep '/ld-linux'</userinput></screen>
|
|---|
| 293 |
|
|---|
| 294 | <para>If everything is working correctly, there should be no errors,
|
|---|
| 295 | and the output of the last command will be of the form:</para>
|
|---|
| 296 |
|
|---|
| 297 | <screen><computeroutput>[Requesting program interpreter: /lib/ld-linux.so.2]</computeroutput></screen>
|
|---|
| 298 |
|
|---|
| 299 | <para>If the output is not shown as above or there was no output at all,
|
|---|
| 300 | then something is wrong. Investigate and retrace the steps to find out
|
|---|
| 301 | where the problem is and correct it. This issue must be resolved before
|
|---|
| 302 | continuing on.</para>
|
|---|
| 303 |
|
|---|
| 304 | <para>Once all is well, clean up the test files:</para>
|
|---|
| 305 |
|
|---|
| 306 | <screen><userinput>rm -v dummy.c a.out</userinput></screen>
|
|---|
| 307 |
|
|---|
| 308 | </caution>
|
|---|
| 309 |
|
|---|
| 310 | </sect2><!-- m32 -->
|
|---|
| 311 |
|
|---|
| 312 | <!-- - - - - - - - - - -->
|
|---|
| 313 | <!-- Multilib - x32bit -->
|
|---|
| 314 | <!-- - - - - - - - - - -->
|
|---|
| 315 |
|
|---|
| 316 | <sect2 arch="ml_x32,ml_all">
|
|---|
| 317 | <title>Building Glibc - x32bit</title>
|
|---|
| 318 |
|
|---|
| 319 | <para>Now recompile for mx32. The extracted source can be
|
|---|
| 320 | reused but needs to cleaned before installing the mx32
|
|---|
| 321 | version of Glibc.</para>
|
|---|
| 322 |
|
|---|
| 323 | <para>Clear the build directory and remove artefacts from
|
|---|
| 324 | previous build:</para>
|
|---|
| 325 |
|
|---|
| 326 | <screen><userinput remap="pre">make clean
|
|---|
| 327 | find .. -name "*.a" -delete</userinput></screen>
|
|---|
| 328 |
|
|---|
| 329 | <para>Configure Glibc for mx32 with the following commands:</para>
|
|---|
| 330 |
|
|---|
| 331 | <screen><userinput remap="configure">CC="$LFS_TGT-gcc -mx32" \
|
|---|
| 332 | CXX="$LFS_TGT-g++ -mx32" \
|
|---|
| 333 | ../configure \
|
|---|
| 334 | --prefix=/usr \
|
|---|
| 335 | --host=$LFS_TGTX32 \
|
|---|
| 336 | --build=$(../scripts/config.guess) \
|
|---|
| 337 | --enable-kernel=&min-kernel; \
|
|---|
| 338 | --with-headers=$LFS/usr/include \
|
|---|
| 339 | --enable-multi-arch \
|
|---|
| 340 | --libdir=&usr-lib-mx32; \
|
|---|
| 341 | --libexecdir=&usr-lib-mx32; \
|
|---|
| 342 | libc_cv_slibdir=&usr-lib-mx32;</userinput></screen>
|
|---|
| 343 |
|
|---|
| 344 | <para>Compile the package:</para>
|
|---|
| 345 |
|
|---|
| 346 | <screen><userinput remap="make">make</userinput></screen>
|
|---|
| 347 |
|
|---|
| 348 | <para>Install the package:</para>
|
|---|
| 349 |
|
|---|
| 350 | <screen><userinput remap="install">make DESTDIR=$PWD/DESTDIR install
|
|---|
| 351 | cp -a DESTDIR&lib-mx32;/* $LFS&lib-mx32;/
|
|---|
| 352 | cp -a DESTDIR&usr-lib-mx32; $LFS/usr/
|
|---|
| 353 | install -vm644 DESTDIR/usr/include/gnu/{lib-names,stubs}-x32.h \
|
|---|
| 354 | $LFS/usr/include/gnu/
|
|---|
| 355 | ln -svf ..&lib-mx32;/ld-linux-x32.so.2 $LFS/lib/ld-linux-x32.so.2</userinput></screen>
|
|---|
| 356 |
|
|---|
| 357 | <caution>
|
|---|
| 358 | <para>At this point, it is imperative to stop and ensure that the basic
|
|---|
| 359 | functions (compiling and linking) of the new toolchain are working as
|
|---|
| 360 | expected. To perform a sanity check, run the following commands:</para>
|
|---|
| 361 |
|
|---|
| 362 | <screen><userinput>echo 'int main(){}' > dummy.c
|
|---|
| 363 | $LFS_TGT-gcc -mx32 dummy.c
|
|---|
| 364 | readelf -l a.out | grep '/ld-linux-x32'</userinput></screen>
|
|---|
| 365 |
|
|---|
| 366 | <para>If everything is working correctly, there should be no errors,
|
|---|
| 367 | and the output of the last command will be of the form:</para>
|
|---|
| 368 |
|
|---|
| 369 | <screen><computeroutput>[Requesting program interpreter: /libx32/ld-linux-x32.so.2]</computeroutput></screen>
|
|---|
| 370 |
|
|---|
| 371 | <para>If the output is not shown as above or there was no output at all,
|
|---|
| 372 | then something is wrong. Investigate and retrace the steps to find out
|
|---|
| 373 | where the problem is and correct it. This issue must be resolved before
|
|---|
| 374 | continuing on.</para>
|
|---|
| 375 |
|
|---|
| 376 | <para>Once all is well, clean up the test files:</para>
|
|---|
| 377 |
|
|---|
| 378 | <screen><userinput>rm -v dummy.c a.out</userinput></screen>
|
|---|
| 379 |
|
|---|
| 380 | </caution>
|
|---|
| 381 |
|
|---|
| 382 | </sect2><!-- mx32 -->
|
|---|
| 383 |
|
|---|
| 384 | <sect2 role="content">
|
|---|
| 385 | <title/>
|
|---|
| 386 |
|
|---|
| 387 | <para>Details on this package are located in
|
|---|
| 388 | <xref linkend="contents-glibc" role="."/></para>
|
|---|
| 389 |
|
|---|
| 390 | </sect2>
|
|---|
| 391 |
|
|---|
| 392 | </sect1>
|
|---|
