Mauve on Solaris 2.8

Thu Apr 4 16:21:00 GMT 2002

Hi,
On Thu, 2002年04月04日 at 20:57, Andrew Haley wrote:
> > Can you tell me what versions of these tools you used? I don't seem
> > to be able to find a combination that works.
>> Ah, OK. I found automake-gcj-1.4.tar.gz

And does it work? I remember complaining that Classpath used automake
1.5 but Mauve needed 1.4. If I remember correctly Brian Jones then fixed
mauve to be useable with automake 1.5. I don't remember exactly from
when my version is.
But I just tried with a fresh CVS checkout. And doing:
mark@elsschot:~/src/gcc-3.2/obj$ export MAUVEDIR=/tmp/mauve
mark@elsschot:~/src/gcc-3.2/obj$ rm -rf \
	i686-pc-linux-gnu/libjava/testsuite/mauve-build
mark@elsschot:~/src/gcc-3.2/obj$ make check-target-libjava
Seems to work out of the box on my machine now.
So no aclocal; ; autoheader; automake; autoconf dance needed.
(make/configure output attached.)
At the moment the number of failures is a bit high (~200) and some of
these are actually faults in the testsuite or tests that produce lots of
failures because we have not yet implemented something. So running it is
not very productive at the moment.
I am working on getting this number down a bit, hopefully to zero FAIL
when we release 3.1 (with xfails for things we now are broken in libgcj
at the moment) so we can really use it regularly again when we start
work on 3.2.
Cheers,
Mark
-------------- next part --------------
Running /home/mark/src/gcc-3.2/gcc/libjava/testsuite/libjava.mauve/mauve.exp ...checking for a BSD compatible install... /bin/sh /home/mark/src/gcc-3.2/gcc/install-sh -c
checking whether build environment is sane... yes
checking for mawk... mawk
checking whether make sets ${MAKE}... yes
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 a BSD compatible install... /bin/sh /home/mark/src/gcc-3.2/gcc/install-sh -c
configure: creating ./config.status
config.status: creating Makefile
config.status: creating gnu/testlet/config.java
make[4]: Entering directory `/opt/src/gcc-3.2/obj/i686-pc-linux-gnu/libjava/testsuite/mauve-build'
Makefile:351: choices: No such file or directory
ok=no; \
if test -f .save-keys && test -f choices && test "`cat .save-keys`" = "libgcj"; then \
 ok=yes; \
fi; \
here=`/bin/pwd`; \
if test "$ok" = no; then \
 echo "libgcj" > .save-keys; \
 cd /tmp/mauve && /bin/sh choose $here libgcj; \
fi
find: com: No such file or directory
make[4]: Leaving directory `/opt/src/gcc-3.2/obj/i686-pc-linux-gnu/libjava/testsuite/mauve-build'
make[4]: Entering directory `/opt/src/gcc-3.2/obj/i686-pc-linux-gnu/libjava/testsuite/mauve-build'
ok=no; \
if test -f .save-keys && test -f choices && test "`cat .save-keys`" = "libgcj"; then \
 ok=yes; \
fi; \
here=`/bin/pwd`; \
if test "$ok" = no; then \
 echo "libgcj" > .save-keys; \
 cd /tmp/mauve && /bin/sh choose $here libgcj; \
fi
/home/mark/src/gcc-3.2/obj/gcc/gcj -B/home/mark/src/gcc-3.2/obj/gcc/ --encoding=UTF-8 -B/home/mark/src/gcc-3.2/obj/i686-pc-linux-gnu/libjava/testsuite/../ -I/home/mark/src/gcc-3.2/obj/i686-pc-linux-gnu/libjava/testsuite/../libgcj.zip -C -g gnu/testlet/config.java
here=`/bin/pwd`; cd /tmp/mauve; \
 CLASSPATH=$CLASSPATH:$here:`/bin/pwd` /home/mark/src/gcc-3.2/obj/gcc/gcj -B/home/mark/src/gcc-3.2/obj/gcc/ --encoding=UTF-8 -B/home/mark/src/gcc-3.2/obj/i686-pc-linux-gnu/libjava/testsuite/../ -I/home/mark/src/gcc-3.2/obj/i686-pc-linux-gnu/libjava/testsuite/../libgcj.zip -C -g -d $here \
[... long line of classes ...]
touch classes.stamp
make[4]: Leaving directory `/opt/src/gcc-3.2/obj/i686-pc-linux-gnu/libjava/testsuite/mauve-build'
FAIL: gnu.testlet.java.io.BufferedByteOutputStream.interrupt: single-byte writes (number 3)
FAIL: gnu.testlet.java.io.BufferedByteOutputStream.interrupt: single-byte writes (number 4)
FAIL: gnu.testlet.java.io.File.jdk11: getCanonicalPath () java.io.IOException: No such file or directory (number 1)
[... etc ...]