Hi Jasper. On Wed, Feb 7, 2018 at 2:35 PM, Jasper Taylor <jas...@simulistics.com> wrote: > > Thanks for looking at my problem. I don't have anything relevant under > /usr/local -- the search paths are built into the package. > > I also have access to a Debian system with tk 8.6.0+8 installed. On this > system, I run tclsh and type > > set auto_path > > and get > > /usr/share/tcltk/tcl8.6 /usr/share/tcltk /usr/lib /usr/local/lib/tcltk > /usr/local/share/tcltk /usr/lib/tcltk/x86_64-linux-gnu /usr/lib/tcltk > /usr/lib/tcltk/tcl8.6
That's a typical auto_path value on a Debian system. > > and then running > > package require Tk > > returns 8.6.2 and opens a toplevel Tk window. Which is as it should be. > > Now on my own system with tk 8.6.0+9 I run tclsh and type > > set auto_path > > and get > > /usr/local/lib/tcl8.6 /usr/local/lib /usr/lib This likely means that you run not /usr/bin/tclsh, or your /usr/bin/tclsh is not a link to /usr/bin/tclsh8.6, or maybe there's some other unknown yet problem. Can you show the output of ls -al /usr/bin/tclsh* (for me it currenly outputs lrwxrwxrwx 1 root root 8 Nov 20 2015 /usr/bin/tclsh -> tclsh8.6* -rwxr-xr-x 1 root root 6336 Mar 21 2016 /usr/bin/tclsh8.5* -rwxr-xr-x 1 root root 6352 Jul 28 2016 /usr/bin/tclsh8.6* -rwxr-xr-x 1 root root 6280 Jan 12 12:03 /usr/bin/tclsh8.7* ) and the output of which tclsh (for me it outputs /usr/bin/tclsh ) And what if you execute /usr/bin/tclsh instead of tclsh? Cheers! -- Sergei Golovan