Eli Zaretskii wrote:
Gnulib decides to generate its own alloca.h header even though there's a system header alloca.h (and HAVE_ALLOCA_H is 1 in config.h). Why does it do that? Isn't that dangerous? e.g., it could conflict with how the system header defies 'alloca', no?
This stuff is rickety, as it's built atop Autoconf's AC_FUNC_ALLOCA and that stuff hasn't changed in at least a decade. In the old days, some alloca implementations were broken and when in doubt it was better to replace the system alloca than to use it. Nowadays I doubt whether it matters much. In any event Autoconf and/or Gnulib patches to be more cautious about replacing alloca.h would be welcome.
