Sebastien Marie

from OpenBSD point of vue, it LGTM.

@locriacyber, [openbsd-ziglibc](https://github.com/semarie/openbsd-ziglibc) is getting real libc and headers files. I think what is expected here is to get only functions stubs.

to build C program (using zig compiler), you need both (libc stubs and header files). to build ZIG program (using zig compiler), you need only libc stubs (assuming no C...

just for reference, at some point I was able to cross compile from Linux (I have not check if it is still working). see https://github.com/semarie/openbsd-ziglibc it is a shell script...

I think it isn't just a "version compatibility" issue. My purpose isn't to have a compatibility layer for missing/removed functions or types. The problem is OpenBSD triple is versioned, meaning...

I hope you are kidding: you are asking to remove `siginfo_t` type for OpenBSD from libc and so to break stack_overflow detection for OpenBSD (libstd relies on it). And even...

@alexcrichton I pushed a WIP branch on my github repository. I hope code will be more explicity than my explaination about what I called having support for OS version. Tree...

@asomers OpenBSD uses ELF on all platforms. but using ELF symbol versioning doesn't help for breaking changes if the OS doesn't use symbol versioning.

@comex yes, the change `char *` to `void *` is just an API break regarding OpenBSD. But it is an uncommitable change in crate libc without major version bump. I...

@mattmacy my understanding of the problem is: - build time configuration adds more complexity for crosscompiling (you need to target a particular OS ABI) - crosscompiling is used a lot...