%general-entities; %patches-entities; ]> Glibc Now we make sure the Glibc goes into /lib32: echo "slibdir=/lib32" >> configparms CC="gcc ${BUILDN32}" CXX="g++ ${BUILDN32}" \ ../glibc-&glibc-version;/configure --prefix=/usr \ --disable-profile --enable-add-ons --enable-kernel=2.6.0 \ --libexecdir=/usr/lib32/glibc --libdir=/usr/lib32 --libexecdir=/usr/lib32/glibc This changes the location of the pt_chown program from its default of /usr/libexec to /usr/lib32/glibc. make check 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 LFS partition with the noatime option, the atime test will fail. As mentioned in , do not use the noatime option while building LFS. When running on older and slower hardware, some tests can fail because of test timeouts being exceeded.