On Sat, Jan 18, 2014 at 12:31 AM, David Kredba <nheghathivhistha@xxxxxxxxx> wrote: > You can use a contrib/test_summary script. Call it from build dir > pointing to a source dir. It formates the results nice way. > As the (B)book suggests you can compare results with gcc-test-results > mailing list. Thanks for pointing it out. > > 2014/1/17 Ian Lance Taylor <iant@xxxxxxxxxx>: >> On Fri, Jan 17, 2014 at 9:33 AM, Prathamesh Kulkarni >> <bilbotheelffriend@xxxxxxxxx> wrote: >>> Hi, after building gcc-4.9.0 with make bootstrap, i ran >>> make -k check and got the following error (make bootstrap, make >>> install work smoothly): >>> >>> make[3]: [check-parallel-gcc] Error 1 (ignored) >>> make[4]: *** [check-DEJAGNU] Error 1 >>> make[3]: *** [check-am] Error 2 >>> make[3]: Target `check' not remade because of errors. >>> make[2]: *** [check-recursive] Error 1 >>> make[2]: Target `check' not remade because of errors. >>> make[1]: *** [check-target-libjava] Error 2 >>> make[4]: *** [check-DEJAGNU] Error 1 >>> make[3]: *** [check-am] Error 2 >>> make[3]: Target `check' not remade because of errors. >>> make[2]: *** [check-recursive] Error 1 >>> make[2]: Target `check' not remade because of errors. >>> make[1]: *** [check-target-libgomp] Error 2 >>> make[1]: Target `check-target' not remade because of errors. >>> make: *** [do-check] Error 2 >>> make: Target `check' not remade because of errors. >> >> All this tells us is that some tests failed. That is fairly normal. >> You will have to actually look at the test failures to see what >> happened. >> >> Ian
