I'm using an own cross-toolchain to compile Node.js using musl from a Ubuntu glib-based system. Thing is that I get always the next error:
/bin/sh: 1: /home/piranna/Proyectos/nodejs/deps/node/out/Release/mkpeephole: not found
The file is there, but since I'm using the cross-toolchain to compile Node.js, mkpeephole gets to be compiled with it too because I'm cross-compiling from LInux x86_64 GLib to Linux x86_64 musl, and at configure script it's only being considered the CPU architecture to detect if it's being done a cross-compilation. I would consider adding other heuristics to check if a cross-compilation is being done, specially the C standard lib being used but also the operating system and others, or alternatively add an option to set explicitly that a cross-compilation is being done.
I'm using an own cross-toolchain to compile Node.js using musl from a Ubuntu glib-based system. Thing is that I get always the next error:
The file is there, but since I'm using the cross-toolchain to compile Node.js,
mkpeepholegets to be compiled with it too because I'm cross-compiling from LInux x86_64 GLib to Linux x86_64 musl, and atconfigurescript it's only being considered the CPU architecture to detect if it's being done a cross-compilation. I would consider adding other heuristics to check if a cross-compilation is being done, specially the C standard lib being used but also the operating system and others, or alternatively add an option to set explicitly that a cross-compilation is being done.