Re: EX_OK collision

[Paul Eggert]

Simon Josefsson <address@hidden> writes:

> Possibly the bug-workaround for unistd.h should only be enabled if the
> sysexits module is present, otherwise the unistd-module would always
> touch non-standardized namespaces which seems wrong.

I agree.  I'd rather not use the sysexits module, which means I'd
rather not have the unistd module messing with EX_OK (for example,
lib/euidaccess.c or similar code may need the system unistd.h EX_OK).

> e) Create a replacement <unistd.h> that does:
>
>    #include </usr/include/unistd.h>
>    #if @GNULIB_SYSEXITS@
>    #  undef EX_OK
>    #endif

That doesn't look right, since code would have to include unistd.h
before sysexits.h.

How about (b)?  It seems the simplest.

>   (b) Create a replacement <sysexits.h> that does
>
>          #include <unistd.h>
>          #undef EX_OK
>          #include </usr/include/sysexits.h>