Open ScottNortonPhD opened 4 years ago
It's not hard coded to use 1.0, but it is linking the shared object to 1.0, which is then not found at runtime. You might look around for a stray libssl 1.0, such as in /usr/local/lib
.
Has any work been done relating to this issue? The problem seems to rise from the configure script. There is a workaround but it really shouldn't be necessary.
First, install openssl@1.0 via Homebrew. Next, unlink the existing openssl. Manually create a symlink from /usr/local/opt/openssl@1.0 to /usr/local/opt/openssl. Configuration should proceed as normal.
Frustratingly, if the user specifies their own PKG_CONFIG_PATH in configure.vars, the configure script flat out ignores it on mac. It also appears to ignore the manual override of OPENSSL_LIBS and OPENSSL_CFLAGS, though I cannot parse why that happens from this portion of the script.
Mac Homebrew has deprecated openssl 1.0.0 in favor of 1.1.0. This means that the older version of the library is substantially harder to acquire. Unfortunately, rtracklayer seems to have hardcoded the openssl-1.0.0 version dependency, so replacing it with 1.1.0 (which is required by other Homebrew packages) causes rtracklayer to break when trying to load. Everything that depends on rtracklayer breaks as well. The installation process uses the correct paths, but attempting to load rtracklayer at any point fails because somehow, somewhere, the path
/usr/local/opt/openssl/libssl.1.0.0.dylib
path is hardcoded.As a workaround, repointing /usr/local/opt/openssl to the 1.0.2t directory in my Cellar allows me to install and run rtracklayer.
See messages below.