Solaris 2.6 is not 64bit, that's Solaris 7 (only on UltraSPARC
machines).
I've been able to get TclBlend 1.2.5 to work on Solaris
2.5.1, 2.6, and 2.7 with JDK 1.1.8 and 1.2.2.
There are several patches to install on Solaris 2.6 for
JDK 1.2.2, but I don't think that's the case for 1.1.8,
but you should check. The JDK/JRE that ships with
Solaris is 1.1.6 or so, which should work fine even
if you built with 1.1.8.
-- Scott
Moses DeJong wrote:
>
> On Mon, 22 Nov 1999, Suvarna Ayyagari wrote:
>
> >
> > Hi,
>
> Humm, Solaris 2.6 is the 64 bit version of the OS right? I have
> yet to run Tcl Blend on a 64 bit OS.
>
> > I have installed tclblend1.2.5. the installation went fine. I built it on
> > Solaris 2.6 with JDK 1.1.8 with native threads and Tcl8.0.5.
> >
> > I used it from this area and I had no problems using it anytime.
>
> Is the production box the same version of Solaris? If not this might
> be a 32/64 bit mismatch problem.
>
> > I now wanted to install it in our prod area. the installation went fine. But
> > when I use this version, in one of the scripts which passed earlier, I get a
> > Segmentation fault now.
>
> Perhaps you ftped the file and forgot to turn binary mode on. I make
> that mistake a lot. If you just moved the file from one system to
> another the size of the file should not change.
>
> > I checked the size of the libtclblend.so (the one which gave me no problems
> > and the one which is giving me problems) in both directories. They are
> > different though I built it with the same tclblend and jdk on the same
> > operating system.
>
> Configure and compile Tcl with --enable-symbols. This will add debug
> symbols to Tcl. After doing that, configure Tcl Blend again and recompile
> Tcl Blend. Tcl Blend will notice that Tcl was compiled with symbols
> and it will also add debug symbols. The only thing to watch out for
> is that the native compiler on Solaris (cc) does not actually add
> debug symbols unless you pass the -g and -xs option to the compiler.
> gcc or egcs will add debug symbols with the -g flag. Now that you
> have debug symbols fire up tclblend using the jtclsh shell script
> and type pid to get the process id. Now go to a different xterm,
> start up gdb and attach it to the Tcl process (like so "gdb TCLPATH pid").
> After gdb starts up type "cont" at the gdb command prompt to keep
> running your Tcl shell. Now switch back to the Tcl shell and type
> "package require java" into the shell. If it crashes, you should be
> able to see where it crashed in the gdb window. You should be able
> to get a stack trace at the point where it crashed by typing "bt"
> at the gdb prompt.
>
> > How do I debug this?
>
> The jtclsh script installed when you build Tcl Blend should set
> the LD_LIBRARY_PATH and CLASSPATH env vars for you. You might
> also want to check the rld linking of libtclblend.so by typing
> "ldd libtclblend.so" at the command line.
>
> I hope that helps
> Mo DeJong
>
> > Now when I do a package require java, the Tclblend which is in the
> > LD_LIBRARY_PATH is picked up right?
>
> ----------------------------------------------------------------
> 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]'.
----------------------------------------------------------------
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]'.
