npm -v和node.js在交叉编译的nodejs0.12.2上抛出非法指令

Question

我使用以下工具链交叉编译了用于Atmel SAMA5D36的nodejs 0.12.2

export AR=arm-linux-gnueabihf-ar
export CC=arm-linux-gnueabihf-gcc
export CXX=arm-linux-gnueabihf-g++
export LINK=arm-linux-gnueabihf-g++

并配置和构建如下

./configure --without-snapshot --dest-cpu = arm --dest-os = linux --prefix =/home/root/nodejs-v0.12.2

make make install DESTDIR =/home/user/Desktop/nodejs_arm/nodebins

编译的文件夹在/ home/user/Desktop/nodejs_arm/nodebins/home/root中生成

我将该文件夹压缩成tar文件并传输到AtmelSAMA5D36 arm board.我在/ home/root目录中的板上解压缩并在符号链接后创建

ln -s /home/root/nodejs-v0.12.2/bin/npm /bin/npm
ln -s /home/root/nodejs-v0.12.2/bin/node /bin/node

当我使用"node -v"和"npm -v"测试它时,

"node -v"给出正确的输出但是

"npm -v"抛出"非法指令"错误
与"节点"相同.

但是,交叉编译的nodejs 0.10.40工作正常.

任何帮助都非常感谢.

更新:

(gdb) run
Starting program: /usr/bin/node
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".

Program received signal SIGILL, Illegal instruction.
0xb6edfec0 in _armv7_neon_probe () from /usr/lib/libcrypto.so.1.0.0
(gdb) c
Continuing.

Program received signal SIGILL, Illegal instruction.
0xb6edfec8 in _armv7_tick () from /usr/lib/libcrypto.so.1.0.0
(gdb) c
Continuing.
[New Thread 0xb65ca4c0 (LWP 3774)]
[New Thread 0xb67ca4c0 (LWP 3773)]
[New Thread 0xb69ca4c0 (LWP 3772)]
[New Thread 0xb6bca4c0 (LWP 3771)]

Program received signal SIGILL, Illegal instruction.
0x0054b504 in v8::internal::ComputeFlagListHash() ()
(gdb) c
Continuing.
[Thread 0xb65ca4c0 (LWP 3774) exited]
[Thread 0xb67ca4c0 (LWP 3773) exited]
[Thread 0xb69ca4c0 (LWP 3772) exited]
[Thread 0xb6bca4c0 (LWP 3771) exited]

Program terminated with signal SIGILL, Illegal instruction.
The program no longer exists.
(gdb) q
# gdb node -e 0
GNU gdb (GDB) 7.9.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-buildroot-linux-uclibcgnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from node...
(gdb)
(gdb) run
Starting program: /usr/bin/node
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
[New Thread 0xb64f84c0 (LWP 14382)]
[New Thread 0xb66f84c0 (LWP 14381)]
[New Thread 0xb68f84c0 (LWP 14380)]
[New Thread 0xb6af84c0 (LWP 14379)]

Program received signal SIGILL, Illegal instruction.
0x0054b504 in v8::internal::ComputeFlagListHash() ()
(gdb)
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /usr/bin/node
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
[New Thread 0xb653d4c0 (LWP 14531)]
[New Thread 0xb673d4c0 (LWP 14530)]
[New Thread 0xb693d4c0 (LWP 14529)]
[New Thread 0xb6b3d4c0 (LWP 14528)]

Program received signal SIGILL, Illegal instruction.
0x0054b504 in v8::internal::ComputeFlagListHash() ()
(gdb) Program received signal SIGILL, Illegal instruction.
Undefined command: "Program".  Try "help".
(gdb) 0x0054b504 in v8::internal::ComputeFlagListHash() ()bt
Undefined command: "0x0054b504".  Try "help".
(gdb) bt
#0  0x0054b504 in v8::internal::ComputeFlagListHash() ()
#1  0x007b8a54 in v8::internal::V8::InitializeOncePerProcessImpl() ()
#2  0x009281b0 in v8::base::CallOnceImpl(int*, void (*)(void*), void*) ()
#3  0x007b8ba8 in v8::internal::V8::Initialize() ()
#4  0x0028fc74 in v8::V8::Initialize() ()
#5  0x00897a34 in node::Start(int, char**) ()
#6  0xb6b95634 in __uClibc_main () from /lib/libc.so.1
#7  0x00000000 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) q

Answer 1

我们在尝试通过 SAMA5D31 上的 buildroot 工具链使用 Nodejs 6.1.0 时遇到了类似的问题，并遇到了相同的“非法指令”问题。最后我们改用版本 0.10.45，它包含在旧处理器（armv5 及更早版本）的 buildroot 中。

在对此问题进行故障排除时，问题似乎出在 Node 使用的 Node.js 和 OpenSSL 库中，其中编译的代码尝试使用 Neon 指令进行浮点运算。SAMA5D3X 处理器报告为armV7，但没有Neon FPU。然而，nodejs（以及我们的 openssl）正在尝试使用 Neon 指令，因为它假设它是armV7。在 Nodejs 可以处理非 Neon ArmV7 之前，最好的选择是使用 0.10.40 或 0.10.45 版本的 Node，直到可以解决该问题。或者自行修改节点的构建配置以处理非 Neon armV7。