From: Andrew T. <and...@ap...> - 2005-02-15 00:27:58
|
On Mon, 2005-02-14 at 15:42 +1100, Andrew McNamara wrote: > What does the output of: > > $ ldd /usr/local/lib/python2.4/site-packages/sybasect.so > > look like? Andrew, Here's the output.. looks good? [ajt@scratch ajt]$ ldd /usr/local/lib/python2.4/site-packages/sybasect.so libpthread.so.0 => /lib/tls/libpthread.so.0 (0x004c9000) libc.so.6 => /lib/tls/libc.so.6 (0x00e6a000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x008af000) I also did it for my 2.2 installation.. [ajt@scratch ajt]$ ldd /usr/lib/python2.2/site-packages/sybasect.so libc.so.6 => /lib/tls/libc.so.6 (0x0070b000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00a14000) Looks exciting! ;) Regards, ajt. > > I know very little about Sybase (I don't have it installed, either), > but I've been working with the dynamic linkers under Linux (and Solaris) > for years. I've seen this specific problem mentioned on the list a few > times, but I can't find a solution in the list archives. The error is > more suggestive of an incorrect library version, rather than a missing > file, so pay careful attention to the paths. > > You can also use ldd to explore the shared dependancies of any other > libraries being used by sybasect.so. > -- Andrew Thomson <and...@ap...> |