Thread: [tcljava-user] problems installing tclBlend on Linux

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

I'm trying to install tclBlend (and therefore tcl and the thread
package)
on the following Linux system:

SUSE Linux Enterprise Server 9 SP2 OS. 
Dual 2.8 GHz Xeon processors.

Because SUSE had Tcl 8.4.6 installed, I went with Tcl/Tk 8.4.6.  The
java JDK
used is the IBMJava2-1.4.2 package from SUSE's repository.

(With this JDK, jacl built OK, but now I see that if I "make test" it
gets to
tcl/stack.test and then errors out with "make: *** [test_jacl.exec]
Error 139".)

The tcl built OK and passed its tests (with threads enabled).

The thread package built OK and passed its tests.

[/usr/local/src/tclBlend1.3.2]# ./configure
--with-tcl=/usr/local/src/tcl8.4.6
--with-thread=/usr/local/src/thread2.6.2
srcdir is /usr/local/src/tclBlend1.3.2
checking for Tcl build in /usr/local/src/tcl8.4.6
checking for Thread build in /usr/local/src/thread2.6.2
Tcl executable /usr/local/src/tcl8.4.6/unix/tclsh works
Tcl was compiled with Thread support
checking for jikes... no
checking for javac... /usr/lib/java/bin/javac
checking for zip or jar files to include on CLASSPATH...
/usr/lib/java/jre/lib/core.jar
checking to see if the java compiler works... yes
checking to see if the java compiler accepts forward slashes... yes
Java found in /usr/lib/java
checking type of jvm... jdk
checking java API version... 1.3
checking for java... /usr/lib/java/bin/java
checking for java_g... no
checking for javah... /usr/lib/java/bin/javah
checking for jar... /usr/lib/java/bin/jar
checking for jdb... /usr/lib/java/bin/jdb
checking for ddd... /usr/bin/ddd
checking for gdb... /usr/bin/gdb
checking for gcc... gcc -pipe
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc -pipe accepts -g... yes
checking for gcc -pipe option to accept ANSI C... none needed
Using the following JNI include flags -I/usr/lib/java/include
checking to see if jni.h can be included... yes
Using the following JNI library flags -lpthread -L/usr/lib/java/jre/bin
-ljava -L/usr/lib/java/jre/bin/classic -ljvm -lhpi
Using the following runtime library path
/usr/lib/java/jre/bin:/usr/lib/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.

Would using the standard Sun (which suppose means Blackdown) JDK work
better?  Is this
a known problem?  (Not that I could tell from the archives.)  Are there
specific things
I can test myself to get better identification of the problem?

Thanks,

escargo 

---

David Cargo
Sr. Principal Engineer

Email: Dav...@Xi...
Office: 952 983 2372
Fax: 952 983 2320

Xiotech Corporation
6455 Flying Cloud Drive
Eden Prairie, MN 55344 

www.xiotech.com : www.xiotech.com/demo : Toll-Free 866 472 6764