tls tests fail of gcc-4.0.3 and glibc errors in nptl; what to do now?

Ken Moffat ken at linuxfromscratch.org
Sun Jan 7 11:40:50 PST 2007


On Sun, Jan 07, 2007 at 07:31:16PM +0100, lynx.abraxas at freenet.de wrote:
> Hallo!
> 
> 
> I'm  trying  to compile a gcc-4.0.3 to compile glibc-2.3.6 but gcc-4.0.3 tests
> have tls failures, see attachment test_summary01.out.
> 
> I ran into problems while trying to upgrade my glibc from 2.3.3-lfs  to  2.3.6
> (because  of  x264  using  sched_getaffinity()  with 2 parms, glibc not beeing
> executable and now wine segfaulting). There I got errors (see below). Are they
> related  to  the gcc tls failures? What can I do with gcc and glibc? Can these
> problems be related to the kernel 2.6.19.1?
> 
> My system is  an  LFS  5.1.1  with  upgraded  versions  of  gcc  and  binutils
> (binutils-2.15.94.0.2.2   ->  binutils-2.17.50.0.1)  and  not  2.4-kernel  but
> 2.6.19.1. I fear that the default gcc (4.1.1) of my system  had  tls  failures
> too.
> 
> Thanks for any help,
> Lynx
> 
 I'm unclear exactly what you are trying to do, or what toolchains
you have available.  At first, I thought 'LFS 5.1.1' was a typo for
'LFS 6.1.1', but when you mention '2.4-kernel' I'm not so sure.

 I'm not familiar with x264 (nor multiprocessors, nor wine), but if
you are intending to upgrade glibc on a running system, you have a
good chance of breaking things.  If you build from source, you
should expect to build a new system from time to time.

 I can't find sched_affinity in any headers on my current system, so
I guess it is a kernel syscall - in that case, and given that it
apparently doesn't work for you with 2.6.19.1, maybe it's the
include/linux headers which cause the compiler to call it with the
wrong args.  If so, upgrading glibc is unlikely to help, and changing
include/linux under a running system is likely to break things.

 You also say you are "trying to compile a gcc-4.0.3", but then you
appear to already have a version of gcc-4.0.3, which you have use to
build gcc:

> with gcc-4.0.3:
> grep Error glibc-check-log0
> make[2]: [/usr/src/glibc/glibc-build/posix/annexc.out] Error 1 (ignored)
> make[2]: *** [/usr/src/glibc/glibc-build/nptl/tst-cancel17.out] Error 1
> make[2]: *** [/usr/src/glibc/glibc-build/nptl/tst-cancelx4.out] Error 1
> make[2]: *** [/usr/src/glibc/glibc-build/nptl/tst-cancelx5.out] Error 1
> make[2]: *** [/usr/src/glibc/glibc-build/nptl/tst-cancelx16.out] Error 1
> make[2]: *** [/usr/src/glibc/glibc-build/nptl/tst-cancelx17.out] Error 1
> make[2]: *** [/usr/src/glibc/glibc-build/nptl/tst-cancelx20.out] Error 1
> make[2]: *** [/usr/src/glibc/glibc-build/nptl/tst-cancelx21.out] Error 1
> make[2]: *** [/usr/src/glibc/glibc-build/nptl/tst-cleanupx4.out] Error 1
> make[1]: *** [nptl/tests] Error 2
> make: *** [check] Error 2
> 

 as well as a version of gcc-4.1.1:

> with gcc-4.1.1:
> grep Error glibc-check-log0
> make[2]: [/usr/src/glibc/glibc-build/posix/annexc.out] Error 1 (ignored)
> make[2]: *** [/usr/src/glibc/glibc-build/nptl/tst-cancel17.out] Error 1
> make[2]: *** [/usr/src/glibc/glibc-build/nptl/tst-cancelx4.out] Error 1
> make[2]: *** [/usr/src/glibc/glibc-build/nptl/tst-cancelx5.out] Error 1
> make[2]: *** [/usr/src/glibc/glibc-build/nptl/tst-cancelx16.out] Error 1
> make[2]: *** [/usr/src/glibc/glibc-build/nptl/tst-cancelx17.out] Error 1
> make[2]: *** [/usr/src/glibc/glibc-build/nptl/tst-cancelx20.out] Error 1
> make[2]: *** [/usr/src/glibc/glibc-build/nptl/tst-cancelx21.out] Error 1
> make[1]: *** [nptl/tests] Error 2
> make[2]: *** [/usr/src/glibc/glibc-build/resolv/tst-leaks.out] Error 1
> make[1]: *** [resolv/tests] Error 2
> make: *** [check] Error 2
>
[ I've snipped the gcc test results here, because I'm getting
totally confused - you only seem to have a _few_ failures, which
should be no big deal ] 

 The glibc test failures look like the sort of things we all see
from time to time - search the archives and I'm sure you'll see most
of these, although not necessarily so many of them together.

 My best advice to you is to consider if it's time to rebuild your
LFS system completely.  But, I'd better add that glibc-2.5 has some
similar errors in the nptl tests (at least on the combinations of
kernel-binutils-gcc-headers that I've tried so far).

ĸen
-- 
das eine Mal als Tragödie, das andere Mal als Farce



More information about the lfs-support mailing list