Upon updating to 2.7.0, breakages were observed in a handful but wide variety of ports. So far, they are of the variety "static declaration of 'X509_NAME_ENTRY_set' follows non-static declaration", albeit with a slew of different functions from ssl.h.
This may or may not become a meta bug at some point. The ports observed to break with my small run:
Interestingly, in terms of the python ports, lang/python34 builds fine. I haven't tried any further ports as many of those depending on USES=ssl also list at least one of the aforementioned listed ports as dependencies.
Gentoo also has this tracked as a meta bug, albeit from the start of their libressl support. Their dependent bugs relevant to this breakage start from 651162.
Thanks for reporting. I'm "commandeering" this PR a bit to keep track of other PR's that break with LibreSSL 2.7.
I'll use this PR as placeholder to check how far along we are to update the ports tree so I can update security/libressl to 2.7 branch.
This is also tracked on the FreeBSD wiki https://wiki.freebsd.org/LibreSSL/Ports#LibreSSL_2.7
I've done exp-runs on 2.6.4 and 2.7.0 to compare diffs
2.7.1 is released . Python upstream released their patches when this happened, I expect some other projects to follow.
Started a new exp-run with LibreSSL 2.7.1
Imported the patch for python27 from the correct branch in git but it fails. Removed the patch for Tools/ssl/multissltests.py for now.
multissltests.py was renamed from something else previously; the file name escapes me but groking the content you'll see the resemblence. For lang/python27 and lang/python35, I removed that part of the patch anyway.