Cannot `npm i node@8` on an armv7l machine

[losingkeys]

I've made a demo repo for this issue.

I think this may be related to #53, but I'm not sure. Please let me know if you need more information than the stuff in my demo repo. Thanks!

[aredridel]

I'm not on armv7l, but what's the error you get?

[losingkeys]

Error: Cannot find module 'node-linux-arm/package.json' (logs here).

There's a longer explanation in the demo project's README. Let me know if you can't access it or need more info :).

[aredridel]

What's the value of process.arch on your platform?

[losingkeys]

'arm'

[aredridel]

Well fudge. Is there one that supplies the 'v7l' ?

[losingkeys]

Hmm... arch responds with armv7l.. but I'm having trouble getting even 7 from node... Here are some threads tracking the same issue:

1. Host arch ARMv7 not correctly detected electron/packager#523 (comment)
2. process.arch not matching with systems arch output for ARM nodejs/node#9491

• Note: I get the same output as this commenter, i.e. uname -m -> armv7l and node -p 'process.config.variables.arm_version' -> 6

Could you run the external commands uname -m or arch via node? I know that's nasty.. but node -p 'process' | grep arm and similar exploratory commands didn't turn up anything useful for me :(

[aredridel]

What about os.arch() an os.platform() ?

[aredridel]

Shelling out to uname isn't the worst thing. It's done only at install time, and that script is where the mess Should live.

[losingkeys]

• os.arch() -> 'arm'
• os.process() -> 'linux'

Good point about it being in an install script. Seems like an acceptable solution. I didn't find much in the linked threads, though I definitely didn't read all of them.

[aredridel]

Geez, node :(

[losingkeys]

Would you be okay with me taking a crack at using the external program arch in the build setup? I'm not exactly sure how to do this, but will take a look if you like that solution.

[aredridel]

Yeah, either arch or uname, go for it!