Re: [DejaGnu] dumb user question

[Joel Sherrill]

Rob Savoye wrote:
> 
> On Wed, Jul 25, 2001 at 05:08:00PM -0500, Joel Sherrill wrote:
> 
> > I am sure this should be a FAQ but can't find the answer. :(
> 
>   What FAQ ? :-)
> 
> > I want to compile all tests in a DejaGNU based testsuite
> > without actually running them.  This is for basic checkout
> > of gcc for cross targets where there is no simulator.
> 
>   Unfortunately, you can't really do this in an east way. You can
> just specify the tests you want to run on the command line, (leaving
> out gcc.execute, etc...). For GCC, this would be a cool feature, but
> support would have to be added to the GCC testuite itself, not DejaGnu.
> All they'd have to do is set a "don't execute" variable that specifies
> not to run any tests that have to be executed.

Maybe I am being dense here but I see "compile, link, and don't  
run" as more generally than just for gcc.  In testing anything
cross, I have always wanted to make sure the tools could
compile and link the entire test suite before messing with
the embedded target.  I was thinking of some general support
inside DejaGNU where an option avoided the run part.  If it
did not link, it fails.  I am not sure exactly what to report
if it links.  It could be an expect pass or fail so automatically
saying pass or fail is deceptive.  I suppose a "linked not run"
would be the most accurate.  Something a bit more than skipped.
For sure not linking would be an unexpected failure.

I have done a similar thing in the past with at least the Ada
Compiler Validation test suite (ACVC not ACATS).  There is no
point in trying to run hours and hours of tests if you can't
even link them all.

>         - rob -

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
address@hidden                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985