PATCH: Document running V3 tests on installed compiler

Mark Mitchell mark@codesourcery.com
Thu May 5 03:06:00 GMT 2005


Benjamin Kosnik wrote:

> This doesn't work for me..... 
> 
> runtest --tool libstdc++ --srcdir=/mnt/hd/src/gcc/libstdc++-v3/testsuite
> 
> WARNING: Couldn't find the global config file.
> Test Run By bkoz on Wed May  4 21:58:24 2005
> Native configuration is i686-redhat-linux-gnu
> 
>                 === libstdc++ tests ===
> 
> Schedule of variations:
>     unix
> 
> Running target unix
> Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
> Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
> Using /mnt/hd/src/gcc/libstdc++-v3/testsuite/config/default.exp as tool-and-target-specific interface file.
> Running /mnt/hd/src/gcc/libstdc++-v3/testsuite/libstdc++-abi/abi.exp ...
> Running /mnt/hd/src/gcc/libstdc++-v3/testsuite/libstdc++-dg/normal.exp ...
> ERROR: tcl error sourcing /mnt/hd/src/gcc/libstdc++-v3/testsuite/libstdc++-dg/normal.exp.
> ERROR: could not compile testsuite_character.cc
>     while executing
> "error "could not compile $f""
>     (procedure "v3-build_support" line 35)
>     invoked from within
> "v3-build_support"

What does libstdc++.log say about the file it tried to compile?  The 
message indicates that it's trying to build one of the files that used 
to be in libv3test, and got an error message from the compiler.

-- 
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304



More information about the Libstdc++ mailing list