-
Notifications
You must be signed in to change notification settings - Fork 13.4k
MAKEFLAGS and nmake.exe with Cargo conflict #42635
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Labels
I-needs-decision
Issue: In need of a decision.
P-high
High priority
regression-from-stable-to-beta
Performance or correctness regression from stable to beta.
T-cargo
Relevant to the cargo team, which will review and decide on the PR/issue.
Comments
AFAICT this will affect most every Rust project building on Windows. I've seen this many times. |
bors
added a commit
to rust-lang/cargo
that referenced
this issue
Jul 12, 2017
Don't set MAKEFLAGS for build scripts Closes #4156 Closes rust-lang/rust#42635
alexcrichton
added a commit
to alexcrichton/cargo
that referenced
this issue
Jul 12, 2017
Looks like this hasn't been backported into rust yet. |
bors
added a commit
to rust-lang/cargo
that referenced
this issue
Jul 13, 2017
[beta] Don't set MAKEFLAGS for build scripts Closes #4156 Closes rust-lang/rust#42635
Should be fixed on current beta 4. Anybody confirm? |
bors
added a commit
that referenced
this issue
Jul 15, 2017
Update the `cargo` submodule Notably pull in an update to the `jobserver` crate to have Cargo set the `CARGO_MAKEFLAGS` environment variable instead of the `MAKEFLAGS` environment variable. cc #42635
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
I-needs-decision
Issue: In need of a decision.
P-high
High priority
regression-from-stable-to-beta
Performance or correctness regression from stable to beta.
T-cargo
Relevant to the cargo team, which will review and decide on the PR/issue.
I'm filing this issue for tracking purposes but discussion should continue on rust-lang/cargo#4156 (comment) instead, just using this for labels so we don't forget it.
The text was updated successfully, but these errors were encountered: