On Sun, Apr 01 2018, Utkarsh Anand <utkarsh...@yandex.com> wrote: >> 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. > "Do you know the definition of insanity?" -- VAAS (Far Cry 3) > https://github.com/neovim/neovim/pull/8215/commits/53d5789124122ad1a8d8e585127429c304fd0ed9
Again, this would not be needed if you just used Lua, which is far nicer than LuaJIT from a portability PoV. I suggested using the same solution/workaround as in the neovim port since that's probably how most people will run neovim on OpenBSD. >> Surely neovim users on OpenBSD care more about the safety and >> portability of their editor than about raw speed in benchmarks. > Being a perfectionist, I care about both B-| I understand you're trying to help here, but forcing the use of an ancient compiler is far from perfect in my book. Fixing LuaJIT to build and work on OpenBSD out of the box looks like a much more correct approach, but is not trivial. -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
