From 86abebe2167a2bec26217d7c8a0c7397c249e331 Mon Sep 17 00:00:00 2001
From: Mark Mitchell
Date: Thu, 5 May 2005 03:57:28 +0000
Subject: [PATCH] test.html: Explain how to run the testsuite on an installed
directory.
* docs/html/test.html: Explain how to run the testsuite on an
installed directory.
From-SVN: r99255
---
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 3355220..0eb21b1 100644
--- a/libstdc++-v3/ChangeLog
+++ b/libstdc++-v3/ChangeLog
@@ -1,3 +1,8 @@
+2005-05-04 Mark Mitchell
+
+ * docs/html/test.html: Explain how to run the testsuite on an
+ installed directory.
+
2005-05-01 Paolo Carlini
+You can run the tests with a compiler and library that have already
+been installed. Make sure that the compiler (e.g., g++
)
+is in your PATH
. If you are using shared libraries, then
+you must also ensure that the directory containing the shared version
+of libstdc++ is in your LD_LIBRARY_PATH
, or equivalent.
+If your GCC source tree is at /path/to/gcc
, then you can
+run the tests as follows:
+
+runtest --tool libstdc++ --srcdir=/path/to/gcc/libstdc++-v3/testsuite
+
+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.
+
In addition, there are some testing options that are mostly of interest to library maintainers and system integrators. As such, -- 2.7.4