"Bruno Haible" <[EMAIL PROTECTED]> writes: > I was assuming that invoking AC_SYS_LARGEFILE is the programmer's > responsibility, because AC_SYS_LARGEFILE is a global switch.
Yes, that was my assumption too. However, as you mentioned, any portable program that accesses files should use AC_SYS_LARGEFILE these days. > The affected modules are not only clean-temp, but at least: > mkstemp > tempname > copy-file > clean-temp mkstemp and tempname already invoke AC_SYS_LARGEFILE, so there's precedent for having copy-file and clean-temp do it as well. > Paul, what do you think? Is it gnulib's or the configure.ac's responsibility > to use AC_SYS_LARGEFILE? I'd say that ultimately it's configure.ac's responsibility, but gnulib modules can require AC_SYS_LARGEFILE as a matter of convenience and/or documentation. Admittedly this is wishy-washy, but it does describe common practice.
