-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
{compiler-builtins,libc} shim cleanup #44515
Conversation
Hm, seems like I should amend the new comments to reference rust-lang/rfcs#1133. WDYT? |
Using cargo features sounds fine to me! |
Sounds find to me too! But it doesn't quite work out, which this PR is really about documenting at this point |
Alright, this is ready for a real look! |
@bors: r+ |
📌 Commit d10c760 has been approved by |
☔ The latest upstream changes (presumably #43972) made this pull request unmergeable. Please resolve the merge conflicts. |
Rebased. |
@bors: r+ |
📌 Commit 509982c has been approved by |
|
@shepmaster did you mean to post that elsewhere? that file didn't change in this PR and I don't see that failure anywhere. |
It was in the CI run; but it appears someone has restarted it. Perhaps it's an unrelated thing that someone has already fixed... |
@bors: rollup |
{compiler-builtins,libc} shim cleanup ~~Depends on rust-lang/libc#764; opening early for feedback.~~ r? @alexcrichton
{compiler-builtins,libc} shim cleanup ~~Depends on rust-lang/libc#764; opening early for feedback.~~ r? @alexcrichton
Haven't come back to this yet; will see about doing that today
…On Sep 28, 2017 10:24, "Alex Crichton" ***@***.***> wrote:
@tamird <https://github.com/tamird> do you have a windows machine to test
this on locally with? Or any luck using appveyor to test this PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#44515 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABdsPJT222CGLCItfSjgvDWa33LLRBhdks5sm6w7gaJpZM4PT-Uu>
.
|
@alexcrichton I edited |
@tamird you'll also need to enable appveyor for the |
Looking at the logs there, the fact that the build script is running is actually a bug I believe, maybe try setting |
Thanks for the hint!
Not sure what to make of this, though. mtime is now None? Does that mean the file was removed? |
The bug I think is this line because with the presence of It's probably fine to just make |
We could just remove that from upstream, right? The docs at http://doc.crates.io/build-script.html state:
|
I commented on the associated PR, but to comment here as well, we want this directive when developing the compiler-builtins crate because only modifications to the build script should rerun the build script. |
Yup, thanks for your help. Done! |
@bors: r+ Ok hopefully we're good to go now! Sort of a crazy coincidence this ever worked. |
📌 Commit 138d5ad has been approved by |
⌛ Testing commit 138d5add2688f2fa5a335c6a1c7ece83d35e82af with merge 62a870877060f4779e5618e5ff8c4aa05fe67667... |
💔 Test failed - status-appveyor |
Urgh. Fixed the license.
…On Fri, Oct 6, 2017 at 8:29 PM, bors ***@***.***> wrote:
💔 Test failed - status-appveyor
<https://ci.appveyor.com/project/rust-lang/rust/build/1.0.4909>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#44515 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABdsPI4wB5HkEQ_-cFmCmaKAy1u3UjxUks5spsXOgaJpZM4PT-Uu>
.
|
@bors: r+ |
📌 Commit 7d6c3da has been approved by |
{compiler-builtins,libc} shim cleanup ~~Depends on rust-lang/libc#764; opening early for feedback.~~ r? @alexcrichton
☀️ Test successful - status-appveyor, status-travis |
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
Depends on rust-lang/libc#764; opening early for feedback.r? @alexcrichton