On Sun, Dec 5, 2010 at 11:28 PM, Eliot Gable <egable+...@gmail.com> wrote: > > Just like mentioned here: > http://comments.gmane.org/gmane.linux.lfs.support/31452 > I seem to be stuck in the same build loop in glibc-2.12.1 in Section 6.9 of > LFS version 6.7. Things I have tried: > rm /etc/localtime > ln -s /usr/share/zoneinfo/GMT /etc/localtime (Note: hardware clock is > storing in GMT) > ntpdate ntp.apple.com > hwclock --systohc > cd <glibc-2.12.1 source dir> > for file in $(find . -print) ; do touch $file ; done > cd <glibc-build dir> > for file in $(find . -print) ; do touch $file ; done > make distclean > Then I tried to configure and make again. No luck. Still gets stuck in the > nptl loop. > > Anyone have any other suggestions I might try to get through this loop? I > have verified the system time is correct in both the system and the hardware > clock. > I am building this under CentOS 5.5 x86_64 on an Intel Core2 Duo. > If you think there is some other piece of information about my system that > might be useful in troubleshooting this, let me know and I'll dig it up.
Found this page today: http://wiki.gnashdev.org/Building_OLPC_Tools It says: "When building GLIBC, you need to remove or rename the $prefix/include directory if you build GLIBC and plan to install it on top of an existing installation. When --prefix is set to a directory with an existing GLIBC installation, the wrong thread headers are picked up, and the nptl add on to GLIBC will get caught in a loop, and try to build forever." Based on that, I modified the glibc configure line to specify '--includedir=' directive and specified a different include directory. Then I tried to build again, and this time it finally made it through the nptl compilation. Doing a 'TIMEOUTFACTOR=16 make -k check' also shows no errors. In all fairness, I'm not explicitly following the LFS build directions. I'm actually working on building a toolchain for building an application I'm writing. So, I am not actually performing the section 6.9 stuff inside the chroot environment. But, for anyone else having this issue, there is something that can cause it other than bad clock settings. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
