port is built against system libcurl. I actually ran into that yesterday while compiling MacPorts under FreeBSD (unfortunately, the tcl build throws a core with a signal 11 when doing portindex).
Marius __ Marius Schamschula On Jun 19, 2021, 8:12 AM -0500, Christopher Jones <jon...@hep.phy.cam.ac.uk>, wrote: > > > > On 19 Jun 2021, at 1:35 pm, Joshua Root <j...@macports.org> wrote: > > > > On 2021-6-19 20:12 , Christopher Jones wrote: > > > A quick web search suggests this could be an issue with an older version > > > of (lib)curl being used ? Does anyone have any insights into this ? > > > > Certainly seems OK with the MacPorts version but not the system version. I > > don't know any specifics, but it seems like maybe the system version > > defaults to an older TLS protocol and this server doesn't allow it. > > > > % /opt/local/bin/curl -Lo test.html https://downloads.xiph.org/releases/ogg/ > > % Total % Received % Xferd Average Speed Time Time Time Current > > Dload Upload Total Spent Left Speed > > 100 161 100 161 0 0 275 0 --:--:-- --:--:-- --:--:-- 277 > > 100 12736 0 12736 0 0 9545 0 --:--:-- 0:00:01 --:--:-- 34144 > > > > % /usr/bin/curl -Lo test.html https://downloads.xiph.org/releases/ogg/ > > % Total % Received % Xferd Average Speed Time Time Time Current > > Dload Upload Total Spent Left Speed > > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 > > curl: (35) error:1400442E:SSL routines:CONNECT_CR_SRVR_HELLO:tlsv1 alert > > protocol version > > > > - Josh > > I guess base doesn’t use macports curl, even if it is installed and first in > PATH, as I do have it installed ? Or does base not invoke ‘curl’ at all but > use some library instead ?
