%general-entities; ]> Glibc CC="gcc ${BUILD64}" CXX="g++ ${BUILD64}" \ ../glibc-&glibc-version;/configure --prefix=/usr \ --disable-profile --enable-add-ons --enable-kernel=2.6.0 \ --libexecdir=/usr/lib64/glibc --libdir=/usr/lib64 --libexecdir=/usr/lib64/glibc This changes the location of the pt_chown program from its default of /usr/libexec to /usr/lib64/glibc. The Glibc test suite is highly dependent on certain functions of the host system, in particular the kernel. In general, the Glibc test suite is always expected to pass. However, in certain circumstances, some failures are unavoidable. This is a list of the most common issues: The math tests sometimes fail. Certain optimization settings are known to be a factor here. The gettext test sometimes fails due to host system issues. The exact reasons are not yet clear. If you have mounted the CLFS partition with the noatime option, the atime test will fail. As mentioned in , do not use the noatime option while building CLFS. When running on older and slower hardware, some tests can fail because of test timeouts being exceeded. /etc/ld.so.conf By default, the dynamic loader (/lib/ld-linux.so.2) searches through /lib, /lib64, /usr/lib, and /usr/lib64 for dynamic libraries that are needed by programs as they are run. However, if there are libraries in directories other than these, they need to be added to the /etc/ld.so.conf file in order for the dynamic loader to find them. Some directories that are commonly known to contain additional libraries are /usr/local/lib, /usr/local/lib64, /opt/lib, and /opt/lib64, so add those directories to the dynamic loader's search path. Create a new file /etc/ld.so.conf by running the following: cat > /etc/ld.so.conf << "EOF" # Begin /etc/ld.so.conf /usr/local/lib /usr/local/lib64 /opt/lib /opt/lib64 # End /etc/ld.so.conf EOF