RFC: run tests on installed compiler

[Mark Mitchell]

Benjamin Kosnik wrote:
>>I would prefer that testsuite_file not be used, but I will defer to your 
>>instructions.  Right now, I'm interpreting what you've said as an 
>>opinion, not a firm direction to change the way it works.  If you want 
>>me to change it, please tell me do that explicitly.
> 
> 
> Please change it.

Here is a patch to restore the previous behavior.  Tested on 
x86_64-unknown-linux-gnu by running with a testsuite_files containing 
only a few files, and by running without testsuite_files and observing 
that the whole testsuite ran.  OK to apply?  If so, I think I am 
(perhaps temporarily) off the hook for updating the docs, as the old 
instructions re. testsuite_files still work.

As a compromise, I would like to remove the automatic generation of 
testsuite_files by default in the Makefile.  In other words, remove 
"testsuite_files" from "all-local" in testsuite/Makefile.am.  That will 
cause the testsuite to use the non-testsuite_files codepath for "casual" 
  users; when V3 maintainers want to test particular tests, they can 
still create testsuite_files (by "make testsuite_files", or by listing 
the tests they want).  Would that be acceptable?

Also, I would still appreciate it if you have a chance to investigate 
any of the other ideas I proposed for debugging the original problem. 
The `cat testsuite_files` solution should work; it's the usual DejaGNU 
way, and it works for all the other testsuites.  It would be nice to 
understand what's going wrong for you, as it would eliminate this 
difference from the other testsuites.

-- 
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: v3.patch
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20050324/30aacda7/attachment.ksh>