Java support not detected on OS X 10.6 + Java Update 3
Imported from http://bugzilla.roxen.com/bugzilla/show_bug.cgi?id=5793
Reported by Jonas Wallden firstname.lastname@example.org
Apple recently shipped Java Update 3 for OS X 10.6. First, it ships without system headers so a separate developer package must be installed from e.g. connect.apple.com (requires a developer account).
However, even after this the JDK structure seems sufficiently different that Pike's configure script cannot detect proper paths and flags.
checking for JAVA_HOME... /Library/Java/JavaVirtualMachines/1.6.0_22-b04-307.jdk/Contents checking for Java architecture directory name... checking for Java libraries... no checking for the Java include directory... /Library/Java/JavaVirtualMachines/1.6.0_22-b04-307.jdk/Contents/Headers Adding /Library/Java/JavaVirtualMachines/1.6.0_22-b04-307.jdk/Contents/Headers to the include search path. Adding /Library/Java/JavaVirtualMachines/1.6.0_22-b04-307.jdk/Contents/Headers//. to the include search path. checking for JavaVM (MacOS X)... no checking for pkg-config... no checking -DMACOSX... yes checking for grep that handles long lines and -e... (cached) /usr/bin/grep checking for egrep... (cached) /usr/bin/grep -E checking for ANSI C header files... (cached) yes checking for sys/types.h... (cached) yes checking for sys/stat.h... (cached) yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for memory.h... (cached) yes checking for strings.h... (cached) yes checking for inttypes.h... (cached) yes checking for stdint.h... (cached) yes checking for unistd.h... (cached) yes checking jni.h usability... yes checking jni.h presence... yes checking for jni.h... yes checking for winbase.h... (cached) no checking for setjmp.h... (cached) yes checking ffi.h usability... no checking ffi.h presence... no checking for ffi.h... no checking ffi/ffi.h usability... yes checking ffi/ffi.h presence... yes checking for ffi/ffi.h... yes checking for ffi_arg... yes checking for ffi_sarg... yes checking for sysOpen in -lhpi... no checking for JNI_CreateJavaVM in -ljvm... no checking for JNI_CreateJavaVM in -lgcj... no
The closest symbol match to JNI_CreateJavaVM is located in $JAVA_HOME/Libraries/libjvm.dylib, though it's named _JNI_CreateJavaVM_Impl so I don't know if that is the proper one since it's 32-bit only. Here are a few candidates:
-rwxrwxr-x 1 root admin 3608352 12 Okt 07:20 libclient.dylib* lrwxr-xr-x 1 root admin 15 11 Nov 11:10 libclient64.dylib@ -> libserver.dylib lrwxr-xr-x 1 root admin 15 11 Nov 11:10 libjvm.dylib@ -> libclient.dylib -rwxrwxr-x 1 root admin 11543712 12 Okt 07:20 libserver.dylib*