Conflict between ActiveTcl version

jeffh — Fri, 07 Mar 2008 23:50:29 +0000

You should not need or use the LD_LIBRARY_PATH pointer to ActiveTcl. Just set your path right, and it should pick up the right libraries for the current version of Tcl. To make it more clear, you should install in more clearly delineated directory names, like:
/opt/ActiveTcl-8.4.12-x86
/opt/ActiveTcl-8.4.18-x64

and then symlink one of those to /opt/ActiveTcl-8.4 if you require it.

Conflict between ActiveTcl version

krishnan_tom — Fri, 07 Mar 2008 14:07:07 +0000

hi ,
I faced another problem w.r.t the ActiveTcl version,
these the steps :
1) I have a ActiveTcl-8.4.12(32-bit) with my application installed on Suse-10(64-bit) and ActiveTcl-8.4.18(64-bit) been installed on the same m/c at /opt.

2)When i am running my application from /home, i got an error stating that "The TclPro ByteCode Loader is not available or does not support the correct version -- couldn't load file "/opt/ActiveTcl-8.4/lib/tcl8.4/tbcload1.7/libtbcload1.7.so": /opt/ActiveTcl-8.4/lib/tcl8.4/tbcload1.7/libtbcload1.7.so: wrong ELF class: ELFCLASS64"

3) Actually i want my application to use ActiveTcl which is in my application [ActiveTcl - 8.4.12]. But it considers the ActiveTcl in /opt which is of a higher version.

4) Later i found out that the above error was because i exported as below:
export LD_LIBRARY_PATH=Active Tcl path in my application

Please suggest me the reason and solution.

ActiveState Community Site - Conflict between ActiveTcl version - Comments

Conflict between ActiveTcl version

Conflict between ActiveTcl version