This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: Run V3 tests on installed compiler
On Mar 23, 2005, at 10:36 AM, Mark Mitchell wrote:
Gabriel Dos Reis wrote:
Mark Mitchell <mark@codesourcery.com> writes:
[...]
| Your plan would work too, but rather than having DejaGNU look
for the
| file, I think it would be technically better to have the user
use the
| normal DejaGNU mechanisms for selecting which tests to run.
Perhaps,
| we could put the logic you're looking for into the Makefile, so
that
| "make check-maintainer" automatically passed in testsuite_files, if
| typing the runtest command manually is noxious. I don't feel very
| strongly about this; if you think its vital that DejaGNU look
for the
| file, I'll make that change ASAP.
That would be an improvement.
What, in particular, would be an improvement? Adding "check-
maintainer" (or "maintainer-check"?)? Or, changing normal.exp to
read testsuite_files if it exists? What is it you would like me to
do?
I have a preference for reading testsuite_files, if it exists. Also,
I don't think it is unreasonable for the testsuite to build by
default the objects it needs during the build, and then just using
them if they like that workflow. The difference can be put into the
site.exp file, such as:
set TESTING_IN_BUILD_TREE 1
and then that can be checked; simple, quick, efficient, clear.