On Feb 21 13:18:47, [email protected] wrote:
> On Feb 21 12:43:28, [email protected] wrote:
> > A more general proposed solution was to bunlde a newer curl with MP,
> > in partcular one built against a newer SSL/TLS library:
> > https://trac.macports.org/ticket/51516
>
> It was also suggested there to recompile MP
> using its own already installed curl port.
>
> Indeed,
> ./configure --with-curlprefix=/opt/local/
> results in MacPorts that uses its own /opt/local/bin/curl
> to download distfiles, and my immediate problem disappears.
The problem is not curl itself of course,
but the SSL library it is linked against,
as already stated in the ticket. On my system:
$ otool -L /usr/bin/curl
/usr/bin/curl:
/usr/lib/libcurl.4.dylib (compatibility version 6.0.0, current version 6.1.0)
/usr/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
/usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version
0.9.8)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
125.2.11)
$ otool -L /opt/local/bin/curl
/opt/local/bin/curl:
/opt/local/lib/libcurl.4.dylib (compatibility version 9.0.0, current version
9.0.0)
/opt/local/lib/libssl.1.0.0.dylib (compatibility version 1.0.0, current version
1.0.0)
/opt/local/lib/libcrypto.1.0.0.dylib (compatibility version 1.0.0, current
version 1.0.0)
/opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version
1.2.11)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
125.2.11)
$ port provides /opt/local/lib/libssl.1.0.0.dylib
/opt/local/lib/libssl.1.0.0.dylib is provided by: openssl
Jan
