On 4-feb-2006, at 3:02, Kevin Ollivier wrote:

Hi Bill,

On Feb 3, 2006, at 5:29 PM, Bill Northcott wrote:

On 04/02/2006, at 12:00 PM, Bob Ippolito wrote:
The issue only arises using Python 2.4.x on Tiger.  It does not
arise
with Python 2.3.x on Tiger or Python 2.4.x on Panther (MacOS 10.3.x)

On top of that, it should only happen if you're using a Python
2.4.x build on Tiger that was compiled on Panther.

Why would it not happen if Python 2.4 was built on Tiger?

Quoting a message Ronald wrote a few days back, when we were
discussing universal builds:

"Python's configure has hardcoded that OSX 10.2 and 10.4 must not
have _POSIX_SOURCE and friends defined. Annoyingly this means that if
you build Python on Panther you'll have to patch the build if you
want to build extensions on Tiger."

In other words, on Tiger and Jaguar, Python does not define
_POSIX_C_SOURCE, in which case everything goes smoothly. I didn't
remember this point until Bob mentioned the patch...

My patch for this is here: http://www.python.org/sf/1416559

This turns of _POSIX_C_SOURCE for 10.2, 10.3 and 10.4.

Ronald

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

Reply via email to