I've completed the installations up to chapter 6.8. When I install glibc according to the instructions in chapter 6.9, I encounter errors in "make -k check". Similar errors have been reported several times by other people (e.g. in http://www.linuxfromscratch.org/pipermail/lfs-support/2007-August/033507.html), but none of the solutions works for my case.
The compilation of glibc produces no error, but only that "make -k check" gives a few dozens of error, all related to the "missing" libgcc_s.so and pthread. As I examine the screen capture, I find that the error : > libgcc_s.so.1 must be installed for pthread_cancel to work > Didn't expect signal from child: got `Aborted' > make[2]: *** [/lfsb/glibc-build/nptl/tst-mutex8.out] Error 1 is caused by the command : > GCONV_PATH=/lfsb/glibc-build/iconvdata LC_ALL=C \ > /lfsb/glibc-build/elf/ld-linux.so.2 --library-path \ > > /lfsb/glibc-build:/lfsb/glibc-build/math:/lfsb/glibc-build/elf:/lfsb/glibc-build/dlfcn:/lfsb/glibc-build/nss:/lfsb/glibc-build/nis:/lfsb/glibc-build/rt:/lfsb/glibc-build/resolv:/lfsb/glibc-build/crypt:/lfsb/glibc-build/nptl > \ > /lfsb/glibc-build/nptl/tst-mutex8 > /lfsb/glibc-build/nptl/tst-mutex8.out I deleted the files "/lfsb/glibc-build/nptl/lfsb-mutex8*" and re-run the command in "/lfsb/glibc-2.5.1/nptl/" with "/tools/lib" appended to the "--library-path" chain, and it works! By tracing the invocations, I find that the command is contained in "glibc-build/testrun.sh", which is generated by "glibc-2.5.1/Makefile" during "make", and the "--library-path" chain is a part of the variable "$(run-program-prefix)". This variable is defined in "glibc-2.5.1/Makeconfig" as the complicated "$(rpath-link)$(patsubst %,:%,$(sysdep-library-path))", and I can't follow beyond this point. I starting everything afresh. After unpacking the glibc source and making all the modifications described in chapter 6.9, I also modify "glibc-2.5.1/Makeconfig", re-defining "$(run-program-prefix)" as "$(rpath-link)$(patsubst %,:%,$(sysdep-library-path)):/tools/lib". Then I follow the usual procedure of "configure", "make", and "make -k check". All three steps are completed without an error! Although this approach works practically, I still feel uncomfortable about this trick. I'd like to ask if this reflects that my "chroot" environment is not sane ? if so, then what'd gone wrong ? _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
