➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients andres, gvanrossum, loewis, nnorwitz, ronaldoussoren, simon.percivall
Date 2007-12-01.15:21:28
SpamBayes Score 0.01050686
Marked as misclassified No
Message-id <1196522489.34.0.317063399839.issue1358@psf.upfronthosting.co.za>
In-reply-to
Content 
This issue is fixed in the trunk and python2.5 branch.

To work around this issue with the 2.5.1 source tree you have to set 
MACOSX_DEPLOYMENT_TARGET when configuring python:

  ../configure <insert-args-here> MACOSX_DEPLOYMENT_TARGET=10.3

(the value 10.3 is what configure picks by default, building with 10.5 
as the target works as well). The problem is that configure picked a 
deployment target for use during compilation of python itself, but 
didn't use that during the configure phase. That causes configure to 
pick up the wrong set of feature macros.
History
Date User Action Args
2007-12-01 15:21:29ronaldoussorensetspambayes_score: 0.0105069 -> 0.01050686
recipients: + ronaldoussoren, gvanrossum, loewis, nnorwitz, simon.percivall, andres
2007-12-01 15:21:29ronaldoussorensetspambayes_score: 0.0105069 -> 0.0105069
messageid: <1196522489.34.0.317063399839.issue1358@psf.upfronthosting.co.za>
2007-12-01 15:21:29ronaldoussorenlinkissue1358 messages
2007-12-01 15:21:28ronaldoussorencreate