libc
libc copied to clipboard
rust-lang
Raw bindings to platform APIs for Rust
use ulong type uniformly.
I don't understand why these constants from Linux headers aren't just defined in linux_like/mod.rs. Surely they'd be the same for every libc?
#3408 introduced new constants for the fanotify linux API. Among those constants, some are used to request additional data, which are formatted according to several C structs that are defined...
Greetings, I may have found a small set of constants whose values were included in [libc](https://github.com/rust-lang/libc) as decimal literals while in fact they were written as octal literals in C....
will be still used for a while.
Fix newlib
So i found several incorrect definitions in the newlib module. ~~I cannot trace these values to anything except #646 which was done for devkitpro, yet definitions there don't seem to...
Move common Linux ptrace definitions to linux_like/mod.rs.
docs: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue It should be achieved by running bors CI on `merge_group` event. IIRC bors doesn't support a multi-release branches strategy, so we have to migrate to the merge queue...
The `get`/`setpwent` functions are not available on the aarch64-linux-android target, however libc on this platform (at least on my phone) does have this symbol in the libc library. I'm happy...
