autoconf: Existing Tests

1 
1 5 Existing Tests
1 ****************
1 
1 These macros test for particular system features that packages might
1 need or want to use.  If you need to test for a kind of feature that
1 none of these macros check for, you can probably do it by calling
11 primitive test macros with appropriate arguments (⇒Writing
 Tests).
1 
1    These tests print messages telling the user which feature they're
1 checking for, and what they find.  They cache their results for future
1 `configure' runs (⇒Caching Results).
1 
11    Some of these macros set output variables.  ⇒Makefile
 Substitutions, for how to get their values.  The phrase "define NAME"
1 is used below as a shorthand to mean "define the C preprocessor symbol
1 NAME to the value 1".  ⇒Defining Symbols, for how to get those
1 symbol definitions into your program.
1 

Menu

1 
· 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
· Declarations                Declarations that may be missing
· Structures                  Structures or members that might be missing
· Types                       Types that might be missing
· Compilers and Preprocessors  Checking for compiling programs
· System Services             Operating system services
· Posix Variants              Special kludges for specific Posix variants
· Erlang Libraries            Checking for the existence of Erlang libraries
1