LFS 6.2. Ch6.9 Glibc-2.3.6 error during make check (system halted)

Ken Moffat ken at linuxfromscratch.org
Sat Aug 19 04:15:26 PDT 2006


On Fri, Aug 18, 2006 at 11:13:55PM +0200, Danny wrote:
> > Ken
> 
> I'm actually building the system straight from a command line on an 
> 'empty' machine. I fully understand that I'm building on an older 
> machine, but didn't have this problem when building 6.1.1
> 
[grumpy editor mode on] Don't get me started on the variability of
glibc test results!  [/]
> First three errors are the same as with my 6.1.1 build and can be ignored:
> 
> make[2]: *** [/sources/glibc-build/posix/bug-regex24.out] Error 1
> make[2]:          "           "      "  /tst-regex2.out] error 1
> make[2]:          "           "      "  /Error 1 (ignored)
> 
> then it starts with:
> 
> make[2]: *** [/sources/glibc-build/nptl/tst-mutex8.out] Error 1
> ...
> three more pages of errors in this directory nptl and it ends with:
> ...
> make[2]: *** [/sources/glibc-build/nptl/tst-fini1.out] Error 134
 Segfault, I think.
> make[2]: *** [/  "        "         "  /tst-execstack.out] Error 1
> make1]: [nptl/tests] Error 2
> make[2]: *** [/sources/glibc-build/rt/tst-mqueue8.out] Error 1
> make[2]: *** [/sources/glibc-build/rt/tst-mqueue8x.out] Error 127
 Possibly, missing a program or a symlink.
> make[1]: [rt/tests] error 2
> make: *** [check] Error 2
> 
> So now I know I am looking for something wrong with nptl, which is??? 
> (something tells me it's perl, came by that phrase some time ago in the 
> archives, I believe)
 No, I believe the name is new posix threading library - the
replacement for linux-threads.  I imagine the mutex tests could be
down to the old processor.

> I'll go and check but any hints are welcome ;-)
> 
 As Dan Nicholson told me the other day on clfs-dev, stdout from the
tests is in the '.out' files.  That won't help with Error 134 and
Error 127, for those you need to look at the full log (e.g.
'/Error\ 134' in 'view') to see what other messages are associated
with  the 'Error' text.  If one of the problems is a segfault, I've
no idea how to track it down (got one of my own on clfs ppc64).

Ken
-- 
das eine Mal als Tragödie, das andere Mal als Farce



More information about the lfs-support mailing list