[tcljava-user] Support for JDK 1.4.1?
Brought to you by:
mdejong
From: <PFi...@hb...> - 2004-06-02 11:05:07
|
Have working TclBlend installation on Windows XP. Components are: TclBlend 1.3.1 tcl8.4.4 thread 25 IBM JDK 1.3. Tried to configure against IBM JDK 1.4.1 shipped with WebSphere. Config script detects 1.4.1 jdk as 1.3 "checking java API version... 1.3". Config fails with link error. checking to see if we can link a JNI application... no configure: error: could not link file that includes jni.h Either the configure script does not know how to deal with this JVM configuration or the JVM install is broken or corrupted. Is there support for JDK 1.4.1? ----------------------------------------------------------------------------------------------- PYF@ISDW1031 /src/tclblend1.3.1 $ ./configure --with-tcl=/src/tcl8.4.4/win --with-jdk=/c/IBM/WebSphere51/AppSer ver/java --with-thread=/src/thread25 configure: loading site script /etc/config.site srcdir is /src/tclblend1.3.1 checking for Tcl build in /src/tcl8.4.4/win checking for Thread build in /src/thread25 Tcl executable /src/tcl8.4.4/win/tclsh84 works Tcl was compiled with Thread support checking for jikes... no checking for zip or jar files to include on CLASSPATH... Grabbing user supplied CLASSPATH env var /c/IBM/WebSphere51/AppServer/java/lib/tools.jar:/c/IBM/WebSphere51/AppServer/java/lib/dt.jar:/c/IBM/WebSphere51/AppServer/java/jre/lib/rt.jar:/c/IBM/WebSphere51 /AppServer/java/jre/lib/jsse.jar:/c/IBM/WebSphere51/AppServer/java/jre/lib/jce.jar checking to see if the java compiler works... yes checking to see if the java compiler accepts forward slashes... yes Java found in /c/IBM/WebSphere51/AppServer/java checking type of jvm... jdk checking java API version... 1.3 checking for java... /c/IBM/WebSphere51/AppServer/java/bin/java checking for java_g... no checking for javah... /c/IBM/WebSphere51/AppServer/java/bin/javah checking for jar... /c/IBM/WebSphere51/AppServer/java/bin/jar checking for jdb... /c/IBM/WebSphere51/AppServer/java/bin/jdb checking for ddd... no checking for gdb... /mingw/bin/gdb checking for gcc... gcc checking for C compiler default output... a.exe checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... .exe checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed Using the following JNI include flags -I/c/IBM/WebSphere51/AppServer/java/include checking to see if jni.h can be included... yes Using the following JNI library flags /c/IBM/WebSphere51/AppServer/java/lib/jvm.lib Using the following runtime library path /c/IBM/WebSphere51/AppServer/java/jre/bin:/c/IBM/WebSphere51/AppServer/java/jre/bin/classic checking to see if we can link a JNI application... no configure: error: could not link file that includes jni.h Either the configure script does not know how to deal with this JVM configuration or the JVM install is broken or corrupted. ============================================================ HBF Health Funds Inc. a registered organisation under the National Health Act HBF Insurance Pty Ltd ACN 009 268 27 This email is a confidential communication intended only for the named Addressee(s). If you are not that person any disclosure, copying, distribution or use of this email or the information in it is prohibited. Please notify us immediately by telephone, (+61) 08 9265 6111 or return email and delete this email. |