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

Add SIGRTMAX and SIGRTMIN on linux-like systems #2304

Merged
merged 2 commits into from
Jul 30, 2021
Merged

Conversation

mkroening
Copy link
Contributor

@mkroening mkroening commented Jul 28, 2021

Fixes #1883. This is based on #2195, which has not seen activity in a while.

The original issue was resolved by making __libc_current_sigrtmax and __libc_current_sigrtmax pub.

I also added a test similar to errqueue's, where the actual value of the macro is compared to libc's implementation.

Closes #2195

@rust-highfive
Copy link

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @JohnTitor (or someone else) soon.

Please see the contribution instructions for more information.

src/unix/linux_like/mod.rs Outdated Show resolved Hide resolved
src/unix/linux_like/mod.rs Outdated Show resolved Hide resolved
@JohnTitor
Copy link
Member

Thanks!
@bors r+

@bors
Copy link
Contributor

bors commented Jul 29, 2021

📌 Commit 91dd411 has been approved by JohnTitor

@bors
Copy link
Contributor

bors commented Jul 29, 2021

⌛ Testing commit 91dd411 with merge d097de4...

bors added a commit that referenced this pull request Jul 29, 2021
Add SIGRTMAX and SIGRTMIN on linux-like systems

Fixes #1883. This is based on #2195, which has not seen activity in a while.

The original issue was resolved by making `__libc_current_sigrtmax` and `__libc_current_sigrtmax` `pub`.

I also added a test similar to `errqueue`'s, where the actual value of the macro is compared to `libc`'s implementation.

Closes #2195
@mkroening
Copy link
Contributor Author

Looks like the constness is not allowed here, since we call __libc_current_sigrtmax.

Should I remove the constness again?

@bors
Copy link
Contributor

bors commented Jul 29, 2021

💔 Test failed - checks-actions

@JohnTitor
Copy link
Member

Ah yes! I forgot that __libc_*s weren't consts.

@mkroening
Copy link
Contributor Author

Done. 👍

@JohnTitor
Copy link
Member

@bors r+

@bors
Copy link
Contributor

bors commented Jul 29, 2021

📌 Commit 8af1a48 has been approved by JohnTitor

@bors
Copy link
Contributor

bors commented Jul 29, 2021

⌛ Testing commit 8af1a48 with merge f46d5b3...

bors added a commit that referenced this pull request Jul 29, 2021
Add SIGRTMAX and SIGRTMIN on linux-like systems

Fixes #1883. This is based on #2195, which has not seen activity in a while.

The original issue was resolved by making `__libc_current_sigrtmax` and `__libc_current_sigrtmax` `pub`.

I also added a test similar to `errqueue`'s, where the actual value of the macro is compared to `libc`'s implementation.

Closes #2195
@bors
Copy link
Contributor

bors commented Jul 29, 2021

💔 Test failed - checks-actions

@JohnTitor
Copy link
Member

@bors retry

@bors
Copy link
Contributor

bors commented Jul 29, 2021

⌛ Testing commit 8af1a48 with merge 80e4a26...

@bors
Copy link
Contributor

bors commented Jul 30, 2021

☀️ Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13
Approved by: JohnTitor
Pushing 80e4a26 to master...

@bors bors merged commit 80e4a26 into rust-lang:master Jul 30, 2021
@mkroening mkroening deleted the sigrt branch June 29, 2023 12:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

libc expose SIGRTMIN and SIGRTMAX
5 participants