fix: add uclibc MIPS signal flags compatibility #2671
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.
I open this PR to fix signal handling compatibility for MIPS uclibc systems by addressing type mismatches in
sa_flags
.MIPS uclibc (version 0.9.x series that can be found on some embedded devices) defines
sa_flags
asunsigned int
instead of the standardint
, causing compilation failures when building nix on these systems.Changes
src/sys/signal.rs
to uselibc::c_uint
forSaFlags_t
type on MIPS with uclibclibc_bitflags!
macro for MIPS uclibc compatibilityTesting
src/sys/statfs.rs
uclibc handling)Note: No API changes, this is purely a compatibility fix for existing signal handling functionality. The public
API remains identical on all platforms.