Ronald Oussoren added the comment: 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. ---------- nosy: +ronaldoussoren resolution: -> fixed status: open -> closed __________________________________ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1358> __________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
