Patch: https://github.com/freebsd/freebsd-ports-gnome/pull/18 This port dynamically links with ssl, so add USES=ssl to account for any SONAME changes or whatnot. The omission leads to downstream build failures in certain situations; more on the gnome-development github PR.
Do you know where LibreSSL dependency pulled in? It sounds like an over linking issue to me because I cannot find any use of OpenSSL or LibreSSL in the source code of libsoup.
It's not LibreSSL specifically; it's any OpenSSL-like implementation, so the linkage happens no matter what. The issue exposes itself when the (primarily ports) SONAME changes. I counted six instances of -lcrypto in my build logs.
(In reply to Charlie Li from comment #2) I know why libsoup links to libcrypto now: It is krb5 in base that pulls it in: $ /usr/bin/krb5-config --libs -L/usr/lib -lkrb5 -lhx509 -lcom_err -lcrypto -lasn1 -lwind -lheimbase -lroken -lcrypt -pthread I configure libsoup to use MIT krb5 from ports so I didn't see it on my system. It seems to me that the same thing should be done on all ports depending on krb5. Adding USES=ssl on a port which doesn't use OpenSSL directly doesn't look like a nice solution to me.
Committed with the rest of the GNOME 3.28 update.