This is the mail archive of the
mailing list for the libstdc++ project.
Re: Distributing 'make check' across a cluster
- From: Jeff Law <law at redhat dot com>
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Cc: Diego Novillo <dnovillo at google dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>, libstdc++ at gcc dot gnu dot org, gcc <gcc at gcc dot gnu dot org>
- Date: Thu, 31 May 2012 21:26:02 -0600
- Subject: Re: Distributing 'make check' across a cluster
- References: <4FC7791E.firstname.lastname@example.org> <Pine.LNX.email@example.com> <4FC781FA.firstname.lastname@example.org> <20120531162258.68555b63@adair>
On 05/31/2012 05:22 PM, Benjamin Kosnik wrote:
I think this still works -- AFAIK Red Hat's QE team makes use of this
Thanks. Having the source tree available is not a problem, as I
require it to copy the actual testsuites into the work tree. Adding
a few more files from the source tree would not be a problem.
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
Anyway. I don't test this way often, so all I know is that it used to
work. If you have problems let me know and I'll fix 'em.