I had a bit of time to look at my logs while the initial backup was running, plus a build failure when one of the tests failed unexpectedly, so I've made a note of everything that failed (this is with a patch for automake, so that didn't fail for me.
This was a "by the book" build in as much as I kept /usr/lib/*.a in place until the end of chroot (usually, I rename them all to whatever.hidden when I'm cleaning up at the end of each package). I'd assumed this would solve the failures I see from static tests in ld during the binutils tests, but it didn't. Those are undoubtedly related to something else in my build, but the ld failures don't matter on my real systems and they now go to the bottom of my "ToDo" list in the "cosmetic" area :) What I'm reporting here are the following - 1. bc - 10 failures, all in a similar style the first is Failed: index = 97 val1 = 1338334719204269500461736408706115029076717.4572136445 val2 = 1338334719204269500461736408706115029076717.45721364460012 All the other failures show a shorter value in val1, but the number of digits varies across the tests. Interestingly, the last screen of the check log just shows a lot of lines reporting Total tests: 300, Total failures: 0 among a few other things, so it is easy to overlook these failures (and anyway they almost certainly don't matter). 2. gcc Running /building/gcc-4.8.1/gcc/testsuite/g++.dg/asan/asan.exp ... FAIL: g++.dg/asan/asan_test.C -O2 AddressSanitizer_HugeMallocTest Ident((char*)malloc(size))[-1] = 0 output pattern test, should match is located 1 bytes to the left of 2726297600-byte and Running /building/gcc-4.8.1/libmudflap/testsuite/libmudflap.c++/c++frags.exp ... FAIL: libmudflap.c++/pass41-frag.cxx ( -O) execution test FAIL: libmudflap.c++/pass41-frag.cxx (-O2) execution test FAIL: libmudflap.c++/pass41-frag.cxx (-O3) execution test 3. glibc make[2]: *** [/building/glibc-build/posix/tst-getaddrinfo4.out] Error 1 make[2]: [/building/glibc-build/posix/annexc.out] Error 1 (ignored) make[1]: *** [posix/tests] Error 2 make[2]: *** [/building/glibc-build/rt/tst-cpuclock2.out] Error 1 make[1]: *** [rt/tests] Error 2 make[2]: [/building/glibc-build/conform/run-conformtest.out] Error 1 (ignored) make: *** [check] Error 2 - pretty much as expected, I think 4. inetutils - this was the one that ended with an error status and stopped my build. Worked on x86_64, maybe something in my kernel's config settings. OTOH, 1 packet transmitted and 1 received doesn't sound like a failure to me. localhost: bluesbreaker PASS: localhost PING 127.0.0.1 (127.0.0.1): 56 data bytes 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.051 ms --- 127.0.0.1 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.051/0.051/0.051/0.000 ms Failed at pinging ::1. FAIL: ping-localhost.sh 5. texinfo. FAIL: test_scripts/formatting_unknown_nodes_renamed.sh Not sure if Matt's patch fixes this. ĸen -- das eine Mal als Tragödie, dieses Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
