There are a few autoconf macros in use deemed obsolete upstream with straight forward alternatives. The autoscan tool can correct most of them, but there are two that take a little bit of code analysis. Most items are replacing AC_TRY_COMPILE with AC_COMPILE_IFELSE. Of those taking a bit more code analysis, there is the assessment by the autoconf developers that sufficient time has passed that you can assume the signal return type. In other words, it's my understanding that instead of having it return RETSIGTYPE and having autoconf determine the type, it can just be void and remove the check. The defined token seems to only occur in rsync.c and main.c. The second item is AC_C_LONG_DOUBLE which is replaced by AC_TYPE_LONG_DOUBLE and/or AC_TYPE_LONG_DOUBLE_WIDER. By their assessment, currently available compilers do indeed have long double types without needing to check for them. What may need checked is whether that long double type is wider than a double using AC_TYPE_LONG_DOUBLE_WIDER. The libs/snprintf.c file is the only one affected by the header definition currently in use.
Created attachment 11232 [details] patch consisting of autoupdate changes that do not involve evaluating code compatibility impact I've created a patch consisting of the autoupdate changes.
Thanks for digging into the autoconf code and providing a patch. I've incorporated your changes, simplified the parts related to RETSIGTYPE and "long double", and tweaked some helper scripts to handle the removed spaces in AC_INIT() (they now allow spaces or no spaces).