Ugh! Frustration. <*sigh*> Egg on face <-- the life of a developer!
Sorry about that - the cvs login is now working for me, too. I tried
it multiple times over the course of two days, so I assumed it was
broken.
So I checked out the latest from the repository and tried again.
Unfortunately, it didn't solve my problem - mauve is still failing.
However, upon closer inspection, it looks like the Java tests might be
getting run 2x, and mauve.exp seems to run without problems the first
time. I run the general regression tests for gcc via the following:
cd <BUILD_DIR>
make -k check
>From this, I see (note the reference to mauve.exp):
***
...
=== libjava tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/source/gcc-4.7.2/libjava/testsuite/config/default.exp as tool-and-target-specific interface file.
Running /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/source/gcc-4.7.2/libjava/testsuite/libjava.cni/cni.exp ...
Running /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/source/gcc-4.7.2/libjava/testsuite/libjava.jar/jar.exp ...
Running /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/source/gcc-4.7.2/libjava/testsuite/libjava.jni/jni.exp ...
Running /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/source/gcc-4.7.2/libjava/testsuite/libjava.jvmti/jvmti-interp.exp ...
LD_LIBRARY_PATH=. /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/i686-pc-linux-gnu/./libjava/gij -cp /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/source/gcc-4.7.2/libjava/testsuite/libjava.jvmti/interp/getargssize.jar -agentlib:dummyagent getargssize
LD_LIBRARY_PATH=. /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/i686-pc-linux-gnu/./libjava/gij -cp /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/source/gcc-4.7.2/libjava/testsuite/libjava.jvmti/interp/getlocalvartable.jar -agentlib:dummyagent getlocalvartable
LD_LIBRARY_PATH=. /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/i686-pc-linux-gnu/./libjava/gij -cp /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/source/gcc-4.7.2/libjava/testsuite/libjava.jvmti/interp/getstacktrace.jar -agentlib:dummyagent getstacktrace
Running /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/source/gcc-4.7.2/libjava/testsuite/libjava.jvmti/jvmti.exp ...
Running /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/source/gcc-4.7.2/libjava/testsuite/libjava.lang/lang.exp ...
Running /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/source/gcc-4.7.2/libjava/testsuite/libjava.loader/loader.exp ...
Running /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/source/gcc-4.7.2/libjava/testsuite/libjava.mauve/mauve.exp ...
Running /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/source/gcc-4.7.2/libjava/testsuite/libjava.special/special.exp ...
Running /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/source/gcc-4.7.2/libjava/testsuite/libjava.verify/verify.exp ...
=== libjava Summary ===
# of expected passes 2574
make[4]: Leaving directory `/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/i686-pc-linux-gnu/libjava/testsuite'
make[3]: Leaving directory `/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/i686-pc-linux-gnu/libjava/testsuite'
make[3]: Entering directory `/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/i686-pc-linux-gnu/libjava'
: make ; exec make "AR_FLAGS=rc" "CC_FOR_BUILD=gcc" "CFLAGS=-g -O2" "CXXFLAGS=-g -O2 -D_GNU_SOURCE" "CPPFLAGS=" "CFLAGS_FOR_BUILD=-g -O2" "CFLAGS_FOR_TARGET=-g -O2" "INSTALL=/usr/bin/install -c" "INSTALL_DATA=/usr/bin/install -c -m 644" "INSTALL_PROGRAM=/usr/bin/install -c" "INSTALL_SCRIPT=/usr/bin/install -c" "GCJFLAGS=-g -O2" "LDFLAGS=" "LIBCFLAGS=-g -O2" "LIBCFLAGS_FOR_TARGET=-g -O2" "MAKE=make" "MAKEINFO=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/source/gcc-4.7.2/missing makeinfo --split-size=5000000 --split-size=5000000 " "PICFLAG=" "PICFLAG_FOR_TARGET=" "SHELL=/bin/bash" "RUNTESTFLAGS=" "exec_prefix=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/install" "datadir=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/install/share" "infodir=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/install/share/info" "libdir=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/install/lib" "mandir=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/install/share/man" "prefix=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/install" "gxx_include_dir=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/install/include/c++/4.7.2" "AR=ar" "AS=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/./gcc/as" "DLLTOOL=dlltool" "LD=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/./gcc/collect-ld" "LIBCFLAGS=-g -O2" "NM=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/./gcc/nm" "PICFLAG=" "RANLIB=ranlib" "DESTDIR=" "JAR=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/i686-pc-linux-gnu/libjava/scripts/jar" DO=all multi-do
make[4]: Entering directory `/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/i686-pc-linux-gnu/libjava'
if [ -z "" ]; then \
true; \
else \
rootpre=`${PWDCMD-pwd}`/; export rootpre; \
srcrootpre=`cd /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/source/gcc-4.7.2/libjava; ${PWDCMD-pwd}`/; export srcrootpre; \
lib=`echo "${rootpre}" | sed -e 's,^.*/\([^/][^/]*\)/$,\1,'`; \
compiler="/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/./gcc/xgcc -B/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/./gcc/ -B/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/install/i686-pc-linux-gnu/bin/ -B/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/install/i686-pc-linux-gnu/lib/ -isystem /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/install/i686-pc-linux-gnu/include -isystem /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/install/i686-pc-linux-gnu/sys-include "; \
for i in `${compiler} --print-multi-lib 2>/dev/null`; do \
dir=`echo $i | sed -e 's/;.*$//'`; \
if [ "${dir}" = "." ]; then \
true; \
else \
if [ -d ../${dir}/${lib} ]; then \
flags=`echo $i | sed -e 's/^[^;]*;//' -e 's/@/ -/g'`; \
if (cd ../${dir}/${lib}; make "AR_FLAGS=rc" "CC_FOR_BUILD=gcc" "CFLAGS=-g -O2" "CXXFLAGS=-g -O2 -D_GNU_SOURCE" "CPPFLAGS=" "CFLAGS_FOR_BUILD=-g -O2" "CFLAGS_FOR_TARGET=-g -O2" "INSTALL=/usr/bin/install -c" "INSTALL_DATA=/usr/bin/install -c -m 644" "INSTALL_PROGRAM=/usr/bin/install -c" "INSTALL_SCRIPT=/usr/bin/install -c" "GCJFLAGS=-g -O2" "LDFLAGS=" "LIBCFLAGS=-g -O2" "LIBCFLAGS_FOR_TARGET=-g -O2" "MAKE=make" "MAKEINFO=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/source/gcc-4.7.2/missing makeinfo --split-size=5000000 --split-size=5000000 " "PICFLAG=" "PICFLAG_FOR_TARGET=" "SHELL=/bin/bash" "RUNTESTFLAGS=" "exec_prefix=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/install" "datadir=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/install/share" "infodir=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/install/share/info" "libdir=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/install/lib" "mandir=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/install/share/man" "prefix=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/install" "gxx_include_dir=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/install/include/c++/4.7.2" "AR=ar" "AS=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/./gcc/as" "DLLTOOL=dlltool" "LD=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/./gcc/collect-ld" "LIBCFLAGS=-g -O2" "NM=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/./gcc/nm" "PICFLAG=" "RANLIB=ranlib" "DESTDIR=" "JAR=/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/i686-pc-linux-gnu/libjava/scripts/jar" \
CFLAGS="-g -O2 ${flags}" \
CCASFLAGS=" ${flags}" \
FCFLAGS=" ${flags}" \
FFLAGS=" ${flags}" \
ADAFLAGS=" ${flags}" \
prefix="/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/install" \
exec_prefix="/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/install" \
GCJFLAGS="-g -O2 ${flags}" \
GOCFLAGS="-O2 -g ${flags}" \
CXXFLAGS="-g -O2 -D_GNU_SOURCE ${flags}" \
LIBCFLAGS="-g -O2 ${flags}" \
LIBCXXFLAGS="-g -O2 -D_GNU_SOURCE -fno-implicit-templates ${flags}" \
LDFLAGS=" ${flags}" \
MULTIFLAGS="${flags}" \
DESTDIR="" \
INSTALL="/usr/bin/install -c" \
INSTALL_DATA="/usr/bin/install -c -m 644" \
INSTALL_PROGRAM="/usr/bin/install -c" \
INSTALL_SCRIPT="/usr/bin/install -c" \
all); then \
true; \
else \
exit 1; \
fi; \
else true; \
fi; \
fi; \
done; \
fi
make[4]: Leaving directory `/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/i686-pc-linux-gnu/libjava'
make[3]: Leaving directory `/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/i686-pc-linux-gnu/libjava'
make[2]: Leaving directory `/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/i686-pc-linux-gnu/libjava'
...
***
Later in my build script, I explicitly run
cd <BUILD_DIR>/i686-pc-linux-gnu/libjava/testsuite
make MAUVEDIR=<SOURCE_DIR>/../mauve -k check
(I have a symlink "mauve" in the parent directory of my gcc source
directory that points to my mauve source directory.)
>From this, I get:
*****
...
Running /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/source/gcc-4.7.2/libjava/testsuite/libjava.mauve/mauve.exp ...
configure: WARNING: unrecognized options: --with-gcj
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking how to create a pax tar archive... gnutar
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for Windows and DOS and OS/2 style pathnames... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... none
configure: creating ./config.status
config.status: creating Makefile
config.status: creating gnu/testlet/config.java
config.status: executing depfiles commands
configure: WARNING: unrecognized options: --with-gcj
make[2]: Entering directory `/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/i686-pc-linux-gnu/libjava/testsuite/mauve-build'
cd /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/source/../mauve && /bin/bash /home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/mauve/missing --run automake-1.10 --foreign Makefile
aclocal.m4:16: warning: this file was generated for autoconf 2.65.
You have another version of autoconf. It may work, but is not guaranteed to.
If you have problems, you may need to regenerate the build system entirely.
To do so, use the procedure documented by the package, typically `autoreconf'.
cd . && /bin/bash ./config.status Makefile
config.status: creating Makefile
make[2]: Leaving directory `/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/i686-pc-linux-gnu/libjava/testsuite/mauve-build'
make[2]: Entering directory `/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/i686-pc-linux-gnu/libjava/testsuite/mauve-build'
make[2]: *** No rule to make target `classes.stamp'.
make[2]: Leaving directory `/home/youngmj/DevTools/Gnu_Compiler_Collection-gcc/Version_4.7.2/build/i686-pc-linux-gnu/libjava/testsuite/mauve-build'
FAIL: Mauve build
...
*****
So, again, I still see "--with-gcj" as an unrecognized configure
option. I have autoconf 2.68 (not 2.65); I'm not sure how significant
the warning about that is. And then the make complains about an
invalid target "classes.stamp" (no rules defined for it).
I explicitly run the libjava testsuite make check (in addition and
subsequent to the overall make check) based on my impression from what
I read in the docs - in the section titled "Additional testing for Java
Class Libraries" at "http://gcc.gnu.org/install/test.html". ; Since this
is "additional" testing, I assumed that I had to invoke it specifically,
but it appears that the general make may pick it up in any case. Of
course, if that's true, it's probably not really doing anything right
now (other than screwing up the configure/make), since it shouldn't
find the actual mauve directory. (I don't have it in the build or
source directory tree, which is why I was using the MAUVEDIR variable.)
I apologize for the long post - I'm just trying to give the relevant info!
So my questions are:
1) Must I explicitly run the libjava/testsuite make separate from
the general "make check" for the overall gcc regression tests in order
to fully test gcj/libjava (including using mauve)?
2) Is it possible to run the libjava testsuite multiple times
(without any intervention in between runs) without problems?
3) If I can/should not run the libjava testsuite separately, can I
simply set the MAUVEDIR variable on the "make check" invocation for the
overall regression tests so that it can be used for the mauve testing
via mauve.exp?
4) What am I doing wrong?
Thanks,
Mike
----------------------------------------
> Date: Wed, 20 Feb 2013 09:27:21 +0000
> From: aph@xxxxxxxxxx
> To: mikado_282@xxxxxxxxxxx
> CC: gcc-help@xxxxxxxxxxx
> Subject: Re: Testing gcj/libgcj with mauve
>
> On 02/19/2013 06:52 PM, Michael Young wrote:
>>
>>
>> I'm trying to build and test the gcc Java compiler and library on a typical PC running Linux (target is "i686-pc-linux-gnu"; I'm actually running Ubuntu 12.04). So I read the following at "http://gcc.gnu.org/install/test.html":
>>
>> ****
>> The Java runtime tests can be executed via `make check' in the target/libjava/testsuite directory in the build tree.
>>
>> The Mauve Project provides a suite of tests for the Java Class Libraries. This suite can be run as part of libgcj testing by placing the Mauve tree within the libjava testsuite at libjava/testsuite/libjava.mauve/mauve, or by specifying the location of that tree when invoking `make', as in `make MAUVEDIR=~mauve check'.
>> ****
>>
>> OK - sounds simple enough. But I go to get mauve, and it *appears* to be an abandoned project at "http://www.sourceware.org/mauve/";. Snapshots are not available as advertised, no recent activity on the mailing lists, source available via CVS (not svn or git), etc.
>> Attempting to anonymously login to the CVS repository per the instructions on the mauve website gets me nowhere:
>>
>> ****
>> $ cvs -d :pserver:anoncvs@xxxxxxxxxxxxxx:/cvs/mauve login
>> Logging in to :pserver:anoncvs@xxxxxxxxxxxxxx:2401/cvs/mauve
>> CVS password: <- I enter "anoncvs" here
>> cvs [login aborted]: unrecognized auth response from sourceware.org: Service temporarily unavailable, please try again later
>> $
>
> Works for me:
>
> zebedee:~ $ cvs -d :pserver:anoncvs@xxxxxxxxxxxxxx:/cvs/mauve login
> Logging in to :pserver:anoncvs@xxxxxxxxxxxxxx:2401/cvs/mauve
> CVS password:
> zebedee:~ $ cvs -d :pserver:anoncvs@xxxxxxxxxxxxxx:/cvs/mauve co mauve
> U mauve/.classpath
> U mauve/.cvsignore
> U mauve/.project
> U mauve/COPYING
>
> Andrew.
