Here are details extracted from "*glibc-check-log*":
Majority of testcase failures showed up with *Error 1 *and for explanation* *Didn't expect signal from child: got 'Aborted' /mnt/lfs/sources/glibc-build/ ... --------- additional error info... dlfcn/bug-atexit3 --------------- unistd.h conflict: /inlude OR /posix ?
... posix/annexc --------------------------- (ignored)
... nptl/tst-mutex8 -mutexpi8 -cond7 -cond8 -cond22
-robust{1,2,3,4,5,6,7} -robustpi{1,2,3,4,5,6,7}
-once{3,4} -key3 -basic{3,4} -join{1,5,6} -tsd5
-cancel{1-18,20-23,25} -cleanup{0,1,3,4}
-exit2 -exit3 ----------------- got 'Aborted', need 'Alarm
clock'
-cancelx{2,3,6,7}
... rt/tst-mqueue8 -cpuclock2
So, to me, this looks like all these failures are due to timeout (? "Sun
VirtualBox" does not have exclusive control of my PC hardware).
Other error codes happened with the following test cases:
/mnt/lfs/sources/glibc-build/
... nptl/tst-sem{11,12} -fini1 Error 134 --- /bin/sh line 1: xxxxx Aborted
-cancel24 Error 127 --- cannot open shared object
file
-cancelx{4,5,8} " " 'libgcc_s.so.1'
-cancelx{9-18,20,21} " " "
-cleanupx{0-4} " " "
-oncex{3,4} " " "
... rt/tst-mqueue8x " " "
.. debug/tst-chk{4,5,6} " " --- (posix/unistd.h problem)
/tst-lfschk{4,5,6} " " "
As far as I can see, no links/symlinks are missing, and yes, I have gone
strictly by the (LFS 6.6) Book, and no, no customization.
Greetings Franz L. Kuhlmann
<<attachment: f_kuhlmann.vcf>>
-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
