10.8. Glibc-2.19 N32

10.8.1. Installation of Glibc

At the end of the installation, the build system will run a sanity test to make sure everything installed properly. This script performs its tests by attempting to compile test programs against certain libraries. However it does not specify the path to ld.so, and our toolchain is still configured to use the one in /tools. The following set of commands will force the script to use the complete path of the new ld.so that was just installed:

LINKER=$(readelf -l /tools/bin/bash | sed -n 's@.*interpret.*/tools\(.*\)]$@\1@p')
sed -i "s|libs -o|libs -L/usr/lib32 -Wl,-dynamic-linker=${LINKER} -o|" \
  scripts/test-installation.pl
unset LINKER

The Glibc build system is self-contained and will install perfectly, even though the compiler specs file and linker are still pointing at /tools. The specs and linker cannot be adjusted before the Glibc install because the Glibc Autoconf tests would give false results and defeat the goal of achieving a clean build.

Apply the following sed so the tzselect script works properly:

sed -i 's/\\$$(pwd)/`pwd`/' timezone/Makefile

The Glibc documentation recommends building Glibc outside of the source directory in a dedicated build directory:

mkdir -v ../glibc-build
cd ../glibc-build

Tell Glibc to install its 32-bit libraries into /lib32:

echo "slibdir=/lib32" >> configparms

Prepare Glibc for compilation:

CC="gcc ${BUILDN32}" CXX="g++ ${BUILDN32}" \
    ../glibc-2.19/configure --prefix=/usr \
    --disable-profile --enable-kernel=2.6.32 \
    --libexecdir=/usr/lib32/glibc --libdir=/usr/lib32 \
    --enable-obsolete-rpc

Compile the package:

make

Use the following commands to run the test suite and output any test failures:

make -k check 2>&1 | tee glibc-check-log; grep Error glibc-check-log

The Glibc test suite is highly dependent on certain functions of the host system, in particular the kernel. The posix/annexc and conform/run-conformtest tests normally fail and you should see Error 1 (ignored) in the output. Apart from this, the Glibc test suite is always expected to pass. However, in certain circumstances, some failures are unavoidable. If a test fails because of a missing program (or missing symbolic link), or a segfault, you will see an error code greater than 127 and the details will be in the log. More commonly, tests will fail with Error 2 - for these, the contents of the corresponding .out file, e.g. posix/annexc.out may be informative. Here is a list of the most common issues:

Install the package, and remove unneeded files from /usr/include/rpcsvc:

make install &&
rm -v /usr/include/rpcsvc/*.x