[ python-Bugs-1655392 ] thirdparty extensions, --enable-shared, static linking

[SourceForge.net]

Bugs item #1655392, was opened at 2007-02-08 17:16
Message generated for change (Comment added) made by gbrandl
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1655392&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Build
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Marien Zwart (marienz)
Assigned to: Georg Brandl (gbrandl)
Summary: thirdparty extensions, --enable-shared, static linking

Initial Comment:
(I'm filing this under the "Build" category which may not be entirely accurate, but couldn't find a closer match. Is there a description of what the categories mean somewhere?).

Python 2.5 built with --enable-shared on linux produces a shared libpython2.5.so in the "normal" libdir and only a static libpython2.5.a in /usr/lib/python2.5/config. Normally when you build extensions you want them to link to the dynamic one. However python-config --ldflags has -L/usr/lib/python2.5/config in its output, causing build processes using it to prefer the static library over the dynamic one.

This is somewhat similar to bug 1600860: distutils does the same thing when compiling extensions in an --enable-shared python 2.5.

I think either python-config should be modified to not mention that "config" dir on an --enable-shared build or the build process should be modified to put a .so file next to the .a file in that directory.


----------------------------------------------------------------------

>Comment By: Georg Brandl (gbrandl)
Date: 2007-03-31 18:58

Message:
Logged In: YES 
user_id=849994
Originator: NO

Fixed in rev. 54634, 54636.

----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2007-02-09 12:46

Message:
Logged In: YES 
user_id=21627
Originator: NO

The categories aren't described anywhere.

python-config should describe the installed code; we shouldn't change what
gets installed how for 2.5.1.

Georg, with python-config being your code, can you take a look? If not,
please unassign (in which case I'd ask marienz whether he would like to
contribute a patch).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1655392&group_id=5470