On 4/13/07, prdcomp <[EMAIL PROTECTED]> wrote: > > Regarding the timing out, I've got one of the log files opened in front of me > now. Will reproduce part of it - it indeed mentions "program timed out", but > don't know what caused it, its relation with the failures etc: > > === libmudflap Summary === > > # of expected passes 974 > # of unexpected failures 314 > make[4]: *** [check-DEJAGNU] Error 1 > make[4]: Leaving directory > `/sources/gcc-build/i686-pc-linux-gnu/libmudflap/testsuite` > make[3]: *** [check-am] Error 2 > make[3]: Target 'check' not remade because of errors. > WARNING: program timed out. > FAIL: libmudflap.cth/pass39-frag.c (-O2) execution test > FAIL: libmudflap.cth/pass39-frag.c (-O2) output pattern test > WARNING: program timed out.
Yep, they're timing out. Wow, that's a spectacular amount of failing. Do this sed before you start the build to give the test programs some more time before they quit. sed -i.bak '/dg-timeout/s/3\|10/20/' libmudflap/testsuite/libmudflap.cth/*.c That's from DIY Linux. We should probably do the same here. That should help get the number of failures down. And yes, 6 is the normal number of failures. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
