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 ronaldoussoren, tarek
Date 2010-04-18.20:44:07
SpamBayes Score 4.805225e-08
Marked as misclassified No
Message-id <1271623450.52.0.5635482395.issue8444@psf.upfronthosting.co.za>
In-reply-to
Content
setup.py detects the version of openssl by looking for openssl headers on a deduced search path. That path is not guaranteed to be equal to the real compiler search path, in particular not when building using the OSX 10.4 SDK on MacOSX 10.6: in that situation the compiler will use a header file with the following definition:

#define OPENSSL_VERSION_NUMBER  0x009070cfL

While setup.py reads the header file in /usr/include which contains this definition:

#define OPENSSL_VERSION_NUMBER  0x009080cfL

The actual version is below the sha256 cutoff in setup.py, while setup.py detects a newer version that is above that cutoff. That results in a tree where setup.py tries to build _sha256 using OpenSSL, but fails. That in turn results in a build of hashlib that doesn't work.


Note that this is a specific instance of Issue7724, but fixing this particular issue is probably easier than fixing the generic issue.
History
Date User Action Args
2010-04-18 20:44:10ronaldoussorensetrecipients: + ronaldoussoren, tarek
2010-04-18 20:44:10ronaldoussorensetmessageid: <1271623450.52.0.5635482395.issue8444@psf.upfronthosting.co.za>
2010-04-18 20:44:08ronaldoussorenlinkissue8444 messages
2010-04-18 20:44:07ronaldoussorencreate