On Mon, Nov 17, 2014 at 5:29 AM, William Harrington <[email protected]> wrote:
> Hello Brent, > > This could be an issue with QEMU and the running kernel or some of the > kernel filesystems are not mounted or some utils required the test suite > were missed in ch5, such as diffutils (in that case there would most likely > be more test failures than above). > > You may wish to view the test .out files for each test that failed and see > what messages you can find or go through the build log and perhaps find > some more output as to why each test failed. > > Sincerely, > > William Harrington > > -- > http://lists.linuxfromscratch.org/listinfo/lfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page > > Do not top post on this list. > > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > > http://en.wikipedia.org/wiki/Posting_style > Thanks for the suggestions. I hoped that maybe QEMU was the issue. I mounted the lfs partitions into the host system and chrooted from the host and retried the build. I am getting the same exact errors so QEMU is not the problem. Here is a sampling of some of the errors: == debug/tst-backtrace3 ========================== root:/src/wrk/glibc-build/debug# cat tst-backtrace3.test-result FAIL: debug/tst-backtrace3 original exit status 1 root:/src/wrk/glibc-build/debug# cat tst-backtrace3.out Obtained backtrace with 0 functions Failure on line 53 root:/src/wrk/glibc-build/debug# head -n 55 ../../glibc-2.20/debug/tst-backtrace3.c | tail -n 5 if (n < NUM_FUNCTIONS) { FAIL (); return 1; } == debug/tst-backtrace3 ========================== == rt/tst-cpuclock2 =========================== root:/src/wrk/glibc-build/rt# cat tst-cpuclock2.test-result FAIL: rt/tst-cpuclock2 original exit status 1 root:/src/wrk/glibc-build/rt# cat tst-cpuclock2.out live thread clock fffffffffffdacb6 resolution 0.000000001 live thread before sleep => 0.000177006 self thread before sleep => 0.000280874 live thread after sleep => 0.500717116 self thread after sleep => 0.000324275 == rt/tst-cpuclock2 =========================== == rt/tst-mqueue8 =============================== root:/src/wrk/glibc-build/rt# cat tst-mqueue8.test-result FAIL: rt/tst-mqueue8 original exit status 1 root:/src/wrk/glibc-build/rt# cat tst-mqueue8.out going to cancel mq_receive in-time Didn't expect signal from child: got `Aborted' == rt/tst-mqueue8 =============================== == nptl/tst-join1 ========================== root:/src/wrk/glibc-build/nptl# cat tst-join1.test-result FAIL: nptl/tst-join1 original exit status 1 root:/src/wrk/glibc-build/nptl# cat tst-join1.out Didn't expect signal from child: got `Aborted' == nptl/tst-join1 ========================== Any suggestions?
-- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
