Closed jailbird777 closed 2 years ago
I know large PRs are frowned upon, sorry. I can try and split out the bigger pieces (socketpair, writev, etc) if that's better.
Bumping the minimum requirement from SUSv3 -> SUSv4 would let us remove the strnlen() compatibility stuff, but I believe that's the only real savings. Personally, if I ever power up one of my Tru64 machines for nostalgia purposes, I won't shed a tear if solanum won't compile as-is on it.
Opinions?
The one line in librb/configure.ac is going to merge conflict with #358 probably, but that's an easy fix.
Remove portability code for systems that don't follow at least SUSv3. This fairly closely aligns with ISO C99, which solanum already requires.