From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Racket: SSL not available; can't install/update packages
Date: Tue, 20 Oct 2020 06:30:04 +0200 [thread overview]
Message-ID: <20201020043004.ftvxjcMYdoLJ39ntl2MFXQgrgtirKjibpdEbOHLrvCw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25748@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2839 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/25748#issuecomment-712581146
Comment:
From `collects/openssl/libcrypto.rkt`:
```
#lang racket/base
(require ffi/unsafe
racket/runtime-path
setup/cross-system
(for-syntax racket/base
setup/cross-system))
(provide libcrypto
libcrypto-load-fail-reason
openssl-lib-versions)
;; Notes on shared library versions when provided by OS
;; ie, VERSION s.t. OS provides "lib{crypto,ssl}.{so,dylib}.$VERSION"
;;
;; As of 1.0.0, OpenSSL has adopted a friendlier version policy (see
;; https://www.openssl.org/policies/releasestrat.html), and recent
;; Linux distros (eg Fedora 27, Debian 9.3 ("stretch")) seem to be
;; using (more) compatible .so versions.
;;
;; Notes on older versions:
;; - Debian and Ubuntu use a few fixed library versions even though
;; actual OpenSSL version changes:
;; - Debian squeeze: lib{crypto,ssl}.so.0.9.8
;; - Debian {wheezy, jessie, stretch, sid}: lib{crypto,ssl}.so.1.0.0
;; - Ubuntu {14.04, 14.10, 15.04}: lib{crypto,ssl}.so.1.0.0
;; - Debian and Ubuntu also provide versionless library in pkg "libssl-dev"
;; - Fedora provides libraries suffixed with actual versions (eg
;; 1.0.1k) as well as a simply-versioned symlink (eg libssl.so.10):
;; - Fedora {19, 20}: lib{crypto,ssl}.so.1.0.1e, also lib{crypto,ssl}.so.10
;; - Fedora 21: lib{crypto,ssl}.so.1.0.1j, also lib{crypto,ssl}.so.10
;; - Fedora 22: lib{crypto,ssl}.so.1.0.1k, also lib{crypto,ssl}.so.10
;; - Fedora also provides a versionless library in pkg "openssl-devel"
;; - Mac OS includes 0.9.8, 0.9.7, and versionless, but as of 10.15 the
;; versionless dylib and will abort with the following error:
;; "Invalid dylib load. Clients should not load the unversioned libcrypto
;; dylib as it does not have a stable ABI."
(define openssl-lib-versions
(let
([versions
'("1.1"
"1.0.2"
;; Compatibility-based version / SONAME
"10" ;; Fedora
"1.0.0" ;; Debian, Ubuntu
;; Other specific known versions
"1.0.1k" "1.0.1j" "1.0.1g" "1.0.1e"
"1.0" "1.0.0" "1.0.0e" "1.0.0d" "1.0.0c" "1.0.0b" "1.0.0a"
"0.9.8e" "0.9.8b" "0.9.8" "0.9.7"
;; Known versions for *BSD variants
"111")])
;; Don't use the versionless dylib on macOS, as it aborts on 10.15
(case (system-type)
[(macosx) versions]
[else
(case (path->string (system-library-subpath #f))
[("x86_64-darwin" "i386-darwin") versions]
[else
(cons "" ; versionless (eg from devel pkg)
versions)])])))
```
Might just be a matter of patching this into a semblance of reasonability.
next prev parent reply other threads:[~2020-10-20 4:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 3:22 [ISSUE] " zsisco
2020-10-20 3:47 ` ericonr
2020-10-20 3:54 ` ericonr
2020-10-20 3:57 ` zsisco
2020-10-20 3:59 ` zsisco
2020-10-20 3:59 ` [ISSUE] [CLOSED] " zsisco
2020-10-20 4:08 ` ericonr
2020-10-20 4:30 ` ericonr [this message]
2021-10-29 13:34 ` [ISSUE] [CLOSED] " leahneukirchen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201020043004.ftvxjcMYdoLJ39ntl2MFXQgrgtirKjibpdEbOHLrvCw@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).