"G. Branden Robinson" <[email protected]> writes:
> [please keep the groff list in your replies' distribution] > > Hi Gnulib mavens, > > I happened upon a baffling bug today. > > https://savannah.gnu.org/bugs/?68552 > > Long story short is the question in the Subject:. > > If Gnulib doesn't--I checked its module list[1] and grepped the lib/ > directory housing Gnulib functions in an affected build and saw no > evidence that it does--then I may have to risk the exciting political > gambit of throwing shade on a compiler vendor or a distribution. No, we don't replace exit. If we did it would be documented here [1]. The only thing we document there is defining EXIT_SUCCESS and EXIT_FAILURE on systems that forgot to. I guess we also work around a Tandem quirk, too, which isn't documented: /* Tandem/NSK and other platforms that define EXIT_FAILURE as -1 interfere with proper operation of xargs. */ #ifndef EXIT_FAILURE # define EXIT_FAILURE 1 #elif EXIT_FAILURE != 1 # undef EXIT_FAILURE # define EXIT_FAILURE 1 #endif I don't have access to that platform, though, so I can't even verify that comment. I think a lot of us have thrown shade at certain vendors. I don't feel too bad doing it to non-free platforms. E.g., I complain about Solaris every once and a while, and I remember Bruno not having a good time with macOS's patches which botched FreeBSD's libiconv [2]. :) Collin [1] https://www.gnu.org/software/gnulib/manual/html_node/exit.html [2] https://lists.gnu.org/archive/html/bug-gnulib/2024-05/msg00375.html
