On May 29, 2018, at 15:58, Matt Billenstein <m...@vazor.com> wrote: > Noticed the OSX buildbot I'm running is linking to homebrew ssl 1.0.0 -- not > ideal -- the distributed python bundles openssl now does it not? > > mattb-mbp2:build buildbot$ pwd > /Users/buildbot/buildarea/3.x.billenstein-sierra/build > > mattb-mbp2:build buildbot$ otool -L > build/lib.macosx-10.13-x86_64-3.8-pydebug/_ssl.cpython-38dm-darwin.so > build/lib.macosx-10.13-x86_64-3.8-pydebug/_ssl.cpython-38dm-darwin.so: > /usr/local/opt/openssl/lib/libssl.1.0.0.dylib (compatibility version > 1.0.0, current version 1.0.0) > /usr/local/opt/openssl/lib/libcrypto.1.0.0.dylib (compatibility > version 1.0.0, current version 1.0.0) > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current > version 1252.50.4)
Matt, In the OpenSSL case, the library file name does not tell you what version of OpenSSL is actually being used. AFAIK, all recent versions use 1.0.0 in the file name I believe because they *may* be ABI compatible, not that I would bet the ranch on it. A better way to tell is to look at the output of the relatively new (and cool - thank you, Victor!) "pythoninfo" buildbot build step which runs a script that records the values of various things including the OpenSSL version that the built Python links to. For your macOS Sierra buildbots for 3.x and 3.7, I see: ssl.OPENSSL_VERSION: OpenSSL 1.0.2o 27 Mar 2018 ssl.OPENSSL_VERSION_INFO: (1, 0, 2, 15, 15) (for example, from http://buildbot.python.org/all/#/builders/14/builds/1056/steps/3/logs/stdio ) So all is cool by you :) Thanks for checking! -- Ned Deily n...@python.org -- [] _______________________________________________ Python-Buildbots mailing list Python-Buildbots@python.org https://mail.python.org/mailman/listinfo/python-buildbots
