>I understand you're trying to help here, but forcing the use of an >ancient compiler is far from perfect in my book. I guess you're talking about LuaJIT using gcc by default, because neovim now uses clang all around wherever possible.
>Fixing LuaJIT to build >and work on OpenBSD out of the box looks like a much more correct >approach, but is not trivial. While building does look trivial to me right now, you might want to elaborate a bit more on that. The choice of not using LuaJIT does not entirely depend on me. The owner of the repository asked me to help run CI for OpenBSD and so I did. I have no control over the choices made for the project. If I were to 'fix' LuaJIT, a bit more elaboration on what all is required would be really helpful. ___________________ PGP: http://pgp.mit.edu/pks/lookup?op=vindex&search=0x96E661DB874CC83F
