#1880 prepare variable like TCL_PACKAGE_PATH in tcl.

obsolete: 8.4.9
Don Porter

I don't know whether this is the problem of Fedora
Core, tk, or blt.

On Fedora Core and Red Hat Enterprise and its clone
distributions, tk is made as
make TK_LIBRARY=/usr/share/tk8.4.9

As a result, pkgIndex.tcl is installed to
/usr/lib/tk8.4.9/ and other stuff installed to

And then, build BLT from source, bltwish cannot find
So I request to add a mechanism like TCL_PACKAGE_PATH
in tcl.


1 2 > >> (Page 1 of 2)
  • Don Porter
    Don Porter

    • status: open --> pending
  • Don Porter
    Don Porter

    • labels: 318657 --> 74. Application Embedding
    • assigned_to: hobbs --> dgp
    • milestone: --> obsolete: 8.4.9
    • status: pending --> pending-works-for-me
  • Don Porter
    Don Porter

    Logged In: YES

    Set the variable TK_LIBRARY at
    runtime to /usr/share/tk8.4.9 and
    tk.tcl will be found.

    Then complain to RedHat about
    delivering you a broken install,
    that you're required to work around
    with environment variables set a

    • status: pending-works-for-me --> open-works-for-me
  • Logged In: YES

    Don, do you have a better way of handling "multilib" libraries,
    since this is really the root of this issue.

    Multilib is used on some 64bit archs (eg x86_64 in particular)
    to allow both 32bit and 64bit programs to be able to run.
    So eg on x86_64 i386 (ia32) libs are in /usr/lib whereas
    64bit libs live in /usr/lib64: for this reason pkgIndex.tcl is
    currently installed under $libdir and not $datadir in Fedora
    since it points to the binary library. If tcl/tk could provide
    better support for this situation it would be much appreciated.

  • Don Porter
    Don Porter

    Logged In: YES

    The location of the pkgIndex.tcl
    file and the location of the tk.tcl
    initialization script don't necessarily
    have anything to do with each other,
    so I don't really follow the last comment.

    The question is why Fedora Core
    has chosen to install tk.tcl and
    other parts of Tk's script library
    in a different place from where Tk
    expects to find it, isn't it?

    Does the "wish" program exhibit
    similar problems, or is this just
    an issue for programs like bltwish
    that embed Tk?

    hmmm.. reading the original report
    more carefully, I see it refers to
    directories named "tk8.4.9". Standard
    Tk will install the script library into
    a directory named "tk8.4" and look
    in directories also with that name.
    Is that the root of the problem?

    If so, I'd expect "wish" to be just as
    broken as "bltwish", unless it's
    received other tweaking as well.

  • Don Porter
    Don Porter

    Logged In: YES

    I found a tk-8.4.9-3.src.rpm file
    "on the web" and though I'm no
    RPM expert, the spec file included
    sure looks like it's set up to set
    TK_LIBRARY to <datadir>/tk8.4 .

    Is the original report in error?
    Am I looking at the wrong RPM?
    Can you point me to the source
    RPM that's at issue, please?

  • Don Porter
    Don Porter

    Logged In: YES

    hmmm... key phrase here might be
    "build BLT from source". Can the
    original reporter please reveal
    what version of BLT that was?
    Pointer to a tarball if possible?

  • Don Porter
    Don Porter

    Logged In: YES

    another detail that might help...

    when a program reports the
    "can't find a usable tk.tcl" error,
    it normally reports a list of
    directories where it looked.
    Can the original reporter report
    that information as well, please?

1 2 > >> (Page 1 of 2)