uclibc: Don't specialize PTRACE_O_MASK for uclibc
This constant comes from the kernel headers, so its value should not depend on the libc type.
To test: see instructions in https://github.com/rust-lang/libc/pull/2566
define TIOCGWINSZ as c_ulong under arm-uclibc.
I'm trying to bring up a new target for rust, `armv7-unknown-linux-uclibceabi (softfloat)`. https://github.com/rust-lang/rust/pull/92383 Looks like a lot of work has already been hashed out from the recent addition of `armv7-unknown-linux-uclibceabihf`. The only issue I'm currently seeing is when I encounter `TIOCGWINSZ` in a couple places. This is the error I see.
```
Compiling termize v0.1.1 (/mmc/.cargo/registry/src/github.com-1285ae84e5963aae/termize-0.1.1)
error[E0277]: the trait bound `u32: From<i32>` is not satisfied
--> src/platform/unix.rs:12:43
|
12 | let mut result = ioctl(STDOUT_FILENO, TIOCGWINSZ.into(), &mut window);
| ----- ^^^^^^^^^^^^^^^^^ the trait `From<i32>` is not implemented for `u32`
| |
| required by a bound introduced by this call
|
= help: the following implementations were found:
<u32 as From<Ipv4Addr>>
<u32 as From<NonZeroU32>>
<u32 as From<bool>>
<u32 as From<char>>
and 2 others
= note: required because of the requirements on the impl of `Into<u32>` for `i32`
error[E0277]: the trait bound `u32: From<i32>` is not satisfied
```
I see the error in the `termize` crate, and also `shell.rs` in the cargo source.
My current fix is to define TIOCGWINSZ as c_ulong under arm-uclibc.
I don't want to break anything with the established `armv7-unknown-linux-uclibceabihf` target so perhaps `@skrap` could chime in and take a look. Maybe a better solutions exists.
Fix definitions for the s390x-musl target.
When I was creating the original s390x musl definitions, I copied a little too closely from glibc for the ioctl(2) constants. This was then exacerbated in c7c238d812 with the creation of an erroneous definition.
On musl, these constants must be ints, not ulongs. On glibc, they are
ulong, and as such, were erroneously included as ulongs in the initial
s390x-musl definitions.
ioctl(2) always takes an int as the request, not a ulong, on musl.
I copied a little too closely from the glibc definitions when creating
the original s390x-musl ones.
apple IP{,V6}_DONTFRAG constants
These are new in macOS Big Sur, but I'm not sure if we're supposed to have any `cfg` incantations that can restrict to that version (I reviewed `cfg` instances in both `apple` and `linux_like` but didn't see anything like that).
