Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid DLL file names on Windows OpenSSL 1.1.0 / 1.1.1 #302

Open
quetzalcoatl opened this issue Mar 1, 2020 · 0 comments
Open

Invalid DLL file names on Windows OpenSSL 1.1.0 / 1.1.1 #302

quetzalcoatl opened this issue Mar 1, 2020 · 0 comments

Comments

@quetzalcoatl
Copy link

Commit f9b817c handled only non-Windows part.

Currently, on Windows with newest OpenSSL, I get:

c:/rubies/Ruby26-x64/lib/ruby/gems/2.6.0/gems/ffi-1.12.2-x64-mingw32/lib/ffi/library.rb:145:in `block in ffi_lib': Could not open library 'libeay32'

Since 1.1.0 (see i.e. https://mta.openssl.org/pipermail/openssl-dev/2016-August/008351.html or issues in other projects like arvidn/libtorrent#1931) libeay32 and sseay32 doesn't exist - it seems that OpenSSL team apparently decided to rename them to libcrypto and libssl.

I'm not sure if that are the correct names though.
When I tried altering the openssl.rb to:

ffi_lib 'libcrypto', 'libssl'

then I get similar:

c:/rubies/Ruby26-x64/lib/ruby/gems/2.6.0/gems/ffi-1.12.2-x64-mingw32/lib/ffi/library.rb:145:in `block in ffi_lib': Could not open library 'libssl'

I can get it running only after changing that line to:

ffi_lib 'libcrypto-1_1-x64', 'libssl-1_1-x64'

I peeked those filenames in Ruby\bin\ruby_builtin_dlls
Unfortunatelly I can't help any further, I don't know why those suffixes were added and what logic controls them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant