Re: errno --> errno name ?

[Bruno Haible]

Hi Bruce,

> I fixed up the "mk" script to be more portable

Indeed, that looks like most portability problems have been eliminated.

> tho I haven't tried it on Solaris' /bin/sh.
> Probably won't work.  I don't have access.

You can also test it with 'zsh', 'ksh', 'ash', and 'dash' on a glibc system.
If it works with these shells, it will likely also pass with /bin/sh on
various systems.

Now, do you plan to convert this into a gnulib module?

> One interesting thing I discovered:
> 
> $ errno . | head -n4 ; echo '[...]';errno . | tail -n4
> looking for matches to:  '.'
>      1 (EPERM. . . . . ) == Operation not permitted
>      2 (ENOENT . . . . ) == No such file or directory
>      3 (ESRCH. . . . . ) == No such process
> [...]
>    130 (EOWNERDEAD . . ) == Owner died
>    131 (ENOTRECOVERABLE) == State not recoverable
>    132 (ERFKILL. . . . ) == Unknown error 132

It just means that your libc does not have the string for ERFKILL. This
string was added in glibc/sysdeps/gnu/errlist.c on 2009-11-14.

Bruno