Re: [tcljava-dev] Problem using configure

[Mo D. <su...@ba...>]

On Thu, 11 Apr 2002 22:47:10 -0400
Shawn Boyce <sh...@bo...> wrote:

> I get the following error when using configure on RedHat Linux 7.2
> and Sun JDK 1.3.1.
> 
> checking whether cc accepts -g... yes
> Using the following JNI include flags -I/usr/java/jdk1.3.1_02/include
> -I/usr/java/jdk1.3.1_02/include/linux
> checking to see if jni.h can be included... yes
> Using the following JNI library flags
> Using the following runtime library path
> checking to see if we can link a JNI application... configure: error:
> could not link file that includes jni.h
>         It is likely that your JVM install is broken or corrupted.
> 
> -Shawn

I am willing to bet the libs have been moved and the configure script
will need to be updated so that it knows how to detect them in the
new location. It is a real PITA but it needs to be done for just about
every JDK release because it changes every time. Just an FYI,
if you only plan on using Jacl you can pass --enable-jacl to the
configure script and it will skip these Tcl Blend checks.

Could you open up tcljava.m4 in your editor and have a look at
the AC_JAVA_JNI_LIBS macro? Inside that macro there are
some lib location checks that end up setting the variable
ac_java_jvm_jni_lib_flags. Your output seemed to indicate
that this var was not set and that it what caused the linker problem.
Note that you will need to regenerate the configure script with
autoconf 2.5X after making these changes.

cheers
Mo