Incidencia #40848

update errno.h ENOTSUP + EOVERFLOW

Abrir Fecha: 2020-10-09 06:51 Última actualización: 2020-10-10 05:08

Informador:
Propietario:
(Ninguno)
Tipo:
Estado:
Cerrado
Componente:
(Ninguno)
Hito:
(Ninguno)
Prioridad:
5 - Medium
Gravedad:
5 - Medium
Resolución:
Rejected
Fichero:
Ninguno
Vote
Score: 0
No votes
0.0% (0/0)
0.0% (0/0)

Details

I needed to include the following into errno.h to be able to build a recent version of binutils:

  1. /* necessary to build recent binutils: */
  2. #define ENOTSUP 129
  3. #define EOVERFLOW 132

and suggest this may be done in general.

Ticket History (2/2 Histories)

2020-10-09 06:51 Updated by: osdn-mensch
  • New Ticket "update errno.h ENOTSUP + EOVERFLOW" created
2020-10-10 05:08 Updated by: keith
  • Estado Update from Open to Cerrado
  • Resolución Update from Ninguno to Rejected
Comentario

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

  1. #ifndef ENOTSUP
  2. #define ENOTSUP ENOSYS
  3. #endif
  4. #ifndef EOVERFLOW
  5. #define EOVERFLOW ERANGE
  6. #endif

Attachment File List

No attachments

Editar

Please login to add comment to this ticket » Entrar