Botched Tcl installation?

Liste des GroupesRevenir à cl tcl 
Sujet : Botched Tcl installation?
De : luc (at) *nospam* sep.invalid (Luc)
Groupes : comp.lang.tcl
Date : 25. Jul 2025, 02:50:07
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <20250724225007.59e8a36e@lud1.home>
Hello, tclers. Long time no see.

I still use that same old Debian installation. Or almost the same.

I had a problem with it and "reinstalled" it. In fact, I didn't
perform the usual orthodox installation. I have a faithful copy of
the / directory structure. So I had a problem, so I had to recover
from backup and I did. Just pure rsync. The operating system works
fine again. The problem is, this backup wasn't properly updated with
a newer Tcl/Tk.

In the old installation, I had built 8.6.15 from source, installed
it in /opt then removed tclsh and wish from /usr/bin and replaced
them with symlinks to /opt/tcltk8615/bin/tclsh8.6 and wish8.6.
But I am not really sure if that was all I did. I just remember
that everything seemed to work fine back then.

So I symlinked tclsh and wish again, /opt/tcltk8615/ is the same
as the old one (/opt is in fact a symlink to a separate partition
that wasn't changed at all).

I thought there was something wrong because not all Unicode
characters were rendered correctly in text widgets, but then
they were in a second test. Shrug. OK!

Now, I am working on a new project and I need to use the command
::thread::queue which I'm told it doesn't exist. Upon investigation,
it seems I also need the command thread::tpool::init which is also
absent.

When I run package require Thread I get 2.8.10. Is that enough?
What about my 8.6.15 "installation"? Is the symlink kludge I
did enough? Have I missed some important step? Whh do you think?

Thank you for any help.

--
Luc
>


Date Sujet#  Auteur
25 Jul02:50 o Botched Tcl installation?1Luc

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal