On Sun, Apr 01 2018, Utkarsh Anand <utkarsh...@yandex.com> wrote: > 01.04.2018, 20:05, "Jeremie Courreges-Anglas" <j...@wxcvbn.org>: >> On Sun, Apr 01 2018, Utkarsh Anand <utkarsh...@yandex.com> wrote: >>> Thank you all for your inputs. With this, I conclude almost complete >>> support for OpenBSD: >>> >>> https://github.com/neovim/neovim/pull/8215/commits/0f65aa585985ad00803d681c85779011c9e9682a >> >> This looks very wrong, you should fix the build with clang instead of >> forcing neovim to use an old gcc version. Please do not push this >> upstream. > > Only LuaJIT builds with gcc. Neovim builds with clang.
Sloppy wording from me indeed, allow me to rephrase: This looks very wrong, you should fix the build with clang instead of forcing LuaJIT-bundled-with-neovim to use an old gcc version. Please do not push this upstream (neovim or LuaJIT). The specific commit I'm referencing is: https://github.com/neovim/neovim/pull/8215/commits/8c9931da055fe0c36ca14edc8945ad2047bfa0cd An easier and saner solution would be to use standard Lua instead of LuaJIT, as done in the neovim port, passing -DPREFER_LUA=ON to cmake. Surely neovim users on OpenBSD care more about the safety and portability of their editor than about raw speed in benchmarks. -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
