Bug 255605 - net/qt5-network 5.15.2 fails to build with libressl 3.3.3
Summary: net/qt5-network 5.15.2 fails to build with libressl 3.3.3
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-kde (group)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-05 04:03 UTC by tjlegg
Modified: 2021-09-20 17:14 UTC (History)
2 users (show)

See Also:
tcberner: maintainer-feedback+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description tjlegg 2021-05-05 04:03:36 UTC 
Error Messages:
In file included from ssl/qsslcertificate.cpp:134:
ssl/qsslsocket_openssl_symbols_p.h:365:29: error: unknown type name 'BIO_ADDR'
int q_DTLSv1_listen(SSL *s, BIO_ADDR *client);
                            ^
ssl/qsslsocket_openssl_symbols_p.h:366:1: error: unknown type name 'BIO_ADDR'
BIO_ADDR *q_BIO_ADDR_new();
^
ssl/qsslsocket_openssl_symbols_p.h:367:22: error: unknown type name 'BIO_ADDR'
void q_BIO_ADDR_free(BIO_ADDR *ap);
                     ^
3 errors generated.
*** Error code 1

This is due to the DTLS code in libressl 3.3.3 that has just landed but isn't completely aligned with OpenSSL 1.1

from 13 stable /usr/include/openssl/
/usr/include/openssl/ssl.h:int DTLSv1_listen(SSL *s, BIO_ADDR *client);

from libressl 3.3.3
/usr/local/include/openssl/ssl.h:#define DTLSv1_listen(ssl, peer)

Previously I created a set of local patches that mostly ripped the DTLS out of qt5-network to get it to compile, but am now looking for guidance for how to make openssl's BIO_ADDR and libressl's peer align.
Comment 1 Tobias C. Berner freebsd_committer freebsd_triage 2021-05-05 16:04:57 UTC 
Moin moin 

Please update you ports tree to include
https://cgit.freebsd.org/ports/commit/?id=49012339a1f2e6bf7a64fffa6847be6e2d4d998b

mfg Tobias
Comment 2 Adriaan de Groot freebsd_committer freebsd_triage 2021-09-20 17:14:49 UTC 
Closed presumed fixed based on tcberner@'s comment about the port-update committed in may.