[MacPorts] #56261: erlang: file not found: /opt/local/lib/libcrypto.1.0.0.dylib (was: file not found: /opt/local/lib/libcrypto.1.0.0.dylib)

MacPorts noreply at macports.org
Tue Apr 10 11:58:55 UTC 2018


#56261: erlang: file not found: /opt/local/lib/libcrypto.1.0.0.dylib
-----------------------+----------------------
  Reporter:  conradwt  |      Owner:  ci42
      Type:  defect    |     Status:  assigned
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:  2.4.2
Resolution:            |   Keywords:
      Port:  erlang    |
-----------------------+----------------------
Changes (by ryandesign):

 * cc: ci42 (removed)
 * status:  new => assigned
 * owner:  (none) => ci42


Comment:

 Looks like you have libressl installed instead of openssl. MacPorts
 currently uses openssl by default but allows libressl to be used instead.
 Most ports that use the openssl api should support either openssl or
 libressl, but sometimes there are problems. In this case, the problem
 might be that one of erlang's dependencies uses openssl, and the version
 of that dependency that you have installed was built using openssl not
 libressl, either because you received a binary from our build server, or
 because you built and installed it while openssl was installed on your
 system and you later deactivated openssl and installed libressl in its
 place. Usually the MacPorts "rev-upgrade" feature automatically detects
 any such problems and rebuilds any affected ports, but in this case the
 problem may not have been detected. So we need to figure out which of
 erlang's dependencies is the culprit and why it wasn't rebuilt.

 The log you attached does not show as much detail as I would like because
 erlang's build system uses silent rules. The erlang port should disable
 silent rules in the build system. Until the maintainer makes that change,
 you can achieve the equivalent by running:

 {{{
 sudo port clean erlang
 sudo port install erlang +hipe +ssl +wxwidgets configure.post_args
 =--disable-silent-rules
 }}}

 If you attach the new main.log after doing that, it might help us diagnose
 the problem better.

-- 
Ticket URL: <https://trac.macports.org/ticket/56261#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list