4 ms·

I think this means you don't have a dependency that Neovim needed to build. Make sure you ran the apt-get commands in the README.

by gw 12y ago

fit2rule 12y ago
I did indeed follow the README to a tee .. and on OSX .. so I'm still at a loss as to what may be wrong.
- gw 12y ago
  The specific build errors won't show because Cargo hides the output. Try cloning https://github.com/oakes/neovim https://github.com/oakes/neovim and running `make libnvim` inside it. The errors you get should make it more clear what dependency is missing.
  - fit2rule 12y ago
    Thanks for the tip .. looks like I've got something not quite right with my busted install, posting the details here in case any other HN users run up against it: Scanning dependencies of target stable-busted-deps [ 93%] Generating usr/lib/luarocks/rocks/stable-busted-deps PANIC: unprotected error in call to Lua API (.../rust/neovim/.deps/usr/share/lua/5.1/luarocks/fs/lua.lua:3 68: cannot open /Users/fit2rule/.cache/luarocks/https___rocks.moonscript.org/manifest-5.1: No such file or directory) make[3]: *** [usr/lib/luarocks/rocks/stable-busted-deps] Error .. seems like a conflict resulting from having lua5.2 installed alongside lua5.1 .. if I figure it out, I'll update. Update: for reasons I don't understand, the manifest-5.1 file is .zip'ed up .. so: $ cd /Users/fit2rule/.cache/luarocks/https___rocks.moonscript.org/ $ unzip manifest-5.1.zip .. fixed the issue, and now libnvim can be built properly. Seems like there are issues with having lua5.2 and lua5.1 side by side as maintained by homebrew on OSX .. so if others run into this issue, there's the facts. Update2: SolidOak still refuses to build, this time getting further but still reporting build failure: Compiling glib-sys v0.1.0 (https://github.com/oakes/rgtk#01b611cf) Build failed, waiting for other jobs to finish... EDIT: Never mind, I neglected to set PKG_CONFIG_PATH again in a new shell session, as per the README .. I'm now running SolidOak just fine and proceeding to use it to learn me some rust ... So .. leaving all the above for historical purposes ..

I think this means you don't have a dependency that Neovim needed to build. Make sure you ran the apt-get commands in the README.

by gw 12y ago

I think this means you don't have a dependency that Neovim needed to build. Make sure you ran the apt-get commands in the README.

fit2rule 12y ago

I did indeed follow the README to a tee .. and on OSX .. so I'm still at a loss as to what may be wrong.

gw 12y ago
The specific build errors won't show because Cargo hides the output. Try cloning https://github.com/oakes/neovim https://github.com/oakes/neovim and running `make libnvim` inside it. The errors you get should make it more clear what dependency is missing.
- fit2rule 12y ago
  Thanks for the tip .. looks like I've got something not quite right with my busted install, posting the details here in case any other HN users run up against it: Scanning dependencies of target stable-busted-deps [ 93%] Generating usr/lib/luarocks/rocks/stable-busted-deps PANIC: unprotected error in call to Lua API (.../rust/neovim/.deps/usr/share/lua/5.1/luarocks/fs/lua.lua:3 68: cannot open /Users/fit2rule/.cache/luarocks/https___rocks.moonscript.org/manifest-5.1: No such file or directory) make[3]: *** [usr/lib/luarocks/rocks/stable-busted-deps] Error .. seems like a conflict resulting from having lua5.2 installed alongside lua5.1 .. if I figure it out, I'll update. Update: for reasons I don't understand, the manifest-5.1 file is .zip'ed up .. so: $ cd /Users/fit2rule/.cache/luarocks/https___rocks.moonscript.org/ $ unzip manifest-5.1.zip .. fixed the issue, and now libnvim can be built properly. Seems like there are issues with having lua5.2 and lua5.1 side by side as maintained by homebrew on OSX .. so if others run into this issue, there's the facts. Update2: SolidOak still refuses to build, this time getting further but still reporting build failure: Compiling glib-sys v0.1.0 (https://github.com/oakes/rgtk#01b611cf) Build failed, waiting for other jobs to finish... EDIT: Never mind, I neglected to set PKG_CONFIG_PATH again in a new shell session, as per the README .. I'm now running SolidOak just fine and proceeding to use it to learn me some rust ... So .. leaving all the above for historical purposes ..