[Starkit] Re: question about tclkit builds for Linux
Jean-Claude Wippler
jcw at equi4.com
Fri Aug 25 11:09:14 CEST 2006
Hi Tom,
> I have switch from a HP-UX system to RedHat Linux on a Sun that
> gives me the following.
>
> % uname -a
> Linux az34lnx11 2.4.21-40.EL #1 Thu Feb 2 22:20:41 EST 2006 x86_64
> x86_64 x86_64 GNU/Linux
>
> I went to http://www.equi4.com/pub/tk/downloads.html and downloaded
>
> Linux, x86 64, 8.4.13
>
> When I tryed running the tclkit I got
>
> ./tclkit8.4.13: error while loading shared libraries: libstdc++.so.
> 6: cannot open shared object file: No such file or directory
[...]
Can you run "ldd" and see what it reports? Maybe a symlink with the
expected name is enough to force it to run?
> Q1: What OS was used to do the Linux builds?
The tclkit for x86_64 was built on my Gentoo Linux AMD box (which
tends to track linux/gcc/libc/etc releases quite quickly in general).
> Q2: Does the above listing from the /usr/lib directory look
> resonable to you? It looks strange to me.
I don't know why there are so many files on your system, but it kinds
of illustrates the huge compatibility mess of the g++/stdc++ combo on
Unix. After all these years of C++'s evolution, this is *precisely*
why I consider C++ virtually undeployable.
I've not tried the trick of linking stdc++ statically into tclkit
(while leaving the rest dynamic).
BTW, if you want to verify that the problem is entirely due to C++,
try a tclkit lite version.
You could build tclkit yourself using genkit to get a working binary
for your setup.
-jcw
More information about the Starkit
mailing list