Repository navigation
process.config.variables.arm_version incorrect in armv7 #4531
Description
Armv7 machine (Scaleway C1). I install node from node-v4.2.4-linux-armv7l.tar.gz. Run node -p process.config.variables.arm_version. It returns incorrect value 6. Expected correct value 7. When node 4.2.4 is compiled from source, it gives correct value 7.
Run readelf -A /usr/bin/node | grep CPU_arch:. Gives correct value "v7". So the binary is armv7 but process.config seems incorrect.
The gist https://github.com/proxy/gist.github.com/igorklopov/8edef2199419e3fb9c99 shows that it started in 4.1.0. Node 4.0.0 was not affected.
Activity
rvagg commentedon Jan 5, 2016
Thanks for reporting this @igorklopov, I'm a little surprised this went unnoticed for so long. I can confirm your analysis and I've traced it to the fact that we're using Raspbian to get gcc 4.8 on the machine we're using to compile these binaries even though it's a vanilla Debian Wheezy armhf base, and of course Raspbian is armv6 so we get
#define __ARM_ARCH 6from the compiler...Doh!
Which means we need to go back to finding a Wheezy armhf gcc 4.8(+) source or build one ourselves (which I think I did in the past but that's such a nightmare).
/cc @nodejs/build
XadillaX commentedon Jun 16, 2017
I will try to take this issue and fix.
interpretor commentedon Jul 6, 2017
This really is a problem, as without any correct architecture information I can not load the correct prebuilt binaries.
Any suggestions for a workaround that does not involve bash scripting?
Trott commentedon Aug 10, 2017
Any chance someone is in a position to move this forward? Or should we label this
stalledand/orhelp wanted?bnoordhuis commentedon Aug 10, 2017
Moving to nodejs/build#829.