'make -k check' successfully performs lots of tests but always quits when reaching objc. I am using Red Hat Linux 9 on an Athlon XP. === objc Summary === # of expected passes 1153 /home/peter/development/gcc/gcc-3.3-binaries/gcc/xgcc version 3.3 make[2]: Leaving directory `/home/peter/development/gcc/gcc-3.3-binaries/gcc' make[1]: Target `do-check' not remade because of errors. make[1]: Leaving directory `/home/peter/development/gcc/gcc-3.3-binaries' make: *** [check] Error 2
Odd, I can't seem to reproduce your problem on RedHat 8. I thought when one specified -k to make, it didn't give the usual "error 2" etc. You're sure you're using -k, right? What options did you configure gcc with? Thanks, Dara
See Dara's question.
I really use -k and I did not use any configure options.
Very strange. What options did you pass to configure? What versions of make and dejagnu are you using? Thanks, Dara
Subject: Re: make -k check quits when reaching objc > Very strange. What options did you pass to configure? What versions of make and dejagnu are you > using? Thanks, I did not pass any options to configure. make and dejagnu were taken from the RHL 9 CDs. make: 3.79.1-17 dejagnu: 1.4.2-10 Best regards, Peter.
Actually it does not quit on objc but it is annoying to have this behaivor. It still on the mainline (20030724) but a different place: ================== All 1 tests passed ================== make[4]: Leaving directory `/home/gates/pinskia/src/gnu/gcc/src/objdir.linux/i686-pc- linux-gnu/boehm-gc' make[3]: Leaving directory `/home/gates/pinskia/src/gnu/gcc/src/objdir.linux/i686-pc- linux-gnu/boehm-gc' make[2]: Leaving directory `/home/gates/pinskia/src/gnu/gcc/src/objdir.linux/i686-pc- linux-gnu/boehm-gc' make[1]: Target `do-check' not remade because of errors. make[1]: Leaving directory `/home/gates/pinskia/src/gnu/gcc/src/objdir.linux' make: *** [check] Error 2 I thought I saw a dup of this bug somewhere.
I found the bug is caused by libjava's testsuite which is filed under bug 2382 so marking this as a dup of that bug. *** This bug has been marked as a duplicate of 2382 ***