nxodejs: fix cross

[Cogitri]

No description provided.

[Cogitri]

aarch64 binaries tested on my RPI3

[Hoshpak]

there's a typo in the commit message. Besides, it still fails on armv6l and armv7l.

[Cogitri]

Besides, it still fails on armv6l and armv7l.

Hum, seems like V8 assumes that we build for 32-bit if we compile to a 32-bit platform

FWIW, we have to do this due to nodejs/node#21079, their code generation tool links against V8 so we have to build it for the host too (sigh)

[Cogitri]

https://github.com/nodejs/node/blob/master/deps/v8/src/base/build_config.h#L149

Seems like we actually have to build nodejs >= 10.9.0 from a i686 host...

[Hoshpak]

Since all builders are x86_64 and that is not likely to change (especially not to a legacy architecture like i686), that means we just cannot build nodejs for 32 bit arm architectures any more.

[Cogitri]

Yup, currently marking it as broken

[Cogitri]

Alright, this should work on aarch64* now, but I'll do some more testing - CI and builders seem busy anyway :P

[Hoshpak]

this will also require removal of nodejs from the armv[67]l* repositories as the builders are currently staging because of nodejs.

[pullmoll]

Perhaps disabling the v8-snapshot option, however it is called in the nodejs v8 source, can fix the problems when cross compiling from 64 to 32 bit. We do that for qt5-webengine's v8 and IIRC I had similar problems before doing that in a previous qt5 version.

[Cogitri]

I don't think node >=10 has that option anymore and looking at https://github.com/void-linux/void-packages/pull/6573/files#diff-8421a2e1c1611cb3b4ee616adbdd6a15L38 it seems like we did pass that to node.

[maxice8]

Please notify when proposed changes are made