Package Details: neovim-git 0.11.0.r711.g7b7c95dac9-1

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: Farzat (gpanders)
Last Packager: gpanders
Votes: 257
Popularity: 1.22
First Submitted: 2014-02-21 19:50 (UTC)
Last Updated: 2024-09-04 00:24 (UTC)

Dependencies (24)

Required by (431)

Sources (3)

Pinned Comments

fwalch commented on 2016-07-04 19:52 (UTC) (edited on 2016-07-04 19:54 (UTC) by fwalch)

Please don't flag this package out-of-date just because the version number displayed on AUR seems old. This is normal for VCS packages. As long as building the package works without problems, it isn't necessary to update the PKGBUILD here. makepkg will automatically retrieve the latest version when you build the package locally.

Latest Comments

« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 28 29 .. 40 Next › Last »

fwalch commented on 2015-06-04 08:20 (UTC)

@swiftgeek: That's because I have the following in /etc/makepkg.conf: CFLAGS="-march=native -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2" Neovim doesn't work with FORTIFY_SOURCE=2, so it adds -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1. Only if I remove the FORTIFY_SOURCE stuff from my /etc/makepkg.conf, I can reproduce your error. In the other case, hardened-wrapper will automatically use FORTIFY_SOURCE=1 and not break the build. So, if you want hardened executables *all the time* (since hardened-wrapper is apparently in your default PATH), why don't you just set the appropriate CFLAGS in /etc/makepkg.conf?

swiftgeek commented on 2015-06-04 08:06 (UTC)

Just as explained in issue - setting any vim variable (triggers buffer overflow detection) While i have -D_FORTIFY_SOURCE=2 in makepkg.conf it is dropped in resulting cc (`pgrep -a cc` during compilation for actual compilation line) hardening-wrapper obviously bypasses all logic in cmake and pushes own flags Also your line is very curious anyway: -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1

fwalch commented on 2015-06-04 07:53 (UTC)

@swiftgeek: Just compiled and ran nvim with hardening-wrapper without problems. To confirm that it was used, some output from 'nvim --version': Compilation: /usr/lib/hardening-wrapper/bin/cc -march=native -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -DINCLUDE_GENERATED_DECLARATIONS -DHAVE_CONFIG_H What exactly does not work in your case? (maybe create a new issue at github.com/neovim/neovim so we can discuss it without flooding the comments here).

swiftgeek commented on 2015-06-03 17:41 (UTC)

Build stage conficts with hardening-wrapper, please drop it from PATH in build() till #223 is resolved (/usr/lib/hardening-wrapper/bin) https://github.com/neovim/neovim/issues/223 https://www.archlinux.org/packages/community/x86_64/hardening-wrapper/

fwalch commented on 2015-06-01 06:56 (UTC)

@Emil: Can you try again with `makepkg -C`? If that doesn't help, can you open an issue at [1]? [1] https://github.com/neovim/neovim/issues

Emil commented on 2015-05-31 23:30 (UTC)

I get this erros while trying to build: ... -- Found LibUV: /usr/lib64/libuv.so CMake Error at /usr/share/cmake-3.2/Modules/FindPackageHandleStandardArgs.cmake:138 (message): Could NOT find Msgpack (missing: MSGPACK_LIBRARY MSGPACK_INCLUDE_DIR) Call Stack (most recent call first): /usr/share/cmake-3.2/Modules/FindPackageHandleStandardArgs.cmake:374 (_FPHSA_FAILURE_MESSAGE) cmake/FindMsgpack.cmake:46 (find_package_handle_standard_args) CMakeLists.txt:178 (find_package) -- Configuring incomplete, errors occurred! See also "/home/emil/Downloads/neovim-git/src/neovim-git/build/CMakeFiles/CMakeOutput.log". See also "/home/emil/Downloads/neovim-git/src/neovim-git/build/CMakeFiles/CMakeError.log". log files: http://pastebin.com/W8f4ZXs3, http://pastebin.com/TpyqEkGx Any idea what's going wrong here?

donnut commented on 2015-05-29 12:55 (UTC)

Solved the issue with MessagePack by making the package in a clean directory.

donnut commented on 2015-05-29 10:51 (UTC)

I've installed neovim successfully up to version neovim-git-0.r3370.df3abf4 Attempting to upgrade to 0.r3530.fa0f122 gives a problem with the MessagePack: > -- [/usr/bin/lua] The 'MessagePack' lua package is required for building Neovim > CMake Error at CMakeLists.txt:247 (message): > A suitable Lua interpreter was not found lua51-messagepack from AUR is installed Reading a comment of @ingvij I tryed to specify lua5.1 instead of the system lua (5.3) in CMakeCache.txt. This gives the error: > -- Checking Lua interpreter /usr/bin/lua5.1 > -- [/usr/bin/lua5.1] The 'bit' lua package is required for building Neovim > CMake Error at CMakeLists.txt:247 (message): > A suitable Lua interpreter was not found Any idea what I'm doing wrong?

ingvij commented on 2015-05-27 18:13 (UTC)

@fwalch: Yep, it's resolved. Thanks

fwalch commented on 2015-05-27 14:55 (UTC)

The issue with `makepkg -i` should be resolved now. There's still a problem when installing with pacaur [1]. [1] https://github.com/rmarquis/pacaur/issues/325

« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 28 29 .. 40 Next › Last »