Follow-up Comment #2, sr #111333 (group autoconf): To elaborate on "not conveniently", this _is_ something that we would like to fix in the long run. WASM is not the only environment that has started complaining about this extremely old-school code, and I expect it to become more of a problem as more compilers adopt C2024 (in which 'extern char strnlen ()' arguably ought to provoke a hard error from the _compiler_, not just the linker, whether or not <string.h> has been included).
However, the only plausible way to fix it is for Autoconf to have a giant
table listing, for each function that AC_CHECK_FUNC is likely to be asked to
check for, the header that is supposed to declare it, and the expected
prototype. At a minimum this table should should cover all of ISO C and all
of POSIX, including functions that _used_ to be in either standard but have
been removed. You can probably imagine how much work this would be, and none
of the core Autoconf maintainers have the time to tackle it in the near
future.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?111333>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
