-
Notifications
You must be signed in to change notification settings - Fork 30.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Duplicate v8 target errors when cross-compiling #37441
Comments
It still the case for 18.4.0... Any chance to fix the upstream? |
Same issue when cross-compiling nodejs 16.15.0 using Buildroot (x86_64 VM -> arm64 target). |
Hi @scr06 , Did you by any chance solved this issue? |
Unfortunatly no... I managed to get pre-built librairies for arm target. But node modules are not available... |
… error Reported also via: nodejs/node#37441 Patched in: minrk/node@5e533cb The error is: ``` ninja: Entering directory `out/Release' ninja: error: obj.host/tools/v8_gypfiles/run_torque.ninja:1356: multiple rules generate gen/torque-generated/bit-fields.h [-w dupbuild=err] make[2]: *** [Makefile:127: node] Error 1 make[1]: *** [package/pkg-generic.mk:293: <buildroot>/output/build/nodejs-16.15.0/.stamp_built] Error 2 make: *** [Makefile:84: _all] Error 2 ``` Fixes: http://autobuild.buildroot.net/results/7fe9132236ee8e3a86dd97fe96ffee42990c2d19/ Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com> [Thomas: - regenerate patch as a git formatted patch, add a link to the original location, add my own SoB to it - improve commit log] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
… error Reported also via: nodejs/node#37441 Patched in: minrk/node@5e533cb The error is: ``` ninja: Entering directory `out/Release' ninja: error: obj.host/tools/v8_gypfiles/run_torque.ninja:1356: multiple rules generate gen/torque-generated/bit-fields.h [-w dupbuild=err] make[2]: *** [Makefile:127: node] Error 1 make[1]: *** [package/pkg-generic.mk:293: <buildroot>/output/build/nodejs-16.15.0/.stamp_built] Error 2 make: *** [Makefile:84: _all] Error 2 ``` Fixes: http://autobuild.buildroot.net/results/7fe9132236ee8e3a86dd97fe96ffee42990c2d19/ Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com> [Thomas: - regenerate patch as a git formatted patch, add a link to the original location, add my own SoB to it - improve commit log] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> (cherry picked from commit 5708c5b) Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
avoids duplicate ninja rules for v8 used in host and target From: minrk/node@5e533cb Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Reported in nodejs/node#46690 and nodejs/node#37441 Signed-off-by: Tim Orling <tim.orling@konsulko.com>
avoids duplicate ninja rules for v8 used in host and target From: minrk/node@5e533cb Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Reported in nodejs/node#46690 and nodejs/node#37441 Minor refactoring as recommended by Christian Clauss. Signed-off-by: Tim Orling <tim.orling@konsulko.com>
avoids duplicate ninja rules for v8 used in host and target From: minrk/node@5e533cb Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Reported in nodejs/node#46690 and nodejs/node#37441 Minor refactoring as recommended by Christian Clauss. Signed-off-by: Tim Orling <tim.orling@konsulko.com>
avoids duplicate ninja rules for v8 used in host and target From: minrk/node@5e533cb Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Reported in nodejs/node#46690 and nodejs/node#37441 Minor refactoring as recommended by Christian Clauss. Signed-off-by: Tim Orling <tim.orling@konsulko.com>
We are working on packaging node for arm64 macs over at conda-forge
Attempting to cross-compile on mac, x86_64 -> arm64 with
fails with this error:
I was able to narrow it down to the fact that v8/torque is built for both host and target, while SHARED_INTERMEDIATE_DIR is not unique per toolset.
Adding
$|OBJ
to SHARED_INTERMEDIATE_DIR via this patch so it is per-toolchain instead of per-product seems to work, but I don't know if that's actually the right fix. It seems plausible that these should only be generated once, and the bug really is is that they are being generated twice. I couldn't figure out how to solve that, though.The text was updated successfully, but these errors were encountered: