* Common Behavior:: Macros' standard schemes
* Alternative Programs:: Selecting between alternative programs
+* Files:: Checking for the existence of files
* Libraries:: Library archives that might be missing
* Library Functions:: C library functions that might be missing
* Header Files:: Header files that might be missing
@menu
* Common Behavior:: Macros' standard schemes
* Alternative Programs:: Selecting between alternative programs
+* Files:: Checking for the existence of files
* Libraries:: Library archives that might be missing
* Library Functions:: C library functions that might be missing
* Header Files:: Header files that might be missing
exist, but conflict. Then @code{HAVE_STRING_H} will be defined, but
@code{HAVE_STRINGS_H} won't.
-@node Alternative Programs, Libraries, Common Behavior, Existing Tests
+@node Alternative Programs, Files, Common Behavior, Existing Tests
@section Alternative Programs
@cindex Programs, checking
@end defmac
-@c FIXME: Not the proper place for these guys.
+@node Files, Libraries, Alternative Programs, Existing Tests
+@section Files
+@cindex File, checking
You might also need to check for the existence of files. Before using
these macros, ask yourself whether a run time test might not be a better
@end defmac
-@node Libraries, Library Functions, Alternative Programs, Existing Tests
+@node Libraries, Library Functions, Files, Existing Tests
@section Library Files
@cindex Library, checking