On Thu, Sep 22, 2016 at 7:18 AM, Michele Bucca <michele.bu...@gmail.com> wrote:
> I've just finished to build binutils and I've run the tests, this was the > result > > === ld Summary === > > # of expected passes 1447 > # of expected failures 4 > # of untested testcases 1 > # of unsupported tests 12 > > /sources/binutils-2.27/build/ld/ld-new 2.27 > make[5]: Leaving directory '/sources/binutils-2.27/build/ld' > make[4]: Leaving directory '/sources/binutils-2.27/build/ld' > make[3]: Leaving directory '/sources/binutils-2.27/build/ld' > make[2]: Leaving directory '/sources/binutils-2.27/build/ld' > make[2]: Entering directory '/sources/binutils-2.27/build/libiberty' > make[3]: Entering directory '/sources/binutils-2.27/build/ > libiberty/testsuite' > gcc -DHAVE_CONFIG_H -g -O2 -I.. > -I../../../libiberty/testsuite/../../include -o test-demangle \ > ../../../libiberty/testsuite/test-demangle.c ../libiberty.a > ./test-demangle < ../../../libiberty/testsuite/demangle-expected > ./test-demangle: 912 tests, 0 failures > ./test-demangle < ../../../libiberty/testsuite/d-demangle-expected > ./test-demangle: 269 tests, 0 failures > gcc -DHAVE_CONFIG_H -g -O2 -I.. > -I../../../libiberty/testsuite/../../include -DHAVE_CONFIG_H -I.. -o > test-pexecute \ > ../../../libiberty/testsuite/test-pexecute.c ../libiberty.a > ./test-pexecute > gcc -DHAVE_CONFIG_H -g -O2 -I.. > -I../../../libiberty/testsuite/../../include -DHAVE_CONFIG_H -I.. -o > test-expandargv \ > ../../../libiberty/testsuite/test-expandargv.c ../libiberty.a > ./test-expandargv > PASS: test-expandargv-0. > PASS: test-expandargv-1. > PASS: test-expandargv-2. > PASS: test-expandargv-3. > PASS: test-expandargv-4. > PASS: test-expandargv-5. > PASS: test-expandargv-6. > gcc -DHAVE_CONFIG_H -g -O2 -I.. > -I../../../libiberty/testsuite/../../include -DHAVE_CONFIG_H -I.. -o > test-strtol \ > ../../../libiberty/testsuite/test-strtol.c ../libiberty.a > ./test-strtol > PASS: test-strtol-0. > PASS: test-strtol-1. > PASS: test-strtol-2. > PASS: test-strtol-3. > PASS: test-strtol-4. > PASS: test-strtol-5. > PASS: test-strtol-6. > PASS: test-strtol-7. > PASS: test-strtol-8. > PASS: test-strtol-9. > PASS: test-strtol-10. > PASS: test-strtol-11. > PASS: test-strtol-12. > PASS: test-strtol-13. > PASS: test-strtol-14. > PASS: test-strtol-15. > PASS: test-strtol-16. > PASS: test-strtol-17. > PASS: test-strtol-18. > PASS: test-strtol-19. > PASS: test-strtol-20. > PASS: test-strtol-21. > PASS: test-strtol-22. > PASS: test-strtol-23. > make[3]: Leaving directory '/sources/binutils-2.27/build/ > libiberty/testsuite' > make[2]: Leaving directory '/sources/binutils-2.27/build/libiberty' > make[1]: Nothing to be done for 'check-target'. > make[1]: Leaving directory '/sources/binutils-2.27/build' > > > is it good? > > P.S Sorry if I'm sendind a lot of these e-mails that may sound of no > point, this is my first build...the second actually..during my first I > stopped in the middle of the process of creating the toolchain. It > just took too long (about 8 hours for toolchain's GCC). > -- > > Hello! Yes, it's good. Those test results are completely normal, and you should be fine to proceed. In terms of the time it took to build LFS that you mentioned above, I've been there. First system for me was a P4 @ 1.3GHz around LFS 7.3 - toolchain-gcc-pass1 took around 9 hours to compile. Second system was even worse - took me a month to do LFS on that one (P3 @ 800MHz around LFS 7.6).
-- 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
