Thanks for the effort. I did discover the same problem. My solution was to use Sun's Java packaged with java-package instead of kaffe. Then the compile went fine, including all checks. (Though I wasn't planning to use javahl so I could just have avoided building this package.)
I simply changed the line confflags += --enable-javahl --without-jikes --with-jdk=/usr/lib/kaffe to confflags += --enable-javahl --without-jikes --with-jdk=/usr/lib/j2sdk1.4-sun in debian/rules. With sid, the original 1.2.3a builds fine so I guess the kaffe(?) bug has been fixed there. Others have mentioned good experiences from using (rebuilt) 1.2.3a on sarge systems, so I think it is just fine to go ahead. Anders On Mon, 2005-09-26, at 18:45:42 -0400, Roberto C. Sanchez wrote: > On Wed, Sep 21, 2005 at 04:55:28PM +0200, Anders Lennartsson wrote: > > Does it break anything essential to build and use the sources for > > subversion 1.2.3a, found in sid, for sarge? The build dependencies in > > debian/control can be met on a properly maintained sarge box, but > > perhaps this may not be the full truth or? > > > > I just tried to build it in a Sarge chroot and here is the result: > > /tmp/buildd/subversion-1.2.3a/build-tree/subversion-1.2.3/subversion/bindings/java/javahl/native/JNIByteArray.cpp:80: > error: invalid > conversion from `jbyte*' to `const signed char*' > make[1]: *** [subversion/bindings/java/javahl/native/JNIByteArray.lo] Error 1 > make[1]: Leaving directory > `/tmp/buildd/subversion-1.2.3a/build-tree/subversion-1.2.3' > make: *** [debian/stamp-build] Error 2 > pbuilder: Failed autobuilding of package > > I imagine that if you took the time to track down the error and patch > the package, then you could make it work. > > -Roberto > -- > Roberto C. Sanchez > http://familiasanchez.net/~roberto -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
