Re: Linking errors when compiled with both python and python3

[Andy Kittner]

On Fri, Jul 23, 2010 at 07:17:24PM -0400, James Vega wrote:

On Fri, Jul 23, 2010 at 11:05:05PM +0200, Andy Kittner wrote:

Running ldd on the files in the lib-dynload directory reveals that
out of my installed python versions (2.4.6, 2.5.4, 2.6.5, 2.7,
3.1.2) revealed that all c-extensions except those for 2.4.6 are
linked against the corresponding libpython.so

That's interesting.  As far as I can tell, Python's build system doesn't
do this normally.  It would appear your distribution (which is?) has
changed that.

    ./configure --prefix=/tmp/pytest2 --enable-shared && make && make install

Which results in this output from ldd:
ldd /tmp/pytest2/lib/python2.6/lib-dynload/termios.so
         linux-vdso.so.1 =>  (0x00007fffa8eac000)
         libpython2.6.so.1.0 => /usr/lib/libpython2.6.so.1.0 
(0x00007f6bc5553000)
         libpthread.so.0 => /lib/libpthread.so.0 (0x00007f6bc5336000)
         libc.so.6 => /lib/libc.so.6 (0x00007f6bc4fd6000)
         libdl.so.2 => /lib/libdl.so.2 (0x00007f6bc4dd2000)
         libutil.so.1 => /lib/libutil.so.1 (0x00007f6bc4bcf000)
         libm.so.6 => /lib/libm.so.6 (0x00007f6bc494c000)
         /lib64/ld-linux-x86-64.so.2 (0x00007f6bc5b72000)

So as you can see it is linked against the libpython.so.

(I case you are wondering, pytest1 was a plain configure without any arguments
but --prefix, but that didn't even build a shared python lib that could be 
dlopen()ed)

Regards,
Andy
--
Steal this tagline.  I did.

I'm on gentoo linux, but it doesn't look related to any of the gentoo specific patches to python. I manually compiled python fresh from the original source tarball without any patches using the following commands:

pgphnjCQb9SCt.pgp
Description: PGP signature