stty, glibc 2.42: panicked at termios.rs called Result::unwrap() on an Err value: EINVAL

[oech3]

> uu-stty

thread 'main' panicked at /tmp/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/nix-0.30.1/src/sys/termios.rs:767:70:
called `Result::unwrap()` on an `Err` value: EINVAL
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

This was not happening previously, and does not happen at prebuilt of 0.1.0 from here.
So I think this is related with system runtimes. Multicall build or not is unrelated.

Arch Linux
Version: 0.1.0 (self build, bumping commit to latest does not solve this issue).
gcc (GCC) 15.1.1
rustc 1.89.0

[julian-klode]

Forwarded to nix-rust/nix#2672

[julian-klode]

In Ubuntu I worked around this by diverting nix and stty crates to the BSD variants as glibc now adopted the BSD semantics:

https://git.launchpad.net/~juliank/ubuntu/+source/rust-coreutils/tree/debian/patches/glibc-2.42.patch?h=ubuntu/devel&id=a16e77bec0546ee51770a891a24468e8048242e3

This of course is not upstreamable, that's for the nix crate people to sort out

[oech3]

I tried to make a small linker script which might upstreamable, but it did not work.

[oech3]

From nix-rust/nix#2672 (comment)

If they are equal to their numeric value, then the translation is trivial (for Linux, B300 == 300 is enough of a test.)

@naoNao89 Can we use the workaound at here without panic?

[naoNao89]

i will take it