@eclairevoyant Can you add lua51-lpeg as a normal dependency instead of a make dependency? Neovim needs it as a shared library in runtime.
Search Criteria
Package Details: neovim-git 0.9.0.r432.g9f9cef1b56-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/neovim-git.git (read-only, click to copy) |
---|---|
Package Base: | neovim-git |
Description: | Fork of Vim aiming to improve user experience, plugins, and GUIs. |
Upstream URL: | https://neovim.io |
Keywords: | editor |
Licenses: | custom:neovim |
Conflicts: | neovim |
Provides: | neovim, vim-plugin-runtime |
Submitter: | fhahn |
Maintainer: | eclairevoyant |
Last Packager: | eclairevoyant |
Votes: | 251 |
Popularity: | 0.181997 |
First Submitted: | 2014-02-21 19:50 (UTC) |
Last Updated: | 2023-04-30 22:13 (UTC) |
Dependencies (19)
- glibc (glibc-force-mmap, lib32-glibc-force-mmap, glibc-minimal-git, glibc-linux4, glibc-git, glibc-widevine)
- hicolor-icon-theme (hicolor-icon-theme-git)
- libluv
- libtermkey (libtermkey-git, libtermkey-bzr)
- libuv (libuv-git)
- libvterm (libvterm-bzr, libvterm-0.1)
- lua51-lpeg
- luajit (luajit-2.1-lua52-git, luajit-openresty)
- msgpack-c
- tree-sitter (tree-sitter-git)
- unibilium
- cmake (cmake-git) (make)
- git (git-vfs, git-run-command-patch-git, git-git, git-fc) (make)
- ninja (ninja-git, ninja-samurai, ninja-kitware, ninja-mem, python-ninja) (make)
- python-neovim (python-neovim-git, python-pynvim) (optional) – for Python 3 plugin support (see :help provider-python)
- ruby-neovim (optional) – for Ruby plugin support (see :help provider-ruby)
- wl-clipboard (wl-clipboard-rs-git, wl-clipboard-git, wl-clipboard-rs) (optional) – for clipboard support on wayland (see :help clipboard)
- xclip (wl-clipboard-x11, xclip-git) (optional) – for X11 clipboard support (or xsel) (see :help provider-clipboard)
- xsel (xsel-git, wl-clipboard-x11) (optional) – for X11 clipboard support (or xclip) (see :help provider-clipboard)
Required by (402)
- astronvim (requires neovim)
- astronvim-git (requires neovim)
- bettervim (requires neovim)
- candyvim-git (requires neovim)
- cmp-buffer (requires neovim)
- cmp-nvim-lsp (requires neovim)
- completion-nvim (requires neovim)
- deoplete (requires neovim) (optional)
- deoplete-git (requires neovim) (optional)
- eovim (requires neovim)
- eovim-git (requires neovim)
- fvim (requires neovim)
- fvim-bin (requires neovim)
- glrnvim (requires neovim)
- gnvim (requires neovim)
- gnvim-git (requires neovim)
- goneovim-bin (requires neovim)
- goneovim-git (requires neovim)
- gonvim (requires neovim)
- instant-rst (requires neovim) (optional)
- Show 382 more...
Sources (3)
jhossbach commented on 2023-04-29 10:02 (UTC) (edited on 2023-04-29 10:02 (UTC) by jhossbach)
chris34241 commented on 2023-04-27 14:46 (UTC)
I'm getting this error when building:
/usr/bin/ld: cannot find -llpeg: No such file or directory
I think it might be related to this commit but I do not know how to fix it. Any ideas?
syyyr commented on 2023-04-20 14:16 (UTC)
upstream issue for the mpack build failure: https://github.com/neovim/neovim/issues/23213
eclairevoyant commented on 2023-04-20 10:20 (UTC)
yeah, normally the way to avoid your current system's packages affecting the build environment is by building in a clean chroot
moreka commented on 2023-04-20 09:00 (UTC) (edited on 2023-04-20 09:05 (UTC) by moreka)
UPDATE: It works now. Had to manually remove lua51-mpack
and then reinstall neovim-git
. Thanks again.
Thanks for the amazing speed @eclairevoyant. Unfortunately I still get the same error.
eclairevoyant commented on 2023-04-20 08:50 (UTC)
fixed
moreka commented on 2023-04-20 08:12 (UTC) (edited on 2023-04-20 08:13 (UTC) by moreka)
There is a build failure:
/usr/bin/luajit: ...-git/src/neovim/src/nvim/generators/gen_api_dispatch.lua:196: attempt to call field 'encode' (a nil value)
I am guessing it is due to this commit and is related to mpack
. Don't know how to fix it, though. Any ideas?
eclairevoyant commented on 2023-03-04 16:18 (UTC)
If you submit an orphan request for a package that's been out of date more than some threshold (I believe 6 months?) then it will automatically get orphaned. Thanks for reaching out.
REmorin commented on 2023-03-04 16:15 (UTC)
@eclairevoyant Thanks!
About the hypothetical package, I was suggesting it before I found out abandoned packages could be adopted so easily; I think it would have some hypothetical differences (more stability of neovim and the aur package, etc.) over the nightly binaries and master, but not substantial enough.
eclairevoyant commented on 2023-03-04 15:00 (UTC)
@REmorin I've orphaned and adopted neovim-nightly-bin
, I can fix the issues there.
Regarding your suggested hypothetical package, rule #1 of the AUR is it should be a useful package; is there some substantial difference with using the nightly
branch instead of the master
branch?
Pinned Comments
fwalch commented on 2016-07-04 19:52 (UTC) (edited on 2016-07-04 19:54 (UTC) by fwalch)