-
-
Notifications
You must be signed in to change notification settings - Fork 12.1k
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 0.7 crashes with "vim/_init_packages.lua: cannot load incompatible bytecode" #99630
Comments
This is due to Neovim linking against PUC Lua 5.4 at runtime instead of the recommended LuaJIT (as it does on macOS, so this is purely a Can you show the output of |
Odd. @madis what is the output of |
|
Can you try Also, what's the LuaJIT version here? Shouldn't Neovim link again against |
This looks like your problem:
You've modified your local Can you try installing from the bottle? |
Same result
Unfortunately I don't know how to answer that. |
I'm not sure how you deduced that I've modified my local
Ran:
|
Someone from neovim/neovim devs posted the following (maybe useful for solving this?)
|
This builds a brand-new bottle on your system, which would potentially pick up locally-installed stuff like You want to do this instead:
or better yet:
then
|
That was my conclusion based on the output of
No, I don't mean building your own bottle locally. Doing a source build on your machine seems to be what's causing your problem, so building your own bottle won't get around it (as that still involves a source build on your machine). I just meant a plain |
One other possibility is that
when it should be using
Can you try doing
? |
Yes, I think this is your problem:
Here we see that
comes before
in This needs fixing in
if you don't want to do CC @Homebrew/linux |
We've been seeing similar linkage issues in Homebrew CI for a while (particularly with May be indirectly fixed for new users (not sure about existing) if we decide to swap |
Unfortunately same result (crash due to incompatible bytecode)
Same as above (crash)
|
☝️ this (the 2 commands) made Neovim (installed via homebrew) start successfully 🥳 Also may be worth mentioning, that downloading the Neovim compiled binary (nvim-linux64.tar.gz in my case) from their Github releases page (https://github.com/neovim/neovim/releases/tag/v0.7.0) works also without issues.
|
This is because the GitHub release is a statically linked executable. It's nice to do to make something portable but generally frowned upon by package managers (primarily for security reasons). |
I have the same problem on arch linux. |
Yes, this issue affects all Linux Homebrew users who have both |
The root cause of this problem is probably the ordering of the array here: https://github.com/Homebrew/brew/blob/fa4f239cd6e7b96de54825d779ca2a8ac3ff7ec2/Library/Homebrew/extend/os/linux/extend/ENV/super.rb#L40-L46 def determine_rpath_paths(formula)
PATH.new(
*formula&.lib,
"#{HOMEBREW_PREFIX}/lib",
PATH.new(run_time_deps.map { |dep| dep.opt_lib.to_s }).existing,
)
end should probably be changed to def determine_rpath_paths(formula)
PATH.new(
*formula&.lib,
PATH.new(run_time_deps.map { |dep| dep.opt_lib.to_s }).existing,
"#{HOMEBREW_PREFIX}/lib",
)
end This would make sure that the Interestingly I wonder if after we make this change, we should start to audit for linkage through |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Just for reference, i was getting the same issue and i was using neovim on aws-arch instsance, turns out by using luajit from community/luajit solved, instead of ec2/luajit |
brew gist-logs <formula>
link ORbrew config
ANDbrew doctor
outputBrew doctor
Verification
brew update
and am still able to reproduce my issue.brew doctor
and that did not fix my problem.What were you trying to do (and why)?
Installing Neovim (both official latest and HEAD) via homebrew on Linux
What happened (include all command output)?
Installation ran normally. When starting Neovim, the following error is printed
What did you expect to happen?
Expected Neovim to start normally (without crashing).
Googled a bit and these threads / commits may be useful (although didn't help in my case)
After installing neovim from https://github.com/neovim/neovim/releases/tag/v0.7.0 nvim-linux64.tar.gz, it started normally. So maybe it's more of a homebrew (/linux) issue?
Step-by-step reproduction instructions (by running
brew
commands)brew install neovim
/home/linuxbrew/.linuxbrew/bin/nvim --clean
System:
Terminal: GNOME Terminal 3.36.2 using VTE 0.60.3 +BIDI +GNUTLS +ICU +SYSTEMD
OS: 20.04.4 LTS (Focal Fossa) x86-64
$SHELL: xterm-256color
The text was updated successfully, but these errors were encountered: