not able to install ActiveTcl

Posted by ldhamoda_cisco on 2008-12-24 00:58

Downloaded ActiveTcl8.5.5.0.287690-solaris-ix86-threaded.tar.gz and untared the .tar.gz file and tried to install in solaris 10 server. Not able install TCL.

while trying to install getting this error :

# sh install.sh
install.sh: ./payload/bin/tclsh8.5: cannot execute

ldhamoda_cisco | Wed, 2008-12-24 04:36

from /ActiveTcl-8.5/bin executing

% teacup install Expect
Resolving Expect ... [package Expect 5.44.1.11 solaris2.8-sparc @ http://teapot.
activestate.com]
Resolving Tcl 8.4 -is package ... [package Tcl 8.5.5 _ ... Installed outside rep
ository, probing dependencies]

Retrieving package Expect 5.44.1.11 solaris2.8-sparc ...@ http://teapot.activest
ate.com ... Ok

Installing into /opt/ActiveTcl-8.5/lib/teapot

Installing package Expect 5.44.1.11 solaris2.8-sparc
INTERNAL ERROR ______________________
INTERNAL ERROR No TEAPOT meta data found in TM archive "/tmp/tpmuXqLZYiuZM", no
embedded meta data block

wcf3 | Tue, 2008-12-30 11:54

A clean install of ActiveTcl8.5.5.0.287690-win32-ix86-threaded on a clean Windows 2000 SP4 system followed by 'teacup update-self' followed by 'teacup update' leads to the same type error for multiple packages:

INTERNAL ERROR ______________________
INTERNAL ERROR No TEAPOT meta data found in TM archive "C:/Documents and Setting
s/user/Local Settings/Temp/tpmv2LXt2XM4a", no embedded meta data block
INTERNAL ERROR     while executing
INTERNAL ERROR "# Compiled -- no source code available
INTERNAL ERROR error "called a copy of a compiled script""
INTERNAL ERROR     (procedure "::repository::api::Snit_methodsync" line 1)

To get around this I was simply removing the package that failed and the installing it again, then return to the update for the next failure. However I'm stuck at Canvas3d and can't get past it. Some of the other packages that failed were: img::tiff, sqlite3, and vfs. I think they were all win32-ix86 packages that failed.

There doesn't appear to be a way around the problem now...

Chuck

jeffh
ActiveState Staff
Tue, 2009-01-13 11:44

This was due to a cluster cache consistency issue which we was unresolved at the time this was posted. We have since resolved those issues (new machines were introduced into the cluster, but not fully updated). Please try again.