[MacPorts] #63255: neovim @0.5.0: Build failure (PANIC: unprotected error in call to Lua API)
MacPorts
noreply at macports.org
Sat Oct 23 19:33:51 UTC 2021
#63255: neovim @0.5.0: Build failure (PANIC: unprotected error in call to Lua API)
---------------------------+----------------------
Reporter: brianclemens | Owner: raimue
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.7.1
Resolution: | Keywords:
Port: neovim |
---------------------------+----------------------
Comment (by flwyd):
Possibly related, I get a segfault whenever I run macports-installed
neovim on macOS Mojave 10.14.6 (Intel chipset) with a stack trace
implicating luajit:
{{{
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libluajit-5.1.2.dylib 0x000000010a8acef4 lj_tab_get + 40
1 libluv.1.dylib 0x000000010a7f196f luv_set_loop +
18
2 nvim 0x000000010a4a6cf6
nlua_enter.llvm.6450955445491329638 + 756
3 nvim 0x000000010a4a772e nlua_exec + 48
4 nvim 0x000000010a5ae3db
list_lua_version + 108
5 nvim 0x000000010a5add4d list_version +
51
6 nvim 0x000000010a4afff0 version + 38
7 nvim 0x000000010a4af2ef main + 11090
8 libdyld.dylib 0x00007fff5f3fa3d5 start + 1
}}}
Running `nvim` brings up the basic vim UI, but doing almost anything, like
moving one character or even running `nvim --version` will generate a
segmentation fault.
I tried deactivating `luv-luajit` and installing `luajit-openresty` as
mentioned by Brian, but `port install neovim` still seems to require `luv-
luajit`.
What would be required to fix `luv-luajit`? Alternatively, could the
Portfile switch to `luajit-openresty` if fixing luv isn't faesible?
--
Ticket URL: <https://trac.macports.org/ticket/63255#comment:6>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list