These macros are used to find programs not covered by the particular
test macros. If you need to check the behavior of a program as well as
find out whether it is present, you have to write your own test for it
(see section Writing Tests). By default, these macros use the environment
PATH. If you need to check for a program that might not
be in the user's
PATH, you can pass a modified path to use
instead, like this:
AC_PATH_PROG(INETD, inetd, /usr/libexec/inetd, $PATH:/usr/libexec:/usr/sbin:/usr/etc:etc)
AC_CHECK_FILEonce for each file listed in files. Additionally, defines `HAVEfile' for each file found, set to 1.
PATH. If it is found, set variable to value-if-found, otherwise to value-if-not-found, if given. Always pass over reject (an absolute file name) even if it is the first found in the search path; in that case, set variable using the absolute file name of the prog-to-check-for found that is not reject. If variable was already set, do nothing. Calls
PATH. If it is found, set variable to the name of that program. Otherwise, continue checking the next program in the list. If none of the programs in the list are found, set variable to value-if-not-found; if value-if-not-found is not specified, the value of variable is not changed. Calls
AC_CHECK_PROG, but first looks for prog-to-check-for with a prefix of the host type as determined by
AC_CANONICAL_HOST, followed by a dash (see section Getting the Canonical System Type). For example, if the user runs `configure --host=i386-gnu', then this call:
AC_CHECK_TOOL(RANLIB, ranlib, :)
RANLIB to `i386-gnu-ranlib' if that program exists in
PATH, or to `ranlib' if that program exists in
or to `:' if neither program exists.
AC_CHECK_PROG, but set variable to the entire path of prog-to-check-for if found.
AC_CHECK_PROGS, but if any of progs-to-check-for are found, set variable to the entire path of the program found.
Go to the first, previous, next, last section, table of contents.