From: Andrew M. <an...@ob...> - 2005-02-15 02:34:04
|
>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! ;) Hmmm - either it statically linked with the sybase client lib, or it's pulling in shared libs by hand. Anyone on the list have a better idea what it's up to? You might want to try running strace (linux) or truss (solaris) on python as it starts. Something like: strace -o /tmp/trace.out -f python -ic "import Sybase" The contents of trace.out will be too large to post to the list, but reading through it might give some clues as to how it's pulling in the client libs. Jump to where it's reading sybasect.so and see what happens after that. -- Andrew McNamara, Senior Developer, Object Craft http://www.object-craft.com.au/ |