On Oct 12, 2004 at 21:50, David Jansen in a soothing rage wrote: >After compiling a package which is linked to tcl/tk I noticed it doesn't >want to run on other machines. It turns out that the package was linked >using -ltcl -ltk, so it requires libtcl.so and libtk.so, but: >$ rpm -qf /usr/lib/libtcl.so >tcl-devel-8.4.5-7 >$ rpm -qf /usr/lib/libtk.so >tk-devel-8.4.5-8 > >So those libraries are part of the -devel rpms. Is this a bug in >packaging, or should software explicitly link to a specific version, >e.g. -ltcl8.4 -ltk8.4 ? (since libtcl8.4.so is part of the tcl-8.4.5-7 >rpm). >Or is it really necessary to have these -devel rpms present on every >machine? (which would be problematic since tk-devel has a dependency on >the X devel rpms so this would pull in a lot of additional stuff) You did not tell us the full story... [work]$ locate libtcl /usr/lib/libtcl8.4.so ... /usr/lib/libtcl.so [work]$ ls -al /usr/lib/libtcl.so lrwxrwxrwx 1 root root 12 Jun 3 14:49 /usr/lib/libtcl.so -> libtcl8.4.so So we now see that libtcl.so is a symlink to libtcl8.4.so. Therefore create these symlinks on the other machines. Repeat for libtk.so as well. N.Emile... -- Registered Linux User # 125653 (http://counter.li.org) Switch to: http://www.speakeasy.net/refer/190653 Confessions may be good for the soul, but they are bad for the reputation. -- Lord Thomas Dewar 18:26:35 up 106 days, 11:41, 3 users, load average: 0.00, 0.00, 0.00
