On 2025-07-17, izzy Meyer <izder...@disroot.org> wrote:
> --MP_/Z8KMZgel7GN.xES0_/Z.4+w
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
>
> Hello misc@,
>
> I was doing my weekly upgrade of my -current machines and ended up

I recommend deferring updates if there has just been a bump to a shared
library major version for things like libc or libpthread in base (or a
perl update, if you use perl packages) - wait for new packages built
against the new libraries first. (To check, download the tgz for
something linking against the relevant library - I often use moo
because it's small - and check the @wantlib lines in +CONTENTS).

> I am currently on:
>
> ~ $ sysctl kern.osrevision
> kern.osrevision=202504

that tells you almost nothing. 'sometime between 7.7 and 7.8'.

"sysctl kern.version" is better.

> ~ $ rlwrap sbcl
> This is SBCL 2.5.5.openbsd.sbcl-2.5.5, an implementation of ANSI Common Lisp.
> More information about SBCL is available at <http://www.sbcl.org/>.

It's not clear from this which arch you use. If it's amd64 it's likely
things will be ok when new packages are available (probably in around
2 days time). If it's i386 then the sbcl port needs fixing because it
can't be built any more. Other archs unknown.

> SBCL is free software, provided as is, with absolutely no warranty.
> It is mostly in the public domain; some portions are provided under
> BSD-style licenses.  See the CREDITS and COPYING files in the
> distribution for more information.
> * (ql:quickload :cl+ssl)
> To load "cl+ssl":
>   Load 1 ASDF system:
>     cl+ssl
> ; Loading "cl+ssl"
> ............sbcl:/usr/lib/libcrypto.so.57.0: undefined symbol '__stderr'
> sbcl:/usr/lib/libcrypto.so.57.0: undefined symbol '__stdin'
>
> debugger invoked on a CFFI:LOAD-FOREIGN-LIBRARY-ERROR in thread
> #<THREAD tid=553824 "main thread" RUNNING {11032D0003}>:
>   Unable to load foreign library (LIBCRYPTO).
>   Error opening shared object "libcrypto.so":
>   Cannot load specified object.

If you can persuade it to use libcrypto.so.56.0 rather than allowing
it to search for the latest version, that would probably work too.
Maybe running it with LD_PRELOAD=/usr/lib/libcrypto.so.56.0 would do
the trick. (Obviously just temporary until new packages are up).



-- 
Please keep replies on the mailing list.

Reply via email to