-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
FreeBSD 10.x is EOL, in FreeBSD 11 and later, ss_sp is actually a void* #57810
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @shepmaster (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
I think this is blocked on rust-lang/libc#1222, so marking as such |
fix stack_t on FreeBSD FreeBSD 10.x is EOL, in FreeBSD 11 and later, ss_sp is actually a void* [1] dragonflybsd still uses c_char [2] [1] https://svnweb.freebsd.org/base/releng/11.2/sys/sys/signal.h?revision=334459&view=markup#l438 [2] https://github.com/DragonFlyBSD/DragonFlyBSD/blob/master/sys/sys/signal.h#L339 should be committed with rust-lang/rust#57810
@MikaelUrankar I've released libc 0.2.48 containing the breaking change committed in rust-lang/libc#1222 , would you mind updating the libc version of rust in this PR to 0.2.48 as well ? |
I don't know how to do that. Is it enough to bump the libc version in src/libstd/Cargo.toml or am I missing something ? |
Pretty much - I am not sure if this is the only Once you do this, the For the commit you need to commit both the modified |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
So it appears that something in the |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
I'm a bit at a loss here, what needs to be updated? FWIW I can build rust locally with these changes. |
This may be a merge conflict with master, I'd recommend rebasing and re-running |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
93 commits, 148 files changed? where do they come from? |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
rust-lang/libc#1222 has been merged so it should no longer be S-blocked. |
r? @nagisa |
@bors r+ the changes here look fine to me. @gnzlbg @alexcrichton why are libc versions not following semver and introducing breaking changes with patch-level versions? |
@MikaelUrankar This PR introduced several new transitive dependencies to rustc:
These must be manually added to a whitelist to pass the tidy check. Or maybe find a way to avoid introducing these dependencies. rust/src/tools/tidy/src/deps.rs Lines 51 to 60 in 52e8856
|
@kennytm @MikaelUrankar this PR upgrades all crates in |
I did the same change in |
Is it OK now? |
@bors r+
Yeah it is good, thanks!
…On Sun, Mar 17, 2019, 15:19 MikaelUrankar ***@***.***> wrote:
Is it OK now?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#57810 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AApc0tstbDn5nDLz3itCh8PDBtDUXITBks5vXkD1gaJpZM4aLS8g>
.
|
📌 Commit dce4b35ccba68083e040759d469bc0f0d276c4d5 has been approved by |
🔒 Merge conflict This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again. How do I rebase?Assuming
You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial. Please avoid the "Resolve conflicts" button on GitHub. It uses Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Error message
|
☔ The latest upstream changes (presumably #59279) made this pull request unmergeable. Please resolve the merge conflicts. |
…d* [1] dragonflybsd still uses c_char [2] [1] https://svnweb.freebsd.org/base/releng/11.2/sys/sys/signal.h?revision=334459&view=markup#l438 [2] https://github.com/DragonFlyBSD/DragonFlyBSD/blob/master/sys/sys/signal.h#L339
Can it be merged quickly? |
@MikaelUrankar It has to be approved again. Then go through bors queue: https://buildbot2.rust-lang.org/homu/queue/rust |
@bors r+ |
📌 Commit 6b766ba has been approved by |
FreeBSD 10.x is EOL, in FreeBSD 11 and later, ss_sp is actually a void* …d* [1] dragonflybsd still uses c_char [2] [1] https://svnweb.freebsd.org/base/releng/11.2/sys/sys/signal.h?revision=334459&view=markup#l438 [2] https://github.com/DragonFlyBSD/DragonFlyBSD/blob/master/sys/sys/signal.h#L339
FreeBSD 10.x is EOL, in FreeBSD 11 and later, ss_sp is actually a void* …d* [1] dragonflybsd still uses c_char [2] [1] https://svnweb.freebsd.org/base/releng/11.2/sys/sys/signal.h?revision=334459&view=markup#l438 [2] https://github.com/DragonFlyBSD/DragonFlyBSD/blob/master/sys/sys/signal.h#L339
☀️ Test successful - checks-travis, status-appveyor |
…d* [1]
dragonflybsd still uses c_char [2]
[1] https://svnweb.freebsd.org/base/releng/11.2/sys/sys/signal.h?revision=334459&view=markup#l438
[2] https://github.com/DragonFlyBSD/DragonFlyBSD/blob/master/sys/sys/signal.h#L339