### Version 19.6.0 (actually git 1b87cb6f39e95267162de92bde9a5bf9c02ad453) ### Platform Linux oss-tx204 5.15.0-41-generic #44-Ubuntu SMP Thu Jun 23 11:20:13 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux ### Subsystem _No response_ ### What steps will reproduce the bug? Configure node to use the cross-compile rules with ninja, then try building it: ```shell $ ./configure --cross-compiling --ninja && make Node.js configure: Found Python 3.10.6... INFO: configure completed successfully ninja -C out/Release ninja: Entering directory `out/Release' ninja: error: obj.host/tools/v8_gypfiles/run_torque.ninja:1451: multiple rules generate gen/torque-generated/bit-fields.h [-w dupbuild=err] ``` This doesn't happen if using ninja but not cross-compiling, or if cross-compiling without ninja. ### How often does it reproduce? Is there a required condition? _No response_ ### What is the expected behavior? _No response_ ### What do you see instead? ``` ninja: error: obj.host/tools/v8_gypfiles/run_torque.ninja:1451: multiple rules generate gen/torque-generated/bit-fields.h [-w dupbuild=err] ``` ### Additional information _No response_
Activity
moto-timo commentedon Feb 16, 2023
The exact same behavior also occurs on
v16.xbranch.bnoordhuis commentedon Feb 17, 2023
I don't think cross-compiling with ninja has ever worked. For anyone wanting to work on this, it probably requires applying fixes to https://github.com/nodejs/gyp-next/blob/main/pylib/gyp/generator/ninja.py
thunder-coding commentedon Feb 18, 2023
Seems like a duplicate of #37441.
Also if you scroll down you can see that a fix (or workaround) is available in a fork minrk@5e533cb, which is in use by buildroot
bnoordhuis commentedon Feb 18, 2023
Oh, indeed it is. I'll close it as such then.
fix: duplicate ninja rules for v8 (cross-compiling)
fix: duplicate ninja rules for v8 (cross-compiling)
fix: duplicate ninja rules for v8 (cross-compiling)
fix: duplicate ninja rules for v8 (cross-compiling)