[Bug testsuite/86446] 'gmake check-fortran' broken in libgomp

2018-07-10 Thread ebotcazou at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446 --- Comment #9 from Eric Botcazou --- > 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 EXPEC

[Bug testsuite/86446] 'gmake check-fortran' broken in libgomp

2018-07-09 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446 --- Comment #8 from Dominique d'Humieres --- > > The correct invocation of a GCC testsuite is "make -k check-blah", otherwise > > the recursive Make processes will stop on errors. > > > > Since when? I've been doing 'gmake check-fortran' and >

[Bug testsuite/86446] 'gmake check-fortran' broken in libgomp

2018-07-09 Thread sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446 --- Comment #7 from Steve Kargl --- On Mon, Jul 09, 2018 at 10:21:20PM +, ebotcazou at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446 > > --- Comment #6 from Eric Botcazou --- > > 'gmake -j6 check-fortran' has n

[Bug testsuite/86446] 'gmake check-fortran' broken in libgomp

2018-07-09 Thread ebotcazou at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446 --- Comment #6 from Eric Botcazou --- > '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. N

[Bug testsuite/86446] 'gmake check-fortran' broken in libgomp

2018-07-09 Thread sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446 --- Comment #5 from Steve Kargl --- On Mon, Jul 09, 2018 at 10:05:23PM +, ebotcazou at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446 > > --- Comment #4 from Eric Botcazou --- > > Since when? > > The dawn of ti

[Bug testsuite/86446] 'gmake check-fortran' broken in libgomp

2018-07-09 Thread ebotcazou at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446 --- Comment #4 from Eric Botcazou --- > Since when? The dawn of time, see https://gcc.gnu.org/contribute.html#testing

[Bug testsuite/86446] 'gmake check-fortran' broken in libgomp

2018-07-09 Thread sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446 --- Comment #3 from Steve Kargl --- On Mon, Jul 09, 2018 at 07:33:48PM +, sgk at troutmask dot apl.washington.edu wrote: > > gmake[4]: *** [Makefile:306: check-DEJAGNU] Error 1 > gmake[4]: Leaving directory > '/safe/sgk/gcc/obj/x86_64-unknow

[Bug testsuite/86446] 'gmake check-fortran' broken in libgomp

2018-07-09 Thread sgk at troutmask dot apl.washington.edu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446 --- Comment #2 from Steve Kargl --- On Mon, Jul 09, 2018 at 07:20:02PM +, ebotcazou at gcc dot gnu.org wrote: > > The correct invocation of a GCC testsuite is "make -k check-blah", otherwise > the recursive Make processes will stop on errors

[Bug testsuite/86446] 'gmake check-fortran' broken in libgomp

2018-07-09 Thread ebotcazou at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86446 Eric Botcazou changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|