Opened 8 years ago
Closed 5 years ago
#49644 closed defect (worksforme)
mariadb-10.0 won't build with LibreSSL
| Reported by: | willem+macports@… | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.4 |
| Keywords: | Cc: | jeremyhu (Jeremy Huddleston Sequoia) | |
| Port: | mariadb-10.0 |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Configuration stops when it doesn't detect libssl.1.0.0.dylib LibreSSL port is installed.
Library not loaded: /opt/local/lib/libssl.1.0.0.dylib /opt/local/lib/libcrypto.1.0.0.dylib
Change History (4)
comment:1 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | jeremyhu@… added |
|---|---|
| Description: | modified (diff) |
| Owner: | changed from macports-tickets@… to pixilla@… |
| Port: | mariadb-10.0-server removed |
| Summary: | MariaDB 10.0 won't build with LibreSLL → mariadb-10.0 won't build with LibreSLL |
comment:2 Changed 8 years ago by raimue (Rainer Müller)
| Summary: | mariadb-10.0 won't build with LibreSLL → mariadb-10.0 won't build with LibreSSL |
|---|
comment:3 Changed 5 years ago by mf2k (Frank Schima)
| Owner: | pixilla deleted |
|---|---|
| Status: | new → assigned |
See #57827
comment:4 Changed 5 years ago by yan12125 (Chih-Hsuan Yen)
| Resolution: | → worksforme |
|---|---|
| Status: | assigned → closed |
Configuration stops when it doesn't detect libssl.1.0.0.dylib LibreSSL port is installed.
Library not loaded: /opt/local/lib/libssl.1.0.0.dylib /opt/local/lib/libcrypto.1.0.0.dylib
libssl.1.0.0.dylib and libcrypto.1.0.0.dylib are provided by openssl. libressl provides libssl and libcrypto with different dylib versions. (e.g., libssl.46.dylib and libcrypto.44.dylib for libressl @2.8.3.) Most likely the reporter does not recompile curl, a dependency of cmake, against libressl, so that cmake fails to run in the configuration step. After recompiling curl, mariadb-10.0 +openssl builds fine with libressl @2.8.3 on my 10.14.6 machine with Command Line Tools 10.3.0.0.1.1562985497.
See also ticket:54744.
The current libressl situation in MacPorts is not correct; I recommend you do not attempt to use libressl at this time because of this type of error. We've been discussing it on the mailing list if you want to read more about it.