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:
On Wed, 4 May 2005, Mark Mitchell wrote:


+ <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>
+ </p>


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.)

It is safe to share between runs, although probably not (due to testsuite lameness) not simultaneous runs. I'll add some additional verbiage.


--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304


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