New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
neovim: switch back to LuaJIT #11168
Conversation
Notifying maintainers: |
Neovim 0.5 will only build with Lua 5.1 or LuaJIT
port:lua-mpack \ | ||
port:lua-luabitop \ | ||
port:luv | ||
port:msgpack \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also taking the chance to upgrade msgpack. Few ports in the tree are using msgpack1
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also taking the chance to upgrade msgpack. Few ports in the tree are using
msgpack1
.
Since msgpack and msgpack1 conflict, it would have been nice to use the "deactivate hack" or something to prevent upgrade from failing over the conflict
Maintainer timeout. Merging. |
Hi @l2dy. Thanks for the contribution 🌟. Lua is used at runtime. I'm afraid this update broke something... And now Neovim crashes. Could you take a look at my ticket? |
@judaew Thanks for the report. Try to update Let's move further discussion to the ticket. |
Description
Upstream officially supports Lua 5.1 or LuaJIT only, and Neovim 0.5 will only build with either of them, see neovim/neovim#12415.
Note:
luv
andluv-luajit
confict with each other, so upgrading requires manual intervention (deactivation).P.S. Last switch to Lua 5.3 was made because we did not have ports for the
lua51-*
dependencies. It builds, but was not thoroughly tested in regard to Lua functionalities.Type(s)
Tested on
macOS 10.15.7 19H1030 x86_64
Xcode 12.3 12C33
Verification
Have you
port lint
?sudo port -vst install
?