https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446
--- Comment #9 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- > So, instead of using -k to pape over an error in the Makefile, > what is wrong with the lines > > check-DEJAGNU: site.exp > srcdir='$(srcdir)'; export srcdir; \ > EXPECT=$(EXPECT); export EXPECT; \ > runtest=$(RUNTEST); \ > if $(SHELL) -c "$$runtest --version" > /dev/null 2>&1; then \ > exit_status=0; l='$(DEJATOOL)'; for tool in $$l; do \ > if $$runtest $(AM_RUNTESTFLAGS) $(RUNTESTDEFAULTFLAGS) > $(RUNTESTFLAGS); > \ > then :; else exit_status=1; fi; \ > done; \ > else echo "WARNING: could not find \`runtest'" 1>&2; :;\ > fi; \ > exit $$exit_status > > If the commands are command out, there are no errors. So, > what is the above suppose to do other that cause 2 ERRORs > in the build. But we are talking about errors in the testsuite, not in the Makefile! Every testsuite of the GNU toolchain (GCC, GDB, Binutils, etc...) must be run the same way with "make -k check" because, otherwise, the recursive Make processes will stop on errors due the way the various testsuites are invoked.
