Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 23 May 2019 17:43:26 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 238079] editors/neovim: use Lua instead of LuaJIT on various architectures (aarch64, powerpc64 etc)
Message-ID:  <bug-238079-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238079

            Bug ID: 238079
           Summary: editors/neovim: use Lua instead of LuaJIT on various
                    architectures (aarch64, powerpc64 etc)
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: adamw@FreeBSD.org
          Reporter: greg@unrelenting.technology
          Assignee: adamw@FreeBSD.org
             Flags: maintainer-feedback?(adamw@FreeBSD.org)

Created attachment 204572
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D204572&action=
=3Dedit
neovim-lua.patch

So, Neovim defaults to LuaJIT, but FreeBSD Ports currently only has LuaJIT
2.0.5, while support for aarch64 and mips64 was only added in 2.1.0-beta, a=
nd
powerpc64 support only exists in an unofficial fork
https://github.com/PPC64/LuaJIT

I posted a luajit 2.1.0-beta3 update as bug 225342, but its dependencies bug
226537 and bug 226541 are still unresolved.

And recently I've discovered an extra problem: LuaJIT was still calling
setrlimit for some reason related to FreeBSD <10 not supporting MAP32 or
something, which was imposing a data size limit on any process you'd run un=
der
neovim :D https://github.com/siddhesh/LuaJIT/pull/1 =E2=80=94 I've sent the=
 fix to one
of the maintained forks, I should also post it to ports but I haven't check=
ed
if it applies to 2.0.5.

Aaaaanyway, since the 2.1.0-beta3 update is not merged yet, let's just unbr=
eak
neovim already by using regular Lua on non-x86 platforms instead. Turns out
Neovim does support lua 5.2+ https://github.com/neovim/neovim/pull/9280/fil=
es
and other distributions are using this for architectures like aarch64:
https://github.com/NixOS/nixpkgs/pull/61588

Honestly I'd be okay with always using regular Lua on any platform, but tha=
t's
not my call to make.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-238079-7788>