Source: nodejs Version: 18.12.1+dfsg-2+0.riscv64.1 Followup-For: Bug #1025736
Hi David,
I can run nodejs(18.12.1+dfsg-2) on real riscv64 hardware:
```
vimer@unmatched10:~/build/01_nodejs$ nodejs --help
Usage: node [options] [ script.js ] [arguments]
node inspect [options] [ script.js | host:port ] [arguments]
Options:
- script read from stdin (default if
no file name is
provided, interactive mode if a tty)
-- indicate the end of node options
--abort-on-uncaught-exception aborting instead of exiting causes a
core file to be
generated for analysis
--build-snapshot Generate a snapshot blob when the
process exits. Currently
only supported in the
node_mksnapshot binary.
-c, --check syntax check script without executing
--completion-bash print source-able bash completion
script
-C, --conditions=... additional user conditions for
conditional exports and
imports
...
vimer@unmatched10:~/build/01_nodejs$ uname -a
Linux unmatched10 6.0.0-2-riscv64 #1 SMP Debian 6.0.3-1 (2022-10-21) riscv64
GNU/Linux
vimer@unmatched10:~/build/01_nodejs$ apt-cache policy nodejs
nodejs:
Installed: 18.12.1+dfsg-2
Candidate: 18.12.1+dfsg-2
Version table:
*** 18.12.1+dfsg-2 100
100 /var/lib/dpkg/status
18.10.0+dfsg-6 500
500 https://mirror.iscas.ac.cn/debian-ports sid/main riscv64 Packages
```
But I got the same result with you in qemu, hope this helps.
--
Regards,
--
Bo YU
signature.asc
Description: PGP signature
-- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
