fix: compatiblity with next libc release - #2821
Draft
xtqqczze wants to merge 3 commits into
Draft
Conversation
asomers
reviewed
Sep 8, 2026
| path = "test/sys/test_prctl.rs" | ||
|
|
||
| [patch.crates-io] | ||
| libc = { git = "https://github.com/rust-lang/libc", branch = "libc-0.2" } |
Member
There was a problem hiding this comment.
I know that this PR isn't ready to merge yet, but please ensure that when it is, you patch to a specific revision of libc-0.2, not a branch.
Contributor
Author
There was a problem hiding this comment.
When it is ready to merge, the patch will be removed.
Contributor
Author
|
@asomers Unfortunately, given the current state of CI, I’m not particularly motivated to spend more time on this right now. That said, I don’t think it’s a good situation for For an idea of the type of changes that may be required, see the corresponding PR in |
needed to fix semicolon_in_expressions_from_macros error in minver
```log
error: trailing semicolon in macro used in expression position
--> build.rs:4:5
|
4 | / cfg_aliases! {
5 | | android: { target_os = "android" },
6 | | dragonfly: { target_os = "dragonfly" },
7 | | ios: { target_os = "ios" },
... |
27 | | solarish: { any(illumos, solaris) },
28 | | }
| |_____^
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #79813 <rust-lang/rust#79813>
= note: `#[deny(semicolon_in_expressions_from_macros)]` (part of `#[deny(future_incompatible)]`) on by default
= note: this error originates in the macro `$crate::cfg_aliases` which comes from the expansion of the macro `cfg_aliases` (in Nightly builds, run with -Z macro-backtrace for more info)
```
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.