| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Done, thank you for the advice :-) |
Sorry, something went wrong.
|
New CI, just in case: https://ci.nodejs.org/job/node-test-pull-request/5555/ |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM but please format the commit log according to the style guide from CONTRIBUTING.md.
Sorry, something went wrong.
|
Commit log suggestion: build: add (not) cross-compiled configure flags Adds --cross-compiling and --no-cross-compiling flags Fixes: https://github.com/nodejs/node/issues/10271 |
Sorry, something went wrong.
Adds --cross-compiling and --no-cross-compiling flags Fixes: nodejs#10271
Done, thanks for the suggestion :-) |
Sorry, something went wrong.
|
Thank you :-) |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Checklist
Affected core subsystem(s)
Build and compilation
Description of change
This fixes issue #10271, allowing to explicitly set that we are doing a cross-compilation (or not, if we desire so) instead of only rely on heuristics. This is useful when you are compiling to the same target CPU of your host system by using a toolchain that uses a different C lib (like musl from glib), since mkpeephole gets compiled with the cross-toolchain and later can't be executed. This way we can force it to use the host toolchain instead. By default it still use the heuristics.
I have checked that it correctly set the GYP variables correctly and the compiled Node.js works as expected.