On Mon, Aug 11, 2003 at 04:23:55PM +0100, David Goodenough wrote: > Looking at the configure file, and the bits that make it up, there is some > specific hand coded function to look for various bits of the JVM that > is to be used, much of which does not exist in GCJ. For a start they > look for an executable called javac, and do not seem to ask > update-alternatives if javac is defined (which would be the Debian > way - or should be).
You should change it to invoke gcj-wrapper rather than javac, if you want to ensure that it uses gcj (which would be appropriate for a package build). > They then look for java in the bin directory of JAVAHOME, libjvm.so > and then various checks for green libraries, and a bunch of include > files and finish off checking that this java knows about JNI. JAVA_HOME seems silly in Debian, where we have alternatives to manage these things. I wish it would go away. Does it actually use libjvm.so? Probably most of these checks can be disabled. -- - mdz