64bit OpenSSL binaries under wrong name in system PATH

Issue #4101 resolved
Volker Birk
created an issue

TortoiseHg x64 installs SSLEAY32.DLL and LIBEAY32.DLL as 64bit DLLs, and adds the installation directory to system PATH.

As a result, other applications, which are using OpenSSL, too, and are 32bit cannot run any more because the 64bit DLLs are found first in PATH.

Either TortoiseHg x64 should rename those librarys to SSLEAY64.DLL and LIBEAY64.DLL, or it shouldn't add a system PATH to where they're stored.

Comments (5)

  1. Steve Borho

    I've yanked the subversion Python bindings and all their dependencies from the installer packages. They will be available as a second download, and won't need to be in the system PATH. They will get pulled into the PYTHONPATH as-needed, so it should be perfectly safe this way. See 426769dbcfe8

  2. Tom Benda

    Based on some tests I've been doing locally, it seems LIBEAY32.DLL and SSLEAY32.DLL are both required by PyQt4 as well - without them, thgw.exe will crash on a fresh install on a system which does not have PyQt4 installed.

  3. Log in to comment