Re: Problems with dejagnu and c++ tests...

[mec dot gnu at mindspring dot com (Michael Elizabeth Chastain)]

drow> I think assuming we can compile and run is fine.  Output is an
drow> absolutely no-show, however.  Take a look at how many of our supported
drow> targets don't have any kind of remote file I/O capability - gdbserver,
drow> for one.

Argh.  Okay.  Although I'm not talking about file I/O, I'm talking
about write to stdout.  There are 58 *.[Cc] files with printf already.

With the pre-process strategy, I think I have to hit this code:

  # Source the output.
  foreach cppline ...
  {
    next if $cppline =~ m/^#/;
    next if $cppline =~ m/^\s*$/;
    eval { $cppline };
  }

(Oops, I wrote that in Perl!)

These need some more checks before eval'ing cppline.  The only lines I want
to eval are 'set' commands; anything else can be treated as a compiler
diagnostic.  Forward it with 'verbose -log' and set the compiler
variables to an "unknown" state.  That would fix Joel's case.

Michael C