[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: needs suggestion on LuaJit's IBM architecture dilemma



Hello all,

It'd be better to switch to luajit2 if it is possible. We can see right now the main issue with luajit project is no response from upstream of LuaJIT to previous merge request attempts. And luajit2 already contains almost everything needed for s390x support.

 

Thanks,

-Dipak

 

From: M. Zhou <lumin@debian.org>
Date: Thursday, 12 May 2022 at 8:07 AM
To: debian-devel <debian-devel@lists.debian.org>
Subject: [EXTERNAL] needs suggestion on LuaJit's IBM architecture dilemma

Hi folks,

I learned in disappointment after becoming LuaJit uploader that
the LuaJit upstream behaves uncooperatively especially for IBM
architectures [1]. IIUC, the upstream has no intention to care
about IBM architectures (ppc64el, s390x).

The current ppc64el support on stable is done through cherry-picked
out-of-tree patch. And I learned that the patch is no longer
functional[2] for newer snapshots if we step away from that
ancient 2.1.0~beta3 release.

However, architectures like amd64 needs relatively newer version[3],
while IBM architecture still has demand luajit[4] (only the
ancient version will possibly work on IBM archs).

I'm looking for suggestions on what to do next:

option 1:
  drop IBM architectures that the upstream cannot support
  from src:luajit, and provide archs like amd64 with relatively
  newer snapshot versions[5].
  and package reliable alternatives (if any) for IBM archs.
option 2:
  use latest source for amd64 architecture, and rollback the
  source specifically for IBM architectures to keep it
  functional.
option 3:
  rollback to the ancient stable release and screw it
option 4:
  ...

Thanks.

[1] https://github.com/LuaJIT/LuaJIT/pull/140
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004511
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981808
[4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008858
[5] Yes ... the upstream do not release anymore.


Reply to: