You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I install the neovim with the ppa stable version. And follow the README.md like the following to install the packer. When I run the PackerSync to install the packages. It will show the error LuaJIT is required for Luarocks functionality. Does anyone met the same issue and know how to deal with?
Any update/solution to this? Running into the same problem when running :PackerSync. Getting this on an ARM based oracle cloud minimal ubuntu instance.
Any update/solution to this? Running into the same problem when running :PackerSync. Getting this on an ARM based oracle cloud minimal ubuntu instance.
The neovim package on arm64 is not compiled with luajit (see the output of nvim --version | grep LuaJIT.) However, the 32-bit armhf version is. It's possible to use that version on what would otherwise be a 64-bit system. Ideally starting with a clean system, one can do sudo dpkg --add-architecture armhf && sudo apt update && sudo apt install neovim:armhf. However, your mileage may vary in a mixed-architecture system like this: for example, I haven't been able to get nvim-treesitter working appropriately with automatically downloaded/compiled parsers, as it's producing 64-bit .so's which error out with e.g. Error executing lua callback: Failed to load parser: uv_dlopen: <path-to-lua.so> wrong ELF class: ELFCLASS64.
nvim --version
: v0.7.2git --version
: 2.34.1Steps to reproduce
I install the neovim with the ppa stable version. And follow the README.md like the following to install the packer. When I run the
PackerSync
to install the packages. It will show the error LuaJIT is required for Luarocks functionality. Does anyone met the same issue and know how to deal with?git clone --depth 1 https://github.com/wbthomason/packer.nvim\ ~/.local/share/nvim/site/pack/packer/start/packer.nvim
The text was updated successfully, but these errors were encountered: