----Original Message----
>From: James E Wilson
>Sent: 13 April 2005 20:29
> Dave Korn wrote:
>> [EMAIL PROTECTED] /gnu/testing/obj-HEAD> make check 2>&1 | tee check.log
>
> Always use "make -k check". Some testsuites exit with an error if one
> or more tests failed, and because this is the normal situation for
> almost all testsuites, this means the only way to get meaningful results
> is to use -k.
>
> You will still get a failure for the fixincludes testsuite, but it will
> be ignored, and the other testsuites will work.
>
> Or alternatively, run the ones you care about individually, e.g. "make
> check-target-libstdc++-v3" which will run only the libstdc++-v3
> testsuite. Or alternatively, you can cd into the directories you care
> about, e.g. "cd gcc; make check-g++" which will run just the gcc C++
> testsuite. Etc.
Thanks James, I did of course forget about "make -k", but I do know about
make in subdirs and about the different targets. I just did a "egrep
'^check-.*:'" on the top level makefile and ran the c, c++ and libstdc
tests; the test_summary will be forthcoming shortly.
cheers,
DaveK
--
Can't think of a witty .sigline today....
