From: Stuart Henderson Subject: Re: About net/nextcloudclient, libp11 and devel/pkgconf To: Adriano Barbosa Cc: ports Date: Tue, 24 Jun 2025 15:17:00 +0100 On 2025/06/24 09:25, Adriano Barbosa wrote: > I've been trying to fix a new issue without success. I've never used > gdb before, and from what I've learned over the past few days, the > issue seems to be an incompatibility between ssl libraries used in qt > and nextcloud, which now require openssl. Please find the backtrace from > the core dump below. I'm out of ideas on how to proceed to make it > work, and I'm wondering if there is any chance to resolve itwithout > recompiling qt stuff. Switching to OpenSSL is difficult or impossible in many cases because a lot of libraries pull in libssl/libcrypto. Generally you can't mix code compiled against OpenSSL and code compiled against LibreSSL in the same process (e.g. a library built against one used in an executable built against the other). > #0 0x00000a2a7028d02f in ossl_asn1_item_embed_free () from /usr/local/lib/eopenssl34/libcrypto.so.32.0 > #1 0x00000a2a7028cfc5 in ASN1_item_free () from /usr/local/lib/eopenssl34/libcrypto.so.32.0 > #2 0x00000a2a493c7f7a in QTlsPrivate::X509CertificateOpenSSL::convertExtension () from /usr/local/lib/qt6/plugins/tls/libqopensslbackend.so This shows QTls code (which expects libressl) calling into functions coming from openssl's libraries, that's not going to work. What's failing with libressl? Do you have a (non-working) diff?