-
Notifications
You must be signed in to change notification settings - Fork 30.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Node fails to start on MTK7620: "Illegal instruction" #4818
Comments
Can you run |
Aside, it's odd that you ran configure with |
root@OpenWrt:/# cat test.js root@OpenWrt:~# gdb --args node test.js Program received signal SIGILL, Illegal instruction. |
root@OpenWrt:/usr/bin# ldd node root@OpenWrt:/usr/bin# node -v |
Are you sure the kernel has FPU emulation compiled in? Does |
dmesg | grep -i fpu |
After |
thanks a lot!!!!! but dmesg | grep -i fpu still no any output!! |
I am sorry, does the app still crash after enabling software fpu? |
From what I understand, floating point emulation on MIPS platforms was disabled several years ago: https://lists.openwrt.org/pipermail/openwrt-devel/2009-June/004562.html , So, node.js should be compiled with floating point emulation support - but, apparently, it is not. I have this same issue with CC 15.05.1 on a TP-LINK TL-WR1043ND v3 (CPU MIPS 74Kc V5.0): the binary package for Node downloaded from https://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/packages/packages/node_v0.12.7-1_ar71xx.ipk crashes on a FP instruction (swc1): Program received signal SIGILL, Illegal instruction. |
I cross compiled nodejs for a MIPSel target (without FPU but FPU emulation in the kernel) using the OpenWRT 15.05 Chaos Calmer toolchain. The target CPU is an MT7620A
I compile using:
./configure --without-snapshot --dest-cpu=mipsel --dest-os=linux --without-npm --without-ssl --without-etw --without-perfctr --with-mips-float-abi=soft
However then I run into the problem is describing.
"Illegal instruction"
on any of the js files in the test directory.
I can execute
node -v
, but notnode test.js
, ornode debug test.js
information see below:
The text was updated successfully, but these errors were encountered: