configure output from largefile.m4

[Bruno Haible]

Hi Paul,

In a configure output I see:

  checking for -I/Users/runner/include -I/usr/local/opt/libiconv/include -Wall 
-DCONTINUE_AFTER_ASSERT option for large files... none needed
  checking for -I/Users/runner/include -I/usr/local/opt/libiconv/include -Wall 
-DCONTINUE_AFTER_ASSERT option for timestamps after 2038... none needed

It comes from largefile.m4:

  AC_CACHE_CHECK([for $CPPFLAGS option for large files],

and

  AC_CACHE_CHECK([for $CPPFLAGS option for timestamps after 2038],

Printing the CPPFLAGS makes no sense to me. I understand that for
some configure tests, we write

  checking for gcc option ... ...

but since in this case the options are independent of the compiler
and even independent of C vs. C++ mode, it would be adequate to print

  checking for compiler option for large files... none needed
  checking for compiler option for timestamps after 2038... none needed

Right?

Also, as mentioned in [1], I find the wording
  option to enable large file support
more understandable than
  option for large files

Bruno

[1] https://lists.gnu.org/archive/html/bug-gnulib/2024-04/msg00420.html