update errno.h ENOTSUP + EOVERFLOW
That would be a bug in binutils, then; you should file a bug report on their tracker.
On what basis have you chosen the values 129, and 132? Both are greater than Windows' _sys_nerr limit, and will thus produce unacceptable results, if passed to strerror(), or perror(). Consequently, I will not accept that, as a general principle, these definitions may be arbitrarily adopted.
FWIW, the recommended work-around for this issue is, in the client code, after including <errno.h>, to insert definitions such as
I needed to include the following into errno.h to be able to build a recent version of binutils:
and suggest this may be done in general.