Hi,

When running a gnulib testdir on a new platform, or when finding the differences
between different versions of the same OS, one needs to review
  - either the config.cache file,
  - or the configure output.

This is relatively easy because most autoconf tests (> 95%) have the answer
"yes" for successful/good, and "no" for broken/bad.

There are a couple of autoconf tests, however, that catch the attention because
the answer is "no" for successful/good.

It would make reading of the config.cache file and of the configure output
easier if "no" meant broken/bad for _all_ tests.

There are some tests, of course, where both outcomes are good, e.g.
"checking whether // is distinct from /...". Nevertheless, it makes things
easier to be systematic when there is a clearly good and a clearly bad outcome.

Does anyone see a problem with this? Here is a proposed set of patches.


2020-07-26  Bruno Haible  <bruno@clisp.org>

	stdint, wchar, wctype-h: Change configure message.
	* m4/wint_t.m4 (gt_TYPE_WINT_T): Say "checking whether wint_t is large
	enough..." instead of "checking whether wint_t is too small...".

2020-07-26  Bruno Haible  <bruno@clisp.org>

	time_rz: Change configure message.
	* m4/time_rz.m4 (gl_TIME_RZ): Say "checking whether localtime works even
	near extrema..." instead of "checking whether localtime loops forever
	near extrema...".

2020-07-26  Bruno Haible  <bruno@clisp.org>

	stdint: Change configure message.
	* m4/stdint.m4 (gl_STDINT_H): Say "checking whether stdint.h works
	without ISO C predefines..." instead of "checking whether stdint.h
	predates C++11...".

2020-07-26  Bruno Haible  <bruno@clisp.org>

	socketlib: Change configure message.
	* m4/socketlib.m4 (gl_SOCKETLIB): Say "checking for WSAStartup..."
	instead of "checking if we need to call WSAStartup in winsock2.h and
	-lws2_32...".

2020-07-26  Bruno Haible  <bruno@clisp.org>

	include_next: Change configure message.
	* m4/include_next.m4 (gl_INCLUDE_NEXT): Say "checking whether source
	code line length is unlimited..." instead of "checking whether system
	header files limit the line length...".

2020-07-26  Bruno Haible  <bruno@clisp.org>

	getcwd: Change configure message.
	* m4/getcwd-abort-bug.m4 (gl_FUNC_GETCWD_ABORT_BUG): Say "checking
	whether getcwd succeeds when 4k < cwd_length < 16k..." instead of
	"checking whether getcwd aborts when 4k < cwd_length < 16k...".

2020-07-26  Bruno Haible  <bruno@clisp.org>

	chdir-long: Change configure message.
	* m4/chdir-long.m4 (gl_FUNC_CHDIR_LONG): Say "checking whether this
	system supports file names of any length..." instead of "checking
	whether this system has an arbitrary file name length limit...".
	Set gl_cv_have_unlimited_file_name_length instead of
	gl_cv_have_arbitrary_file_name_length_limit.
	* modules/chdir-long (Depends-on, configure.ac): Update accordingly.

2020-07-26  Bruno Haible  <bruno@clisp.org>

	ceill: Change configure message.
	* m4/ceill.m4 (gl_FUNC_CEILL): Say "checking whether ceill() works..."
	instead of "checking whether ceill() breaks with small values...".

2020-07-26  Bruno Haible  <bruno@clisp.org>

	iconv: Change configure message.
	* m4/iconv.m4 (AM_ICONV): Say "checking whether iconv is compatible
	with its POSIX signature..." instead of "checking for iconv
	declaration...". Remove K&R C support.