gyp: Inherit CC/CXX for CC/CXX.host #6173
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
CI without custom configure flags: CI on FreeBSD with custom configure flags: |
|
Can you try upstreaming it first? I don't want us to carry out-of-tree patches unless absolutely necessary. |
|
@bnoordhuis: That was the plan -- just want to have a better look through their bug trackers first. |
|
Can I suggest you upload the patch with |
|
Maybe assign a reviewer as well. |
|
LGTM here if it's rejected or gets stalled upstream |
|
@bnoordhuis silent upstream -- I'd be keen on getting this in 6.x. There's still time but I'd just like a LGTM from you so I can land it quickly if needed. |
|
LGTM then. |
|
Thanks. I will hold off for a week (or whatever's closing in on 6.x) until I merge as-is. |
|
@jbergstroem ... the current plan is to cut the v6 release on Tuesday the 26th. |
|
@bnoordhuis do we carry this in node-gyp too? |
|
I guess we should for consistency: nodejs/node-gyp#908 |
|
Merging this. Was hoping for upstream but hopefully they'll catch up in time. |
jbergstroem
force-pushed
the
fix/gyp-cxx.host
branch
from
3961ffd
to
065e155
Compare
Gyp defaults to gcc/g++ if CC.host/CXX.host is unset. This is not suitable for environments that only uses the clang toolchain. Since we already assume that the user will provide clang/clang++ through CC/CXX, lean against it (then drop to gcc/g++). Also apply the same logic for link/ar for consistency although it doesn't affect us. PR-URL: nodejs#6173 Fixes: nodejs#6152 Reviewed-By: João Reis <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
|
Final CI run: https://ci.nodejs.org/job/node-test-pull-request/2375/ |
|
PPC slaves unrelated. |
jbergstroem
force-pushed
the
fix/gyp-cxx.host
branch
from
065e155
to
f1294f5
Compare
joelostrowski
pushed a commit
to joelostrowski/node
that referenced
this pull request
Apr 25, 2016
Gyp defaults to gcc/g++ if CC.host/CXX.host is unset. This is not suitable for environments that only uses the clang toolchain. Since we already assume that the user will provide clang/clang++ through CC/CXX, lean against it (then drop to gcc/g++). Also apply the same logic for link/ar for consistency although it doesn't affect us. PR-URL: nodejs#6173 Fixes: nodejs#6152 Reviewed-By: João Reis <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
jasnell
pushed a commit
that referenced
this pull request
Apr 26, 2016
Gyp defaults to gcc/g++ if CC.host/CXX.host is unset. This is not suitable for environments that only uses the clang toolchain. Since we already assume that the user will provide clang/clang++ through CC/CXX, lean against it (then drop to gcc/g++). Also apply the same logic for link/ar for consistency although it doesn't affect us. PR-URL: #6173 Fixes: #6152 Reviewed-By: João Reis <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
|
@jbergstroem is this something we would want for lts? |
|
I think -1 for LTS, who knows what crazy build environments ppl have out there that this might impact |
|
thanks @rvagg labeling as don't land |
bnoordhuis
pushed a commit
to bnoordhuis/io.js
that referenced
this pull request
Oct 8, 2016
Gyp defaults to gcc/g++ if CC.host/CXX.host is unset. This is not suitable for environments that only uses the clang toolchain. Since we already assume that the user will provide clang/clang++ through CC/CXX, lean against it (then drop to gcc/g++). Also apply the same logic for link/ar for consistency although it doesn't affect us. PR-URL: nodejs#6173 Fixes: nodejs#6152 Reviewed-By: João Reis <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
refack
pushed a commit
that referenced
this pull request
Apr 18, 2017
Gyp defaults to gcc/g++ if CC.host/CXX.host is unset. This is not suitable for environments that only uses the clang toolchain. Since we already assume that the user will provide clang/clang++ through CC/CXX, lean against it (then drop to gcc/g++). Also apply the same logic for link/ar for consistency although it doesn't affect us. PR-URL: #6173 Fixes: #6152 Reviewed-By: João Reis <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
refack
pushed a commit
to refack/node-gyp
that referenced
this pull request
Apr 23, 2017
Gyp defaults to gcc/g++ if CC.host/CXX.host is unset. This is not suitable for environments that only uses the clang toolchain. Since we already assume that the user will provide clang/clang++ through CC/CXX, lean against it (then drop to gcc/g++). PR-URL: nodejs#908 Refs: nodejs/node#6173 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Johan Bergström <[email protected]>
evanlucas
pushed a commit
that referenced
this pull request
Apr 25, 2017
Gyp defaults to gcc/g++ if CC.host/CXX.host is unset. This is not suitable for environments that only uses the clang toolchain. Since we already assume that the user will provide clang/clang++ through CC/CXX, lean against it (then drop to gcc/g++). Also apply the same logic for link/ar for consistency although it doesn't affect us. PR-URL: #6173 Fixes: #6152 Reviewed-By: João Reis <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
Merged
evanlucas
pushed a commit
that referenced
this pull request
May 1, 2017
Gyp defaults to gcc/g++ if CC.host/CXX.host is unset. This is not suitable for environments that only uses the clang toolchain. Since we already assume that the user will provide clang/clang++ through CC/CXX, lean against it (then drop to gcc/g++). Also apply the same logic for link/ar for consistency although it doesn't affect us. PR-URL: #6173 Fixes: #6152 Reviewed-By: João Reis <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
evanlucas
pushed a commit
that referenced
this pull request
May 2, 2017
Gyp defaults to gcc/g++ if CC.host/CXX.host is unset. This is not suitable for environments that only uses the clang toolchain. Since we already assume that the user will provide clang/clang++ through CC/CXX, lean against it (then drop to gcc/g++). Also apply the same logic for link/ar for consistency although it doesn't affect us. PR-URL: #6173 Fixes: #6152 Reviewed-By: João Reis <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
refack
pushed a commit
to refack/node
that referenced
this pull request
Jul 18, 2017
Gyp defaults to gcc/g++ if CC.host/CXX.host is unset. This is not suitable for environments that only uses the clang toolchain. Since we already assume that the user will provide clang/clang++ through CC/CXX, lean against it (then drop to gcc/g++). Also apply the same logic for link/ar for consistency although it doesn't affect us. PR-URL: nodejs#6173 Fixes: nodejs#6152 Reviewed-By: João Reis <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
refack
pushed a commit
to refack/node-gyp
that referenced
this pull request
Aug 19, 2017
Gyp defaults to gcc/g++ if CC.host/CXX.host is unset. This is not suitable for environments that only uses the clang toolchain. Since we already assume that the user will provide clang/clang++ through CC/CXX, lean against it (then drop to gcc/g++). PR-URL: nodejs#908 Refs: nodejs/node#6173 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Johan Bergström <[email protected]>
refack
pushed a commit
to refack/node
that referenced
this pull request
Aug 23, 2017
Gyp defaults to gcc/g++ if CC.host/CXX.host is unset. This is not suitable for environments that only uses the clang toolchain. Since we already assume that the user will provide clang/clang++ through CC/CXX, lean against it (then drop to gcc/g++). Also apply the same logic for link/ar for consistency although it doesn't affect us. PR-URL: nodejs#6173 Fixes: nodejs#6152 Reviewed-By: João Reis <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
addaleax
pushed a commit
to addaleax/ayo
that referenced
this pull request
Aug 25, 2017
Gyp defaults to gcc/g++ if CC.host/CXX.host is unset. This is not suitable for environments that only uses the clang toolchain. Since we already assume that the user will provide clang/clang++ through CC/CXX, lean against it (then drop to gcc/g++). Also apply the same logic for link/ar for consistency although it doesn't affect us. PR-URL: nodejs/node#6173 Fixes: nodejs/node#6152 Reviewed-By: João Reis <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
addaleax
pushed a commit
to ayojs/ayo
that referenced
this pull request
Aug 28, 2017
Gyp defaults to gcc/g++ if CC.host/CXX.host is unset. This is not suitable for environments that only uses the clang toolchain. Since we already assume that the user will provide clang/clang++ through CC/CXX, lean against it (then drop to gcc/g++). Also apply the same logic for link/ar for consistency although it doesn't affect us. PR-URL: nodejs/node#6173 Fixes: nodejs/node#6152 Reviewed-By: João Reis <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
MylesBorins
pushed a commit
that referenced
this pull request
Sep 10, 2017
Gyp defaults to gcc/g++ if CC.host/CXX.host is unset. This is not suitable for environments that only uses the clang toolchain. Since we already assume that the user will provide clang/clang++ through CC/CXX, lean against it (then drop to gcc/g++). Also apply the same logic for link/ar for consistency although it doesn't affect us. PR-URL: #6173 Fixes: #6152 Reviewed-By: João Reis <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
Merged
MylesBorins
pushed a commit
that referenced
this pull request
Sep 12, 2017
Gyp defaults to gcc/g++ if CC.host/CXX.host is unset. This is not suitable for environments that only uses the clang toolchain. Since we already assume that the user will provide clang/clang++ through CC/CXX, lean against it (then drop to gcc/g++). Also apply the same logic for link/ar for consistency although it doesn't affect us. PR-URL: #6173 Fixes: #6152 Reviewed-By: João Reis <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
Affected core subsystem(s)
tools/gyp
Description of change
Gyp defaults to gcc/g++ if CC.host/CXX.host is unset. This is not suitable for environments that only uses the clang toolchain.
Since we already assume that the user will provide clang/clang++ through CC/CXX, lean against it (then drop to gcc/g++).
I don't think this will be accepted upstream but I guess I should give it a try.
Refs #6088 and fixes #6152.
/cc @srl295, @bnoordhuis.