Created attachment 228392 [details] 0001-security-stunnel-fix-build-with-libressl The port currently isn't marked broken with LibreSSL, but doesn't build either. It only contains a package restriction and an IGNORE when FIPS is selected. As I've learned from previous PRs, this seems to be one of the cases where upstream is unwilling to support LibreSSL. But FreeBSD ports support it, so IMHO, there are two ways to fix this problem: Either mark the port broken with LibreSSL, or add a local patch… Either way, I'm attaching a patch that works for me (no warranties…), so anyone who is fine with an unofficial patch can apply it themselves.
Created attachment 228394 [details] 0001-security-stunnel-add-optional-patch-for-LibreSSL As a possible alternative, it might also make sense to add LibreSSL support as an extra patch, so the user has to actively choose to use an unofficial patch? Idea outlined in attached patch…
Created attachment 228395 [details] 0001-security-stunnel-add-optional-patch-for-LibreSSL fixed stupid typo…
Please submit detection/support for libressl upstream to the stunnel devs. As requested, I've marked the port broken with libressl in commit a2e23f5c2e.