Re: [lfs-support] LFS 7.1 - 6.17. GCC-4.6.2
En 08/05/2012 19:34:13, Eleanore Boyd cara...@cox.net escribió: Another hint: If you trust yourself and/or your copy+paste skills, you can save time by skipping all of the testing in the book. However, if you want to know absolutely that it won't break on you, don't skip them. Then again, I just make a huge command that untars the package, goes into the new directory, does what the book says to do, then exits the directory and proceeds to delete it. Said huge command usually doesn't go on if I do carry out the testing yet I know it's good. Don't be crazy like me and make a huge command out of entire sections of the book. It can go wrong very easily. Elly I will keep it in mind. Best Regards, Lázaro -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] LFS 7.1 - 6.17. GCC-4.6.2
Hello, The GCC compilation process finished fine, but I get the next errors in the testing phase and then the test is stopped. === libgomp Summary === [...] make[2]: Target `check-target' not remade because of errors. make[2]: Leaving directory `/sources/gcc-build' make[1]: *** [do-check] Error 2 make[1]: Target `check' not remade because of errors I checked the log in http://www.linuxfromscratch.org/lfs/build-logs/7.1/core2duo/test-logs/080-gcc and this occur and the test continue without problems. Is there some reason of why did not continue the test? What do you recommend me at this point? Should I compile again or test the suite again? Thanks! Lázaro -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFS 7.1 - 6.17. GCC-4.6.2
Lázaro Morales wrote: Hello, The GCC compilation process finished fine, but I get the next errors in the testing phase and then the test is stopped. === libgomp Summary === [...] make[2]: Target `check-target' not remade because of errors. make[2]: Leaving directory `/sources/gcc-build' make[1]: *** [do-check] Error 2 make[1]: Target `check' not remade because of errors It's always been that way. I suppose it's because of the unexpected failures in libmudflap. gcc-4.7.0 has improved a lot in the area of unit testing. I checked the log in http://www.linuxfromscratch.org/lfs/build-logs/7.1/core2duo/test-logs/080-gcc and this occur and the test continue without problems. Is there some reason of why did not continue the test? What do you recommend me at this point? Should I compile again or test the suite again? No. You are OK. If you had hundreds of errors, then that would be a problem, but notice that the book points out libmudflap as a common problem. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFS 7.1 - 6.17. GCC-4.6.2
En 08/05/2012 12:29:41, Bruce Dubbs bruce.du...@gmail.com escribió: No. You are OK. If you had hundreds of errors, then that would be a problem, but notice that the book points out libmudflap as a common problem. Thanks Bruce! I will continue then. Best Regards, Lázaro -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] LFS 7.1 - 6.17. GCC-4.6.2
On 5/8/2012 11:41 AM, Lázaro Morales wrote: En 08/05/2012 12:29:41, Bruce Dubbsbruce.du...@gmail.com escribió: No. You are OK. If you had hundreds of errors, then that would be a problem, but notice that the book points out libmudflap as a common problem. Thanks Bruce! I will continue then. Best Regards, Lázaro Another hint: If you trust yourself and/or your copy+paste skills, you can save time by skipping all of the testing in the book. However, if you want to know absolutely that it won't break on you, don't skip them. Then again, I just make a huge command that untars the package, goes into the new directory, does what the book says to do, then exits the directory and proceeds to delete it. Said huge command usually doesn't go on if I do carry out the testing yet I know it's good. Don't be crazy like me and make a huge command out of entire sections of the book. It can go wrong very easily. Elly -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
