[ python-Bugs-1095822 ] Apple-installed Python fails to build extensions

[SourceForge.net]

Bugs item #1095822, was opened at 2005-01-04 16:43
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1095822&group_id=5470

Category: Macintosh
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jack Jansen (jackjansen)
Assigned to: Jack Jansen (jackjansen)
Summary: Apple-installed Python fails to build extensions

Initial Comment:
Apple-installed Python 2.3 (on Mac OS X 10.3) can no longer build 
extension modules after a newer framework build has been 
installed.

This happens because it will build extensions with "-framework 
Python", which will actually link against the newer framework (be 
it 2.3.X or 2.4 or later) that is in /Library in stead of against it's 
own framework in /System/Library.

After over a year of debating multiple solutions the Pythonmac-SIG 
consensus is that linking extensions with "-undefined 
dynamic_lookup" in stead of against the framework is the best 
solution.

All of 2.5a0, 2.4.1 and 2.3.5 will detect the fact that they are being 
run on a machine that has an Apple-installed python that needs to 
be patched, and apply that patch. A standalone patch installer will 
also be made available.

In addition, 2.5a0, 2.4.1 and 2.3.5 themselves will also use the 
-undefined dynamic_lookup method of linking when running on 
10.3 or later (unless the user has specifically set 
MACOSX_DEPLOYMENT_TARGET to 10.2 or earlier).

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

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