➜

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 hirenvadalia
Recipients christian.heimes, hirenvadalia
Date 2017-08-04.13:03:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1501851817.64.0.525660205253.issue31120@psf.upfronthosting.co.za>
In-reply-to
Content 
I did some more digging into this and I found something strange:
So while compiling Python, it downloads externals from http://svn.python.org/projects/external/
Above site has many version of openssl so I looked into all openssl directory and found that from openssl version 0.9.8g we have ‘buildinf_amd64.h’ file under http://svn.python.org/projects/external/openssl-0.9.8g/crypto/ till openssl version 1.0.2f and after that we don’t have ‘*_amd64.h’ file under openssl-*/crypro directory and that is the reason 64 bit build is failing when user tries to compile Python 2.7.13 using PC\VS9.0 build scripts + Visual Studio 2008.

Since all openssl source on http://svn.python.org/projects/external/ is pre-configured, don’t you guys think we should have *_amd64.h file under openssl-*/crypto directory?
History
Date User Action Args
2017-08-04 13:03:37hirenvadaliasetrecipients: + hirenvadalia, christian.heimes
2017-08-04 13:03:37hirenvadaliasetmessageid: <1501851817.64.0.525660205253.issue31120@psf.upfronthosting.co.za>
2017-08-04 13:03:37hirenvadalialinkissue31120 messages
2017-08-04 13:03:37hirenvadaliacreate