Open wolfgang371 opened 3 years ago
Sorry for the issue. In the meantime I rolled back the stable version to 1.2.1 until it's fixed. In the future we need to test better the result and/or give more time before promoting a release to stable.
Looks like in snap it's linking against a really old version of OpenSSL (< 1.1.0
). Ubuntu 18.04 provides OpensSSL 1.1.1, so question would be where that old one is coming from.
libssl
version checks in the program code and relies on the LibSSL
bindings being correct for any version. Apparently, bindings for some BIO_*
functions are defined even when linking against OpenSSL versions that don't have them.I doubt that's worth fixing, though. The OpenSSL 1.0 has been out of upstream support for 2 years now, and even distribution packagers' maintenance is falling out. I'm not aware of any major distribution system keeping 1.0 releases actively maintained. So we do not need to support OpenSSL < 1.1.0 and should probably just drop it entirely.
It's still unclear why crystal in the snap package would end up linking against an old OpenSSL version. It might actually be a local configuration issue. Can somebody confirm this issue with the snap install?
Yesterday I got the automatic update to 1.2.2. Before that compiling worked just fine, with the update I get this:
Reinstalling didn't help.
Also on crystal snap the old versions are not available, so I couldn't rollback.
I then installed crystal via
apt
(https://crystal-lang.org/install/on_ubuntu/ and https://software.opensuse.org/download.html?project=devel%3Alanguages%3Acrystal&package=crystal) and now it's working again for me.I use Ubuntu 18.04.
As an aside, both versions still use the old LLVM 10.0.0 (see #11342).