2010/4/21 Franz L. Kuhlmann <[email protected]>:
> 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'
>
>
> So, to me, this looks like all these failures are due to timeout (? "Sun
> VirtualBox" does not have exclusive control of my PC hardware).
>
I suspect that isn't a very common platform on which to build LFS.
> 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'
> 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.
I think you should take another look at the libgcc_s symlinks (in the
first part of section 6.6). Both the symlinks from /usr/lib need to
point to the corresponding files in /tools. Please run 'file' on them
from the host system to confirm they don't show up as *broken*
symbolic link.
ĸen
--
After tragedy, and farce, "OMG poneys!"
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
