[issue10007] Visual C++ cannot build _ssl and _hashlib if newer OpenSSL is placed in $(dist) directory (PCBuild)
Hirokazu Yamamoto
report at bugs.python.org
Fri Oct 1 16:47:11 CEST 2010
New submission from Hirokazu Yamamoto <ocean-city at m2.ccsnet.ne.jp>:
Visual C++ cannot build _ssl and _hashlib if newer OpenSSL
is placed in $(dist) directory. This happens on PCbuild.
Python3.2 uses openssl-1.0.0a
Python3.1 and 2.7 uses openssl-0.9.8l
If the directory layout is like this, Python3.1
cannot build _ssl and _hashlib.
python-dev
+- openssl-0.9.8l
+- openssl-1.0.0a
+- py3k
+- release31-maint
+- release27-maint
Because build_ssl.py in release31-maint thinks newer
is better, and select openssl-1.0.0a, but pyproject.vsprops
hard-corded $(openssldir) as openssl-0.9.8l. So Modules/ssl.c
cannot import ssl.h and so on.
----------
components: Build
messages: 117805
nosy: ocean-city
priority: normal
severity: normal
status: open
title: Visual C++ cannot build _ssl and _hashlib if newer OpenSSL is placed in $(dist) directory (PCBuild)
versions: Python 2.7, Python 3.1, Python 3.2
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10007>
_______________________________________
More information about the Python-bugs-list
mailing list