This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] merge java/test.html into install.texi and sourcebuild.texi
- From: Tom Tromey <tromey at redhat dot com>
- To: Janis Johnson <janis187 at us dot ibm dot com>
- Cc: Gcc Patch List <gcc-patches at gcc dot gnu dot org>
- Date: 12 Nov 2002 10:38:57 -0700
- Subject: Re: [PATCH] merge java/test.html into install.texi and sourcebuild.texi
- References: <20021112093931.A3615@us.ibm.com>
- Reply-to: tromey at redhat dot com
>>>>> "Janis" == Janis Johnson <janis187@us.ibm.com> writes:
Janis> This patch merges information from java/test.html into the main
Janis> GCC documents.
Thanks for doing this.
Janis> +The @uref{http://sources.redhat.com/mauve/,,Mauve Project} provides
Janis> +a suite of tests for the Java Class Libraries.
Janis> +libgcj supports Mauve testing. If you have Mauve checked out in,
Janis> +e.g., @file{~/mauve/}, then you can tell the libgcj to run the Mauve
Janis> +tests like so: @samp{make MAUVEDIR=~/mauve check}.
Recently I also added the ability to do this without setting an
environment variable. If the libgcj test suite finds the mauve tree
in gcc/libjava/testsuite/libjava.mauve/mauve, then it will use it
automatically. (This is more convenient sometimes, since you can just
do another checkout and use the normal test procedure.)
Janis> +We don't as yet have an automated mechanism to run Jacks tests in our test
Janis> +framework.
I added this recently too.
Currently the only way to run Jacks is to have the jacks source tree
in gcc/libjava/testsuite/libjava.jacks/jacks.
If you don't mind, please add this information to your patch.
If you'd rather, I can write a patch to update the docs after your
patch goes in.
Tom