This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

PATCH: testsuite/README* (was: 3.2/3.3/3.4 Lookup in Nested Class)


On Tue, 28 Jan 2003, Jeffrey Oldham wrote:
> Also, it is confusing why C++-specific information is in
> gcc/testsuite/README when there is a gcc/testsuite/README.g++ file.

That's a very valid point.  I am not a testsuite expert by any means,
but the following seems obvious, so I am going to install it.

Hopefully this improves the situation at least a bit.

Gerald

2003-01-28  Gerald Pfeifer  <pfeifer@dbai.tuwien.ac.at>

	* README: Move relevant parts from README.g++.

	* README.g++: Remove this file.

Index: README
===================================================================
RCS file: /cvs/gcc/gcc/gcc/testsuite/README,v
retrieving revision 1.6
diff -u -3 -p -r1.6 README
--- README	16 Oct 2000 10:00:23 -0000	1.6
+++ README	28 Jan 2003 17:00:52 -0000
@@ -48,3 +48,24 @@ DejaGnu drivers. But just because its ol
 Tests that want to use the normal dg.exp driver can be put in g++.dg instead.
 This may be required for platform-specific tests, or tests with other
 special requirements.
+
+
+Finally, some random last minute notes by Mike Stump <mrs@cygnus.com>, on
+how to run tests (in the GCC 2.7 era):
+
+	runtest --tool g++ --srcdir ./testsuite
+
+where
+
+	runtest	Is the name used to invoke DejaGnu.   If DejaGnu is not
+		install this will be the relative path name for runtest.
+
+	--tool	This tells DejaGnu which tool you are testing. It is
+		mainly used to find the testsuite directories for a
+		particular tool when several testsuites are in the
+		same directory. (like the gcc and g++ testsuites)
+
+	--srcdir This points to the top level of the directory
+		containing the sources of the testsuite. This is
+		./testsuite if you are in the directory that has the
+		testsuite directory.
Index: README.g++
===================================================================
RCS file: README.g++
diff -N README.g++
--- README.g++	16 Dec 1998 21:21:29 -0000	1.3
+++ /dev/null	1 Jan 1970 00:00:00 -0000
@@ -1,33 +0,0 @@
-Here are some random last minute notes by this file's original maintainer,
-Mike Stump <mrs@cygnus.com>:
-
-> and the command
-
->       runtest --tool g++ --srcdir ./testsuite
-
-> doesn't work.  I got it to work by explicitly setting CXX and CXXFLAGS
-> on the command line, e.g.
-
-> runtest --tool g++ --srcdir ./testsuite CXX=g++ CXXFLAGS=""
-
-site.exp updated to have right CXXFLAGS and CXX, but not at the FSF yet.
-
-
-  To run the tests, first change to the gcc-2.7.1 directory, then type:
-
-	runtest --tool g++ --srcdir ./testsuite
-
-Here's a brief explanation.
-
-runtest         - Is the name used to invoke DejaGnu.   If DejaGnu is not
-		  install this will be the relative path name for runtest.
-
---tool          - This tells DejaGnu which tool you are testing. It is
-                  mainly used to find the testsuite directories for a
-                  particular tool when several testsuites are in the
-                  same directory. (like the gcc and g++ testsuites)
-
---srcdir        - This points to the top level of the directory
-                  containing the sources of the testsuite. This is
-                  ./testsuite if you are in the directory that has the
-                  testsuite directory.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]