Ken Moffat wrote:

On Fri, 9 Sep 2005, Keith wrote:

Gotten pretty far with my first LFS build and just hit my first snag. I'm at the point in Chapter 6 of the stable build where I'm getting glibc-2.3.4 set up. During the make check, I'm getting this error back on the shell screen:
libgcc_s.so.1 must be installed for pthread_cancel to work


Please re-read section 6.6, Creating Essential Symlinks, and make the link(s) you missed 8-)

Because 'make check' will not remake whatever it has already run, you really want to delete the glibc-build directory, and for good measure the glibc-2.3.4 directory, re-extract, apply the patch, make a fresh glibc, then run the tests from the beginning.

I don't recognize the second error you've got, but I'm sure that the missing libgcc_s symlink(s) are enough to break most of these tests.


I'm using Suse 9.3 with kernel 2.6.1.4-21.9-default. Intel Celeron D 2.8Ghz processor. I brought this up in the IRC channel and was told there may be something funky in the latest Suse kernel patch that may be causing this. If that's the case, is there anything I can do? The book says it's important for this test to pass without deviating from the pre-mentioned errors too much. Is it safe to keep building?


You really can't test nptl without the libgcc_s symlinks. I'm fairly hopeful that a clean build of glibc, with reguired patch, will then give good results. Certainly, if your results are significantly different, it won't be a good idea to continue.

Ken

Typos will be the death of me. I'd had errors yesterday with getting the glibc configure to work and found the same problem someone else had in the mailing list with mistyping the perl5 directory name. Sure enough, I did the same.

I missed the "1" in the brackets for the libgcc symlink. I had "libgcc_s.so." :/

Thanks very much for the quick response! I recompiled from scratch and re-ran the make check with 0 errors! :)

Keith
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to