This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Problems with "make check"
Phil Edwards <phil at jaj dot com> writes:
|> On Thu, Apr 03, 2003 at 08:10:59AM +0200, Andreas Jaeger wrote:
|> > On Wed, Apr 02, 2003 at 10:04:55PM -0800, Zack Weinberg wrote:
|> > > Andreas Jaeger <aj at suse dot de> writes:
|> > > > 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.
|> >
|> > Yes, it would be. The problem that I see is that libstdc++-v3 uses
|> > automake to generate the calls for runtest. I do not know how to
|> > teach automake to ignore the error (otherwise I would have send a patch
|> > already ;-).
|>
|> You're not the first. :-) It would require a one-line change to automake's
|> $share/am/dejagnu.am, and I'm not sure what else.
But then, what's so bad about make -k check?
Andreas.
--
Andreas Schwab, SuSE Labs, schwab at suse dot de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."