Bad system call (running Luvi) - missing syscall 425.
- Dominant language
- C
- Stars
- 20.5k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
Description
Basically I'm trying to get Luvit running on iSH, and I've been trying to build Luvit using a script from `luvit-bin` repo on GitHub, but it has stopped on running Luvi (not a typo). When I try to run `./luvi`, it responds with `Bad system call`. I've used `dmesg`, and it responded with `19(luvi) missing syscall 425`. That's all I know.
_About Luvit, and why I'm talking about Luvi instead - Luvit is based on three things: Lit, Luvi and Luvit. Luvi is compiled first, then it's used to make Lit, and Lit is used to make Luvit. Install script stops at the point where Luvi is already compiled, and script tries to run Luvi, but it can't due to bad system call. I've compiled it from this script: https://github.com/truemedian/luvit-bin_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the failure with the compiled `./luvi` and checking `dmesg` for missing syscall 425. The issue names no iSH source file or test; done would mean Luvi runs on iSH and the Luvit build script proceeds past that step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100