> So first - in my opinion, if you apply your logic this strictly, NuttX is already very much non-compliant. For example - one of the interfaces POSIX mandates is a sigprocmask system call, correct? My compiled NuttX binary (with full signal support enabled) does not have that system call. It is, therefore, non-compliant.
POSIX standardizes the OS interface (API), not the resulting binary. Whether your binary is POSIX compatible is not a matter of NuttX, but of your configuration. The standard applies to source code, not compilation results wt., 5 maj 2026 o 11:26 <[email protected]> napisał(a): > > Remember that the range of time_t has to support the epoch as the > > minimum (zero) value. Now is the running time plus the epoch > > (CLOCK_REALTIME). > > Unless it is - from the toaster's (or washing machine's) point of view - > year 1970. Such a device is most likely not even going to provide a way > to set real time. >
