www.delorie.com/gnu/docs/autoconf/autoconf_35.html

search

	Buy the book!

Autoconf

5. Existing Tests

These macros test for particular system features that packages might need or want to use. If you need to test for a kind of feature that none of these macros check for, you can probably do it by calling primitive test macros with appropriate arguments (see section 6. Writing Tests).

These tests print messages telling the user which feature they're checking for, and what they find. They cache their results for future configure runs (see section 7.3 Caching Results).

Some of these macros set output variables. See section 4.7 Substitutions in Makefiles, for how to get their values. The phrase "define name" is used below as a shorthand to mean "define C preprocessor symbol name to the value 1". See section 7.1 Defining C Preprocessor Symbols, for how to get those symbol definitions into your program.

5.1 Common Behavior		Macros' standard schemes
5.2 Alternative Programs		Selecting between alternative programs
5.3 Files		Checking for the existence of files
5.4 Library Files		Library archives that might be missing
5.5 Library Functions		C library functions that might be missing
5.6 Header Files		Header files that might be missing
5.7 Declarations		Declarations that may be missing
5.8 Structures		Structures or members that might be missing
5.9 Types		Types that might be missing
5.10 Compilers and Preprocessors		Checking for compiling programs
5.11 System Services		Operating system services
5.12 UNIX Variants		Special kludges for specific UNIX variants