I don't happen to have OpenSSL configured on my OSX dev box right now. This usually leads to some warnings during the build stage and obviously various ssl-based tests don't work, but I can still get other stuff done. But with the latest repo, "make install" refuses to complete -- it ends fatally as follows:
if test "xupgrade" != "xno" ; then \
case upgrade in \
upgrade) ensurepip="--upgrade" ;; \
install|*) ensurepip="" ;; \
esac; \
./python.exe -E -m ensurepip \
$ensurepip --root=/ ; \
fi
Traceback (most recent call last):
File "/Users/guido/cpython/Lib/runpy.py", line 171, in _run_module_as_main
"__main__", mod_spec)
File "/Users/guido/cpython/Lib/runpy.py", line 86, in _run_code
exec(code, run_globals)
File "/Users/guido/cpython/Lib/ensurepip/__main__.py", line 4, in <module>
ensurepip._main()
File "/Users/guido/cpython/Lib/ensurepip/__init__.py", line 203, in _main
default_pip=args.default_pip,
File "/Users/guido/cpython/Lib/ensurepip/__init__.py", line 74, in bootstrap
_require_ssl_for_pip()
File "/Users/guido/cpython/Lib/ensurepip/__init__.py", line 23, in _require_ssl_for_pip
raise RuntimeError(_MISSING_SSL_MESSAGE)
RuntimeError: pip 1.5.2 requires SSL/TLS
make: *** [install] Error 1
Can this failure be suppressed in the Makefile (given that I know what I'm doing)?