diff options
| author | Benjamin Kosnik <bkoz@redhat.com> | 2004-03-01 17:42:01 +0000 |
|---|---|---|
| committer | Benjamin Kosnik <bkoz@gcc.gnu.org> | 2004-03-01 17:42:01 +0000 |
| commit | 6728336267457f71da6261ab59e3fedd4f987d8d (patch) | |
| tree | a65cd5bb6475469c09f4b793faab3b7364277ae7 /libstdc++-v3/docs/html/test.html | |
| parent | 98e953f57b334e690be6b162cc18df798b579f3c (diff) | |
| download | gcc-6728336267457f71da6261ab59e3fedd4f987d8d.zip gcc-6728336267457f71da6261ab59e3fedd4f987d8d.tar.gz gcc-6728336267457f71da6261ab59e3fedd4f987d8d.tar.bz2 | |
test.html: Add multilib RUNTESTFLAGS example.
2004-03-01 Benjamin Kosnik <bkoz@redhat.com>
* docs/html/test.html: Add multilib RUNTESTFLAGS example.
* docs/html/18_support/howto.html: Add bit about writing to
stderr, mostly by Zack.
From-SVN: r78709
Diffstat (limited to 'libstdc++-v3/docs/html/test.html')
| -rw-r--r-- | libstdc++-v3/docs/html/test.html | 11 |
1 files changed, 9 insertions, 2 deletions
diff --git a/libstdc++-v3/docs/html/test.html b/libstdc++-v3/docs/html/test.html index 8c76111..a4ef5ec 100644 --- a/libstdc++-v3/docs/html/test.html +++ b/libstdc++-v3/docs/html/test.html @@ -477,11 +477,11 @@ or make check-target-libstdc++-v3 RUNTESTFLAGS="-v -v" </pre> + There are two ways to run on a simulator: set up DEJAGNU to point to a specially crafted site.exp, or pass down --target_board flags. Example flags to pass down for various embedded builds are as follows: - <pre> --target=powerpc-eabism (libgloss/sim) make check-target-libstdc++-v3 RUNTESTFLAGS="--target_board=powerpc-sim" @@ -492,7 +492,14 @@ make check-target-libstdc++-v3 RUNTESTFLAGS="--target_board=calmrisc32-sid" --target=xscale-elf (newlib/sim) make check-target-libstdc++-v3 RUNTESTFLAGS="--target_board=arm-sim" </pre> - + +<p> Also, here is an example of how to run the libstdc++ testsuite for a +multilibed build directory with different ABI settings: +</p> +<pre> +make check-target-libstdc++-v3 RUNTESTFLAGS='--target_board \"unix{-mabi=32,,-mabi=64}\"' +</pre> + <p> To run a subset of the library tests, simply edit the generated file, <em>testsuite_files </em>, to include only the files that are desired instead of all available test cases. |