Eric Blake wrote: > On 11/19/2012 04:26 PM, matimatik wrote: >> I cannot find #define for HAVE_RAW_DECL_GETS in it (moreover, >> 'grep -R HAVE_RAW_DECL_GETS .' in workdir doesn't show anything >> relevant). But it does contain GNULIB_GETS='1'. > > GNULIB_GETS doesn't appear anywhere in current gnulib sources. Is your > package using the latest gnulib? [This wouldn't be the first time > someone has complained that a package suffers from FTBFS when coupled > with newer glibc, because the package was released with an older gnulib > snapshot]
What do you guys think about a gnulib-tool-time warning (or perhaps even a configure-time warning for a non-tarball build) when gnulib is more than N days out of date? Or maybe when the current version of glibc is newer than the one that was current for "this" version of gnulib. At the minimum, configure output could warn that gnulib is N days old when N > some_threshold.
