➜

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.

classification
Title: Name of 64-bit OpenSSL v1.1.1 DLLs
Type: Stage: resolved
Components: Installation, SSL, Windows Versions: Python 3.8, Python 3.7
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: christian.heimes Nosy List: christian.heimes, paul.moore, philthompson10, steve.dower, tim.golden, zach.ware
Priority: normal Keywords:

Created on 2019-06-20 21:57 by philthompson10, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Messages (4)
msg346172 - (view) Author: Phil Thompson (philthompson10) Date: 2019-06-20 21:57 
In the 3.8b1 64-bit Windows installer the names of the OpenSSL DLLs do not have the -x64 suffix which seems to be the convention (and is the default when building OpenSSL from source). The convention is followed in the 3.7.0 to 3.7.3 installers. I haven't yet checked the 3.7.4rc1 installer.
msg346174 - (view) Author: Steve Dower (steve.dower) * (Python committer) Date: 2019-06-20 23:15 
Yes, I noticed that they changed with OpenSSL 1.1.1a, but as far as I can tell we didn't do anything to cause that - our build definition is still the same, and uses "perl Configure VC-WIN64A-masm && nmake".

Is this causing issues? Or is it just something that you noticed?
msg346195 - (view) Author: Phil Thompson (philthompson10) Date: 2019-06-21 09:08 
I think I was incorrect in saying the suffix was the default when building v1.1.1 from source, so any problem I have (trying to share the DLL with different pre-built packages) is not a Python problem. Sorry for the noise.
msg346199 - (view) Author: Phil Thompson (philthompson10) Date: 2019-06-21 09:41 
A clarification...

It seems the suffix is added when configured as VC-WIN64A but omitted when configured as VC-WIN64A-masm.

...still not a Python problem.
History
Date User Action Args
2022-04-11 14:59:17adminsetgithub: 81537
2019-06-21 09:41:01philthompson10setmessages: + msg346199
2019-06-21 09:08:34philthompson10setstatus: open -> closed
resolution: not a bug
messages: + msg346195

stage: resolved
2019-06-20 23:15:40steve.dowersetmessages: + msg346174
2019-06-20 21:57:58philthompson10create