Re: Can't find a usable init.tcl ... Tcl wasn't installed correctly
Available news archives: comp.lang.tcl - comp.lang.python - comp.security.firewalls - sci.crypt - comp.lang.php - comp.lang.javascript
Google
 
Web news.hping.org


comp.lang.tcl archive

Re: Can't find a usable init.tcl ... Tcl wasn't installed correctly

From: Don Porter <dgp@email.nist.gov>
Date: Mon Mar 06 2006 - 18:35:40 CET

In article <0d_Of.1893$kg.1014@news02.roc.ny>, Patrick wrote:
> I built a toy tcl/tk program with an embedded interpreter. It works as
> expected under Linux.
>
> When I run the program from the Windows XP command prompt,
> initialization of the embedded interpreter fails, returning a message like:
>
> -----------------------------------------------------------
> Can't find a usable init.tcl in the following directories:

What was here? Was there a long list of directories that
you trimmed away when posting?

If not something is very very weird.

If so, then you trimmed exactly the part that might allow
me to help you.

> This probably means that Tcl wasn't installed correctly.
> -----------------------------------------------------------
>
>
> I tried again after executing
>
> SET TCL_LIBRARY=C:\Tcl\Lib\tcl8.4
>
> from the command prompt, and the Tcl_Init call succeeded.
>
> Have I actually installed Tcl incorrectly? I just accepted all the
> default settings rather dumbly during installation.

Please state exactly what Tcl you installed. Where did it come
from, and what version did it claim to be?

> Will I have to set TCL_LIBRARY like this each time I want to run such a
> program?

That's the last-resort workaround, you will always have available,
but with a proper install, it ought not be needed.

Even if your install programs can't be solved, you can always
take care of the issue within the code of your "toy tcl/tk program".

-- 
| Don Porter          Mathematical and Computational Sciences Division |
| donald.porter@nist.gov             Information Technology Laboratory |
| http://math.nist.gov/~DPorter/                                  NIST |
|______________________________________________________________________|
Received on Sun Apr 30 02:25:01 2006