Bruno Haible <[EMAIL PROTECTED]> wrote: ... >> A more conservative approach would be to make each of those >> proposed-obsolete module AC_REQUIRE a new macro with code to run at >> configure-time if ever the module is required. That code could make >> configure fail by default with a diagnostic > > This approach would be good if we did not know about the possible portability > problems. But our database in doc/* tells us. > > The functions we are talking about were apparently all part of ANSI C, and > added by vendors in the years 1992-1994, in the scope of ANSI C compliance.
Here's a proposal you might prefer. Go ahead and declare these modules "obsolescent", but rather than ripping out all dependencies on them, add an option to gnulib-tool (say, --ignore-obsolescent) to tell it to do ignore any dependency on an obsolescent module.
