This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Problems with "make check"
- From: Zack Weinberg <zack at codesourcery dot com>
- To: Andreas Jaeger <aj at suse dot de>
- Cc: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner), gcc at gcc dot gnu dot org
- Date: Wed, 02 Apr 2003 22:04:55 -0800
- Subject: Re: Problems with "make check"
- References: <10303280216.AA26907@vlsi1.ultra.nyu.edu><87he9gfx0q.fsf@egil.codesourcery.com> <u8istw88pf.fsf@gromit.moeb>
Andreas Jaeger <aj at suse dot de> writes:
> Zack Weinberg <zack at codesourcery dot com> writes:
>
>> kenner at vlsi1 dot ultra dot nyu dot 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