Problems with "make check"
Zack Weinberg
zack@codesourcery.com
Thu Apr 3 06:24:00 GMT 2003
Andreas Jaeger <aj@suse.de> writes:
> Zack Weinberg <zack@codesourcery.com> writes:
>
>> kenner@vlsi1.ultra.nyu.edu (Richard Kenner) writes:
>>
>>> What is causing this?
>>>
>>> === libstdc++-v3 Summary ===
>>>
>>> # of expected passes 1255
>>> # of unexpected failures 76
>>> # of expected failures 2
>>> make[4]: *** [check-DEJAGNU] Error 1
>>
>> dejagnu exits unsuccessfully if there are unexpected failures. Use
>> make -k check.
>
> But libstdc++-v3 is the only directory where then make fails. If you
> run the other testsuites, the error is always ignored and libstdc++-v3
> forces you to use make -k check.
Ah, yes, I see that gcc/Makefile.in for instance uses -$(RUNTEST) so
errors will be ignored. It would probably be good to make this
consistent.
zw
More information about the Gcc
mailing list