statically linked tcl conflict with dynamically linked tcl error

[TingChong]

My solaris 8 computer have a dynamically linked tclsh as the default.
After another statically linked tclsh is executed, the computer
environment is corrupted for that shell.
How to solve this problem?

This is what I had done:
pwdly0ee% which tclsh
/opt/bsmext/bin/tclsh

pwdly0ee% /opt/bsm/lib/home/bsmbin/tcma/tclsh
application-specific initialization failed: Can't find a usable
init.tcl in the following directories:
/bsmbootstrap/lib/tcl8.3 /opt/bsm/lib/home/bsmbin/lib/tcl8.3
/opt/bsm/lib/home/lib/tcl8.3 /opt/bsm/lib/home/bsmbin/library
/opt/bsm/lib/home/library /opt/bsm/lib/home/tcl8.3/library
/opt/bsm/lib/tcl8.3/library /bsmbootstrap/lib/tcl8.3



This probably means that Tcl wasn't installed properly.

% ls
invalid command name "ls"

[Rich Teer]

On 5 Aug 2003, TingChong wrote:

> My solaris 8 computer have a dynamically linked tclsh as the default.
> After another statically linked tclsh is executed, the computer
> environment is corrupted for that shell.
> How to solve this problem?

Don't use statically linked binaries.

--
Rich Teer, SCNA, SCSA

President,
Rite Online Inc.

Voice: +1 (250) 979-1638
URL: [url]http://www.rite-online.net[/url]