[MacPorts] #45114: Erlang can't load crypto library
#45114: Erlang can't load crypto library ----------------------+------------------------------------- Reporter: dedalo@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.3.1 Keywords: | Port: erlang @17.3_0+hipe+ssl ----------------------+------------------------------------- There is a problem with the openssl library. When I try to load the crypto library, which depends on ssl, an exception is triggered. I'm on Mac OS X 10.7.5. erl Erlang/OTP 17 [erts-6.2] [source] [64-bit] [smp:4:4] [async-threads:10] [hipe] [kernel-poll:false] Eshell V6.2 (abort with ^G) 1> crypto:start(). ** exception error: undefined function crypto:start/0 2> =ERROR REPORT==== 21-Sep-2014::17:55:32 === Unable to load crypto library. Failed with error: "load, Library load-call unsuccessful." OpenSSL might not be installed on this system. =ERROR REPORT==== 21-Sep-2014::17:55:32 === The on_load function for module crypto returned {error, {load, "Library load-call unsuccessful."}} port installed erlang The following ports are currently installed: erlang @17.1_0+hipe+ssl erlang @17.3_0+hipe+ssl (active) -- Ticket URL: <https://trac.macports.org/ticket/45114> MacPorts <http://www.macports.org/> Ports system for OS X
#45114: erlang @17.3_0+hipe+ssl: can't load crypto library -----------------------+------------------------- Reporter: dedalo@… | Owner: ciserlohn@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: erlang | -----------------------+------------------------- Changes (by larryv@…): * owner: macports-tickets@… => ciserlohn@… * priority: High => Normal * port: erlang @17.3_0+hipe+ssl => erlang Old description:
There is a problem with the openssl library. When I try to load the crypto library, which depends on ssl, an exception is triggered. I'm on Mac OS X 10.7.5.
erl Erlang/OTP 17 [erts-6.2] [source] [64-bit] [smp:4:4] [async-threads:10] [hipe] [kernel-poll:false]
Eshell V6.2 (abort with ^G) 1> crypto:start(). ** exception error: undefined function crypto:start/0 2> =ERROR REPORT==== 21-Sep-2014::17:55:32 === Unable to load crypto library. Failed with error: "load, Library load-call unsuccessful." OpenSSL might not be installed on this system.
=ERROR REPORT==== 21-Sep-2014::17:55:32 === The on_load function for module crypto returned {error, {load, "Library load-call unsuccessful."}}
port installed erlang The following ports are currently installed: erlang @17.1_0+hipe+ssl erlang @17.3_0+hipe+ssl (active)
New description: There is a problem with the openssl library. When I try to load the crypto library, which depends on ssl, an exception is triggered. I'm on Mac OS X 10.7.5. {{{ erl Erlang/OTP 17 [erts-6.2] [source] [64-bit] [smp:4:4] [async-threads:10] [hipe] [kernel-poll:false] Eshell V6.2 (abort with ^G) 1> crypto:start(). ** exception error: undefined function crypto:start/0 2> =ERROR REPORT==== 21-Sep-2014::17:55:32 === Unable to load crypto library. Failed with error: "load, Library load-call unsuccessful." OpenSSL might not be installed on this system. =ERROR REPORT==== 21-Sep-2014::17:55:32 === The on_load function for module crypto returned {error, {load, "Library load-call unsuccessful."}} port installed erlang The following ports are currently installed: erlang @17.1_0+hipe+ssl erlang @17.3_0+hipe+ssl (active) }}} -- Comment: Thanks for the report. In the future, please Cc relevant port maintainers (`port info --maintainers erlang`) and avoid setting the Priority field (it’s reserved for MacPorts developers). -- Ticket URL: <https://trac.macports.org/ticket/45114#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#45114: erlang @17.3_0+hipe+ssl: can't load crypto library -----------------------+------------------------- Reporter: dedalo@… | Owner: ciserlohn@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: erlang | -----------------------+------------------------- Comment (by ciserlohn@…): It works on my machine (OS X 10.9.5): {{{ bash-4.3$ erl Erlang/OTP 17 [erts-6.2] [source] [64-bit] [smp:8:8] [async-threads:10] [hipe] [kernel-poll:false] Eshell V6.2 (abort with ^G) 1> crypto:start(). ok 2> }}} It looks like the bug described [http://erlang.org/pipermail/erlang- bugs/2013-December/003929.html here] although the fix mentioned there is contained in erlang 17.3. Could you check if the any of the described workarounds works for you?
If I did any of: calling crypto:start() a second time, or waiting a few seconds before calling it, or evaluating another shell command before crypto:start() , it would work just fine.
And please provide the output of: {{{ otool -L /opt/local/lib/erlang/lib/crypto-3.4.1/priv/lib/crypto.so }}} -- Ticket URL: <https://trac.macports.org/ticket/45114#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#45114: erlang @17.3_0+hipe+ssl: can't load crypto library -----------------------+------------------------- Reporter: dedalo@… | Owner: ciserlohn@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: erlang | -----------------------+------------------------- Comment (by dedalo@…): {{{ otool -L /opt/local/lib/erlang/lib/crypto-3.4.1/priv/lib/crypto.so /opt/local/lib/erlang/lib/crypto-3.4.1/priv/lib/crypto.so: /opt/local/lib/libcrypto.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0) }}} {{{ port installed openssl The following ports are currently installed: openssl @1.0.1i_0 (active) }}} -- Ticket URL: <https://trac.macports.org/ticket/45114#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#45114: erlang @17.3_0+hipe+ssl: can't load crypto library -----------------------+------------------------- Reporter: dedalo@… | Owner: ciserlohn@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: erlang | -----------------------+------------------------- Comment (by ciserlohn@…): Replying to [comment:3 dedalo@…]:
{{{ otool -L /opt/local/lib/erlang/lib/crypto-3.4.1/priv/lib/crypto.so
/opt/local/lib/erlang/lib/crypto-3.4.1/priv/lib/crypto.so: /opt/local/lib/libcrypto.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0) }}}
{{{ port installed openssl
The following ports are currently installed: openssl @1.0.1i_0 (active) }}}
Ok, there is nothing suspicious. Could you please try the workarounds mentioned upstream:
If I did any of: calling crypto:start() a second time, or waiting a few seconds before calling it, or evaluating another shell command before crypto:start() , it would work just fine.
and report the results. -- Ticket URL: <https://trac.macports.org/ticket/45114#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#45114: erlang @17.3_0+hipe+ssl: can't load crypto library -----------------------+------------------------- Reporter: dedalo@… | Owner: ciserlohn@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: erlang | -----------------------+------------------------- Comment (by dedalo@…): I have tried it, I have just forgot to mention it. It didn't work, I got the same error twice. :-( -- Ticket URL: <https://trac.macports.org/ticket/45114#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
#45114: erlang @17.3_0+hipe+ssl: can't load crypto library -----------------------+------------------------- Reporter: dedalo@… | Owner: ciserlohn@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: erlang | -----------------------+------------------------- Comment (by dedalo@…): Just a fast update. I have restarted the system and CouchDB (it's built on Erlang) didn't start. The log shows the same error above. So I have reverted to 17.1 version and it works. If there is something I can do to help further let me know. Anyway the bug exists and it's just related to 17.3. The 17.1 release instead works fine. You might check the difference between 17.1 and 17.3 to figure out the problem. -- Ticket URL: <https://trac.macports.org/ticket/45114#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts