Python3.7 installation-Pip3 shows ssl problems-openssl does not install
python3.7 and 2.7 coexistence environment
everything is fine after installation, but pip3 starts to show tcl/ssl problems when it is in use, and cannot get the files in the source.
on the network, it is indicated that openssl related files are not installed. After yum installation, take the parameter. / configure-- with-ssl reinstalls python
but I never succeeded, OPENSSL and other related files installed dozens, hundreds of times, useless.
after that, it is said that HOST is not secure, and it is not possible to modify the source address.
here comes the problem. I found that there are differences after Yum installs OPENSSL and other related files
< hr >
the following is the post-installation results displayed on the network, all of which are two files!
< hr >
View installation results
[root@localhost ~]-sharp rpm -aq|grep openssl
openssl-0.9.8e-26.el5_9.1
openssl-0.9.8e-26.el5_9.1
openssl-devel-0.9.8e-26.el5_9.1
openssl-devel-0.9.8e-26.el5_9.1
< hr >
mine is all single!
< hr >
Why is mine a single file? Other people are in pairs?
does a single file cause SSL problems?
how to solve this SSL problem?
Thank you all!
< hr >
http://blog.51cto.com/1354442.
refer to this. Recently, server python2.6 upgrade 3.7 also encountered this problem
Thank you very much for sharing, which I haven't worked out all day. Follow you. Pip3 finally works. Openssl 1.1.0j python3.65
< H2 >
next is the resolution process < / H2 >
< hr >
I decided to do two versions of the stand-alone environment mode and take a look at it again. Previously, a python3 error would have been reported if the environment had been created separately.
now that make is released, the prompt is as follows
Python build finished filling!
The necessary bits to build these optional modules were not found:
_ ssl _ uuid
To find the necessary bits, look in setup.py in detect_modules () for the module's name. Could not build the ssl module! Python requires an OpenSSL 1.0.2 or
1.1 compatible libssl with X509_VERIFY_PARAM_set1_host (). LibreSSL 2.6.4 and earlier do not provide the necessary APIs, https://github.com/libressl-p.
< hr >
! Found out why! The openssl version of YUM image is too old! It's 1.0.1, version 1.02!
< hr >
so go to the openssl site to download and install manually,
but after installing openssl, the new version, is still not recognized, so ln-s modifies the connection,
but the internal designation will still be different, and the ssl module will not be installed
.
[root@i-ABC Python-3.7.0]-sharp rpm -aq|grep openssl
openssl-1.0.1e-57.el6.x86_64
openssl-devel-1.0.1e-57.el6.x86_64
openssl-static-1.0.1e-57.el6.x86_64
[root@i-ABC Python-3.7.0]-sharp openssl version
OpenSSL 1.0.2o 27 Mar 201
< hr >
in despair, I searched everywhere and found that this article was good. It was also a problem with installing SSL in python3.7, and finally I used libressl instead of openssl to fix it. This seems to be the right way, but it still hasn't solved my side of the environment.
http://ju.outofmemory.cn/entr.
I guess there are two possible sources of problems. One is that the pagoda panel was installed before, and there is an openssl conflict.
the second possibility may be that Centos6.8 is not a good choice for installing python3.7.
but uninstalling the panel is also troublesome. You don't know how many holes are waiting for you to install pearl,.
< hr >
I checked the make test, of openssl and found that I didn't install it in the first place. I don't know what it means
SSL_accept() failed -1, 1
140053220050600:error:140800FF:SSL routines:ssl3_accept:unknown state:s3_srvr.c:869:
< hr >
< H2 >
short teeth, guys, I got it all of a sudden. < / H2 >
I did three things:
1. Install all openssl1.0.2 / libressl / python3.7 in the / usr/ directory
2. The shared zlib parameter is added when compiling and installing openssl (the ssl parameter cannot be added for unknown reasons)
cd openssl-1.0.2o
./config --prefix=/usr --openssldir=/usr/openssl shared zlib
3. Then test it when make compiles, and it is said that it can also make depend to prevent compilation from failing, but I didn't use it.
make
make test
make install
then go all the way-- with-ssl install python3.7,
then pip3 install-- upgrade install pip upgrade the latest version pip
finally test pip3 install mkl-succeeded.
it is possible that the parameter is a treasure. Modify the soft link and so on, the hidden danger is too big, easily recommend an openssl installation parameter library instructions.
http://www.jinbuguo.com/linux.
as to why rpm's qa query is different from openssl's version query in the end, please let me know!
maybe you will encounter problems after configuring the python environment independently. Remember to execute / sbin/ldconfig after establishing the soft link and upgrade the dynamic library.
< hr >
< hr >
reference answers are as follows: thank you!
https://blog.csdn.net/mingtian625/article/details/52368677
https://zhidao.baidu.com/question/566026641912735684.html
https://blog.csdn.net/shanliangliuxing/article/details/18499625
https://blog.csdn.net/jeryjeryjery/article/details/77880227
https://www.cnblogs.com/cnlihao/p/7069776.html
https://blog.csdn.net/zx_whu/article/details/71773923
https://www.cnblogs.com/wenchengxiaopenyou/p/5709218.html
https://blog.csdn.net/qq_36416904/article/details/79316972
https://www.cnblogs.com/freeweb/p/5181764.html
http://www.cnblogs.com/devilmaycry812839668/p/9274547.html
< hr >
< H2 > finally post the goal of this article: the environment required to install each version of tensorflow. Yes,
python3.7+centos6.8 is not a particularly good choice at the moment. < / H2 >
TensorFlow 1.10 has been released, and officials have not yet specified which environments it is suitable for.
friends who are as excited as me to install python3.7, and struggle with a series of questions and finally find out that they don't have the support of the tensorflow version can wait and see.
LINUX
windows
friends of Mac, please check the official website by yourself
