https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446
--- Comment #7 from Steve Kargl <sgk at troutmask dot apl.washington.edu> --- On Mon, Jul 09, 2018 at 10:21:20PM +0000, ebotcazou at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446 > > --- Comment #6 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- > > 'gmake -j6 check-fortran' has never died on an error > > like the one I've shown in the 15+ years that I've been > > contributing to GCC. Needing -k now, means someone has > > broken the build infrastructure. > > No, it's just https://gcc.gnu.org/ml/gcc-patches/2018-06/msg01023.html > 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.
