From 92c0223838d201746600a71a11a469e545928d83 Mon Sep 17 00:00:00 2001
From: mmitchel <mmitchel@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Thu, 5 May 2005 03:57:28 +0000
Subject: [PATCH] * docs/html/test.html: Explain how to run the
testsuite on an installed directory.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@99255 138bc75d-0d04-0410-961f-82ee72b054a4
---
libstdc++-v3/ChangeLog | 5 +++++
libstdc++-v3/docs/html/test.html | 17 +++++++++++++++++
2 files changed, 22 insertions(+)
diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog
index 3355220d7478..0eb21b15948f 100644
--- a/libstdc++-v3/ChangeLog
+++ b/libstdc++-v3/ChangeLog
@@ -1,3 +1,8 @@
+2005-05-04 Mark Mitchell <mark@codesourcery.com>
+
+ * docs/html/test.html: Explain how to run the testsuite on an
+ installed directory.
+
2005-05-01 Paolo Carlini <pcarlini@suse.de>
* config/os/aix/os_defines.h: Remove obsolete __off_t,
diff --git a/libstdc++-v3/docs/html/test.html b/libstdc++-v3/docs/html/test.html
index 947a277b62ca..d15dc427180a 100644
--- a/libstdc++-v3/docs/html/test.html
+++ b/libstdc++-v3/docs/html/test.html
@@ -509,6 +509,23 @@ multilibed build directory with different ABI settings:
make check-target-libstdc++-v3 RUNTESTFLAGS='--target_board \"unix{-mabi=32,,-mabi=64}\"'
</pre>
+<p>
+You can run the tests with a compiler and library that have already
+been installed. Make sure that the compiler (e.g., <code>g++</code>)
+is in your <code>PATH</code>. If you are using shared libraries, then
+you must also ensure that the directory containing the shared version
+of libstdc++ is in your <code>LD_LIBRARY_PATH</code>, or equivalent.
+If your GCC source tree is at <code>/path/to/gcc</code>, then you can
+run the tests as follows:
+<pre>
+runtest --tool libstdc++ --srcdir=/path/to/gcc/libstdc++-v3/testsuite
+</pre>
+The testsuite will create a number of files in the directory in which you
+run this command,. Some of those files might use the same name as
+files created by other testsuites (like the ones for GCC and G++), so
+you should not try to run all the testsuites in parallel from the same
+directory.
+</p>
<p> In addition, there are some testing options that are mostly of
interest to library maintainers and system integrators. As such,
--
GitLab