Skip to content
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

rustc_back: Don't pass 'u' to ar invocations #25411

Merged
merged 1 commit into from
May 26, 2015

Conversation

alexcrichton
Copy link
Member

This flag indicates that when files are being replaced or added to archives (the
r flag) that the new file should not be inserted if it is not newer than the
file that already exists in the archive. The compiler never actually has a use
case of not wanting to insert a file because it already exists, and this
causes rlibs to not be updated in some cases when the compiler was re-run too
quickly.

Closes #18913

@rust-highfive
Copy link
Collaborator

r? @Aatch

(rust_highfive has picked a reviewer for you, use r? to override)

@alexcrichton
Copy link
Member Author

r? @brson

This will tangentially fix the MUSL builds on the bots right now.

@rust-highfive rust-highfive assigned brson and unassigned Aatch May 14, 2015
@brson
Copy link
Contributor

brson commented May 19, 2015

@bors r+

@bors
Copy link
Contributor

bors commented May 19, 2015

📌 Commit ae13436 has been approved by brson

@bors
Copy link
Contributor

bors commented May 20, 2015

☔ The latest upstream changes (presumably #25350) made this pull request unmergeable. Please resolve the merge conflicts.

@bors
Copy link
Contributor

bors commented May 21, 2015

🔒 Merge conflict

This flag indicates that when files are being replaced or added to archives (the
`r` flag) that the new file should not be inserted if it is not newer than the
file that already exists in the archive. The compiler never actually has a use
case of *not* wanting to insert a file because it already exists, and this
causes rlibs to not be updated in some cases when the compiler was re-run too
quickly.

Closes rust-lang#18913
@alexcrichton
Copy link
Member Author

@bors: r=brson fa0834d

@bors
Copy link
Contributor

bors commented May 26, 2015

⌛ Testing commit fa0834d with merge a83201f...

bors added a commit that referenced this pull request May 26, 2015
This flag indicates that when files are being replaced or added to archives (the
`r` flag) that the new file should not be inserted if it is not newer than the
file that already exists in the archive. The compiler never actually has a use
case of *not* wanting to insert a file because it already exists, and this
causes rlibs to not be updated in some cases when the compiler was re-run too
quickly.

Closes #18913
@bors bors merged commit fa0834d into rust-lang:master May 26, 2015
@alexcrichton alexcrichton deleted the issue-18913 branch July 17, 2015 18:46
bors added a commit to rust-lang/cargo that referenced this pull request Oct 10, 2017
cargo_rustc: remove workaround for fixed upstream issue

Fixed in rust-lang/rust#25411. Also, the
removed code is implicated in test failures observed in
rust-lang/rust#44515.

r? @alexcrichton
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Compiler doesn't actually write output if rerun quickly
5 participants