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]

Re: PATCH: Document running V3 tests on installed compiler


Joseph S. Myers wrote:

Should this say to use runtest in an empty temporary directory because it will create many temporary files and not necessarily remove all of them afterwards? (I don't know whether it is safe to share that directory between simultaneous runs of the libstdc++, g++, gcc etc. testsuites.)

Revised thusly. OK to apply?


--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304
2005-05-04  Mark Mitchell  <mark@codesourcery.com>

	* docs/html/test.html: Explain how to run the testsuite on an
	installed directory. 

Index: test.html
===================================================================
RCS file: /cvs/gcc/gcc/libstdc++-v3/docs/html/test.html,v
retrieving revision 1.10
diff -c -5 -p -r1.10 test.html
*** test.html	7 Apr 2005 04:16:07 -0000	1.10
--- test.html	4 May 2005 21:41:10 -0000
*************** multilibed build directory with differen
*** 507,516 ****
--- 507,533 ----
  </p>
  <pre>
  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,
     these tests may not work on all cpu and host combinations, and may need to
     be executed in the <em>libbuilddir/testsuite</em> directory.  These options

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