> When I started this project back in March, I could not get anything to work with JDK
>1.1.8, Tcl
> 8.3, and TclBlend 1.2.5, so I used Tcl 8.2.3. I do not remember now what the symptom
>was, just
> that it didn't work. (I am using JDK 1.1.8 because of warnings about JDK 1.2 at
> http://dev.scriptics.com/software/java/faq.html#Q4.)
Thats is odd, the only problem I know of is Tcl 8.2 and the whole
vfork vs fork mess. Tcl 8.3 is the way to go if you ask me. That
"warning" about JDK 1.2 only matters if you are using the TclClassloader
to load new .class files without putting them on the CLASSPATH.
> Tcl, or TclBlend? I have not compiled Tcl... should I? (I'm using the binary
>distribution of Tcl.)
> I will see if I can get anywhere with this approach.
Ok, the very first thing you need to do is nuke and precompiled
code and compile Tcl 8.3.1 with debug symbols enabled. Then
reconfigure and rebuild Tcl Blend, it will automatically notice that you
compiled Tcl with debug and include debug info in libtclblend.so.
This sort of thing is the exact reason there are only Windows
binaries on the Tcl Blend 1.2.6 download site. It is safer
to just build things by yourself.
Mo DeJong
Red Hat Inc
----------------------------------------------------------------
The TclJava mailing list is sponsored by Scriptics Corporation.
To subscribe: send mail to [EMAIL PROTECTED]
with the word SUBSCRIBE as the subject.
To unsubscribe: send mail to [EMAIL PROTECTED]
with the word UNSUBSCRIBE as the subject.
To send to the list, send email to '[EMAIL PROTECTED]'.
An archive is available at http://www.mail-archive.com/tcljava@scriptics.com
