Hi Christophe,
Christophe Labouisse wrote:
>I've been trying to create a patch for the current Debian package to
>build the javahl bindings. In order to be compliant with Debian policy I
>had to put aside using Sun's JDK and work with alternative compilers:
>gcj & kaffe. Jikes is currently out because of a bug (issue 2057) but
>also because compiling the javahl bindings requires both javac & javah.
>
>Gcj is suggested in issue 2057 discussion and may be convenient as it
>includes gcjh which is a replacement for Sun's javah. This last part is
>currently not working because of a bug in gcjh which prevent it to
>generate #defines for java constants as the other javah compilers do
>(http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16843).
>
>Kaffe is not bad however, I ran into 2 bugs. The first one is most
>probably a Kaffe bug since in CommitMessage.cpp at line 106 uses
>NewObjectArray which is declared as returning a jarray in Kaffe's jni.h
>while CommitMessage.cpp wants to put it in a jobjectArray. The second
>one is also probably a Kaffe bug although I'm not really sure. In
>JNIByteArray.cpp, the getBytes method returns a signed char pointer
>while m_data is declared as jbyte*. This does not cause any problem with
>Sun's javah as jbyte is a typedef for signed char but Kaffe's definition
>of jbyte is char. Hence a compilation error on JNIByteArray.cpp line 80.
>
1. newObjectArray and all the other object array functions work with
jobjectArray in the sun include files, this is a bug in the include file.
2. jbyte should be a signed char, since the byte in java is also signed.
Since both error come from errors in the jni include files of Kaffe, I
would suggest that add the neccesary casts in your patch. I do not want
to add unneeded casts jast for buggy include files.
Patrick
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 29 10:20:47 2004