[testsuite] check for languages consistently

Nathan Sidwell nathan@codesourcery.com
Tue Nov 3 16:22:00 GMT 2009


I've dusted off this patch from some time ago, it makes the way gdb tests for 
target compilers consistent.  currently, (missing) ada tests fail with:
  UNSUPPORTED: gdb.ada/tasks.exp: Ada compilation failed: default_target_compile
: Can't find gnatmake.

whereas missing fortran and java tests fail with:
UNTESTED: gdb.fortran/array-element.exp: Couldn't compile array-element.f
UNTESTED: gdb.java/jmain.exp: Couldn't compile /scratch/nathan/fsf/src/gdb-mai
nline/gdb/testsuite/gdb.java/jmain.java

This is inconsistent.  My understanding is that 'UNSUPPORTED' is the appropriate 
failure mode, as the test depends on conditionally available feature, which is 
not present.  UNTESTED is for when the testcase is not complete.

This patch changes the testsuite so that all cases of one of those compilers 
missing produces:

UNSUPPORTED: gdb.java/jmain.exp: compilation jmain.java

tested on i686-pc-linux-gnu where ada, java and fortran compilers were not present.

ok?

nathan

-- 
Nathan Sidwell    ::   http://www.codesourcery.com   ::         CodeSourcery

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: lang-test.diff
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20091103/31014d3e/attachment.ksh>


More information about the Gdb-patches mailing list