Problems with dejagnu and c++ tests...

[Joel Brobecker <brobecker at gnat dot com>]

I was wondering if somebody could help understand a problem that
all of a sudden appeared on me.

I am running the testsuite on Tru64, and I don't have a C++ compiler
on this target (and I never have). Up until recently, the gdb.cp tests
where executed as best as they could. But I tried running it today, and
kaboum:

<<
Running ./gdb.cp/ambiguous.exp ...
ERROR: (DejaGnu) proc "default_target_compile: Can't find g++." does not exist.
The error code is NONE
The info on the error is:
close: invalid spawn id (6)
    while executing
"close -i 6"
    invoked from within
"catch "close -i $spawn_id""
>>

The error, unfortunately, is simply aborting my run, and I don't
understand why.

As best as I can determine, the sequence of calls goes like this:

   gdb_compile
    -> target_compile
      -> default_target_compile

target_compile returns what default_target_compile returned, which
is 

    return "default_target_compile: Can't find $compiler."

And then the postprocessing of the output by gdb_compile looks like:

    set result [target_compile $source $dest $type $options];
    regsub "\[\r\n\]*$" "$result" "" result;
    regsub "^\[\r\n\]*" "$result" "" result;
    if { $result != "" && [lsearch $options quiet] == -1} {
        clone_output "gdb compile failed, $result"
    }
    return $result;

Does anybody have a clue of what's happening?

Thanks,
-- 
Joel