Including <cerrno> instead of <errno.h>, does it upset POSIX?

[Ahmad Samir]

On 21/04/2021 15:20, Harald Sitter wrote:
> To conclude this our verdict is to always use the modern headers?
> 

I am re-checking the rest of the frameworks that failed the first time around; Albert already 
reported that it built for him locally with '#include <cerrno>'; I'll test again, push the changes 
and if the CI doesn't barf on any of it, then my conclusion is it's OK so far.

-- 
Ahmad Samir