Re: Meaning of sys_nerr (and porting programs)

[Thomas Bushnell, BSG]

Wolfgang Jährling <wolfgang@pro-linux.de> writes:

> It allocates an array of sys_nerr elements (the sys_nerr in glibc on
> GNU/Hurd is 119) and tries to store an object for each E* constant in
> one of those elements, but uses the actual value of the constant as
> offset. However, it doesn't crash while doing this on GNU/Hurd, because
> it checks if the number is smaller or equal to sys_nerr and if it is
> not, it simply does not copy it into the array.

sys_nerr shouldn't be defined at all on the Hurd, if I understand the
situation correctly.  Roland, can you comment?

> Programs might (and in fact do) assume that sys_nerr is the biggest
> numeric value of any errno constant, which is not the case on GNU/Hurd.

Quite right they can assume that.  sys_nerr doesn't make any sense on
the Hurd.