Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 30 May 2020 09:01:47 +0000
From:      bugzilla-noreply@freebsd.org
To:        python@FreeBSD.org
Subject:   [Bug 246857] finance/electrum: Fails to run: _ssl.so: Undefined symbol "SSLv3_method@OPENSSL_1_1_0"
Message-ID:  <bug-246857-21822-O9ck9pjmTu@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-246857-21822@https.bugs.freebsd.org/bugzilla/>
References:  <bug-246857-21822@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246857

--- Comment #4 from Kubilay Kocak <koobs@FreeBSD.org> ---
Thanks you for the additional information

The system does not have a SSL library built from ports, which means SSL
functionality is provided by base, and I believe FreeBSD's base OpenSSL ver=
sion
recently changed, and has on a couple of occasions in the recent past.

When running non-RELEASE FreeBSD versions, part of the support and manageme=
nt
process is to rebuild dependent subsystems (in this case Python and/or other
SSL consuming softwares), when the underlying base system ABI changes. This
appears to be one of those cases.

Since you're also using packages, and unless you're creating or using your =
own
package sets built on or from the *same base revision* as the consuming sys=
tem
(13-CURRENT), this means that those packages will require (be built against)
the OpenSSL version that the package building servers have, which may not m=
atch
your systems.

This is very likely the cause of this issue.

Rebuilding Python and any other software that depends on OpenSSL from base,
from ports, should resolve the issue.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-246857-21822-O9ck9pjmTu>