-with-mauve on configure at this point is there any real use? If not
what is
the plan? ( I'm trying to help classpath build the test cases with
mauve, and
I pick kissme as my vm cause John had build deb support for it and I use
debian :) )
I don't know what the plan is yet :-)
John,
I'll try post some new instructions for running mauve and kissme soon.
No need. I've just added rules to the Kissme makefile and updated
doc/BUILDING to document them.
-- Steve
___
Classpath mailing list
[EMAIL PROTECTED]
Stephen Crawley :
-with-mauve on configure at this point is there any real use? If not
what is
the plan? ( I'm trying to help classpath build the test cases with
mauve, and
I pick kissme as my vm cause John had build deb support for it and I use
debian :) )
I don't know what the plan
Alex == Alex Lau [EMAIL PROTECTED] writes:
Alex That kind of give me a bad feeling how solid the test base are (
Alex not the test case ) e.g. gnu/testlet/SimpleTestHarness.java
Alex Unless the test case is bad also ( I read a couple test cast,
Alex some shouldn't fail in jdk, but it did )
Yeah... :) Get that build finally... I do need 1.6 automake...
Yup. That's what the Kissme doc/BUILDING document says. In fact,
I built the Kissme automake/configure scripts using version 1.6.1.
Sorry about that.. I'm still getting use to all the cvs structure (
kissme, classpath
Yup. That's what the Kissme doc/BUILDING document says. In fact,
I built the Kissme automake/configure scripts using version 1.6.1.
Sorry about that.. I'm still getting use to all the cvs structure (
kissme, classpath
and mauve). And I just find out doc/ get Building info rather then
Alex,
John Leuner [EMAIL PROTECTED]
Alex Lau [EMAIL PROTECTED],
In some document mention kissme can't know handle zip/jar file, what's
that mean? it seem working fine with
./kissme -classpath classes:/usr/share/classpath/glibj.zip:. myclass
The native zip support is very new. It
John Leuner :
Hello Alex
I'm sorry for responding so late.
If you want to build Classpath 0.04 and kissme you must do the following:
1. Unpack and build classpath
./configure --enable-jni --with-jikes
make
make install
this work ok. I'm not sure I understand the concept ... so
If you want to build Classpath 0.04 and kissme you must do the following:
1. Unpack and build classpath
./configure --enable-jni --with-jikes
make
make install
this work ok. I'm not sure I understand the concept ... so the VM build
after
the classpath? I always throught
Yeah... :) Get that build finally... I do need 1.6 automake...
However
./kissme -classpath classes:/usr/share/classpath/glibj.zip:. helloworld
debug: lost error code 1, (loading class helloworld from
java/lang/Class): Could not find a .class file for this class
Hello world
It run but don't
Yeah... :) Get that build finally... I do need 1.6 automake...
Yup. That's what the Kissme doc/BUILDING document says. In fact,
I built the Kissme automake/configure scripts using version 1.6.1.
However
./kissme -classpath classes:/usr/share/classpath/glibj.zip:. helloworld
debug:
Hello Alex
I'm sorry for responding so late.
If you want to build Classpath 0.04 and kissme you must do the following:
1. Unpack and build classpath
./configure --enable-jni --with-jikes
make
make install
2. Get kissme from CVS
(and also)
mkdir kissme-classpath
touch
12 matches
Mail list logo