Re: After update, vim reports undefined symbols in libruby32.so

2023-06-18 Thread Why 42? The lists account.
On Tue, Jun 13, 2023 at 09:37:32AM +0200, Theo Buehler wrote: > ... > That's because libruby32 did not link explicitly against libc++abi, which > is now needed on aarch64 and amd64 for the Rust-based YJIT compiler. > > Fixed in this commit: >

Re: After update, vim reports undefined symbols in libruby32.so

2023-06-13 Thread Theo Buehler
On Sun, Jun 11, 2023 at 07:22:28PM +0200, Why 42? The lists account. wrote: > vim:/usr/local/lib/libruby32.so: undefined symbol '_Unwind_Backtrace' > vim:/usr/local/lib/libruby32.so: undefined symbol '_Unwind_GetIP' > vim:/usr/local/lib/libruby32.so: undefined symbol '_Unwind_GetCFA' ... That's

After update, vim reports undefined symbols in libruby32.so

2023-06-11 Thread Why 42? The lists account.
Hi All, FYI, After running "sysupgrade -s" + "pkg_add -u" earlier today, I now see these messages when I exit vim: mjoelnir:awk 11.06 18:42:45 % vi substrtest.awk ... vim:/usr/local/lib/libruby32.so: undefined symbol '_Unwind_Backtrace' vim:/usr/local/lib/libruby32.so: undefined symbol