I only did a configure (with --with-cdebug) in the src directory
of
the CVS tree and a make in the upper directory gives the same
result.
I also have the same problem under FreeBSD.
If you (or someone) make it runs and detect on freebsd using
whatever
jdk api (I'd like to use diablo-jdk since it is native one), then I
own
you (or him) a pack of beer.
I don't think the problem is FreeBSD specific. I got this problem on Linux and fixed it and before I had the same problem with FreeBSD (didn't try to fix it). I think the configure script of this module is broken and that's the only reason. I got it to work by simply adding every libs Java needed in my ld.so.conf (it also seems there was more than the configure say), modify by hand configure to force it to say that my JVM really really works and to shut up and then it worked fine. The thing I don't get is why gcc can't find the Java libraries if you give all the paths with -L.
/ David