This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: PATCH: Document running V3 tests on installed compiler
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: gcc-patches at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
- Date: Wed, 4 May 2005 21:36:15 +0000 (UTC)
- Subject: Re: PATCH: Document running V3 tests on installed compiler
- References: <200505042113.j44LDwMu024981@sethra.codesourcery.com>
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.)
--
Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/
jsm@polyomino.org.uk (personal mail)
joseph@codesourcery.com (CodeSourcery mail)
jsm28@gcc.gnu.org (Bugzilla assignments and CCs)