deon wrote to Digital Man <=-
Noticing something odd and looking for advise.
On intel:
====
/opt/sbbs # jsexec binkit
JSexec v3.30a-Linux next-js/6a2a5eef1 - Execute Synchronet JavaScript Module Compiled Apr 14 2026 07:54 with GCC 15.2.0
Loading configuration files from /opt/sbbs/ctrl
JavaScript-C128.14.0
JavaScript: Initializing engine: 16777216 bytes max
Reading script from /opt/sbbs/exec/binkit.js
/opt/sbbs/exec/binkit.js compiled in 0.00 seconds
====
All good.
However on aarch64
====
/opt/sbbs # jsexec binkit
!No JavaScript module-name or expression specified
JSexec v3.30a-Linux next-js/6a2a5eef1 - Execute Synchronet JavaScript Module Compiled Apr 14 2026 07:54 with GCC 15.2.0
usage: jsexec [-opts] [[path/]module[.js] [args]
or: jsexec [-opts] -r js-expression [args]
or: jsexec -v
available opts:
...
Returning error code: 1
/opt/sbbs # ls -al exec/binkit.js
-rw-r--r-- 1 sbbs root 36851 Apr 15 07:19 exec/binkit.js ====
Cannot run jsexec on the command line to run any commands (connecting
via telnet is working fine).
Any ideas?
Noticing something odd and looking for advise.
/opt/sbbs # jsexec binkit
!No JavaScript module-name or expression specified
JSexec v3.30a-Linux next-js/6a2a5eef1 - Execute Synchronet JavaScript Module Compiled Apr 14 2026 07:54 with GCC 15.2.0
I'm not DM..., but one difference is see is the lack of this line:
Loading configuration files from /opt/sbbs/ctrl
on your aarch64 version.
Do you have your SBBSCTRL environment variable set on that device?
If what Gamgee suggested isn't the culprit, try adding the ".js" extension to see if it works then?
JSexec v3.30a-Linux next-js/6a2a5eef1 - Execute Synchronet JavaScript Module Compiled Apr 14 2026 07:54 with GCC 15.2.0
I don't recommend you run this branch for now - there are still a lot of known and unknown issues.
Re: sbbs:next-js aarch64
By: Digital Man to deon on Wed Apr 15 2026 10:40 am
Howdy,
JSexec v3.30a-Linux next-js/6a2a5eef1 - Execute Synchronet JavaScript Module Compiled Apr 14 2026 07:54 with GCC 15.2.0
I don't recommend you run this branch for now - there are still a lot of known and unknown issues.
Bummer, for what I want to use it for, its working really well, except cannot jsxexec on aarch64.
My workaround is run the intel images my mac, and its working fine. Just thought you'd want to know that aarch64 seems to be an issue.
There are a lot of issues, but for what its worth, there's a CI job that builds and runs the jsexec test suite (exec/tests/*) on an M4 Mac Mini and it appears to be currently working. That said, I'm not surprised at all that you're seeing issues with that branch at the moment, it's very early still.
Re: sbbs:next-js aarch64
By: Digital Man to deon on Wed Apr 15 2026 05:52 pm
Howdy,
There are a lot of issues, but for what its worth, there's a CI job that builds and runs the jsexec test suite (exec/tests/*) on an M4 Mac Mini and it appears to be currently working. That said, I'm not surprised at all that you're seeing issues with that branch at the moment, it's very early still.
Is that test suite darwin/aarch64?
I'm running alpine-linux/aarch64, which from memory, I only saw an intel runner for alpine. My alpine-linux/intel is working fine on my M1.
Could this be another issue with the set_personality() that deuce was working on originaly with linux/aarch64?
| Sysop: | Thumper |
|---|---|
| Location: | Copperopolis, CA |
| Users: | 5 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 37:22:39 |
| Calls: | 157 |
| Files: | 4,897 |
| D/L today: |
4 files (162K bytes) |
| Messages: | 53,771 |