@c @setchapternewpage odd
@c %**end of header
-@set EDITION 2.4.2
-@set VERSION 2.4.2
+@set EDITION 2.5
+@set VERSION 2.5
@set UPDATED July 1995
@iftex
configure source code packages using templates and an @code{m4} macro
package.
-Copyright (C) 1992, 1993, 1994 Free Software Foundation, Inc.
+Copyright (C) 1992, 1993, 1994, 1995 Free Software Foundation, Inc.
Permission is granted to make and distribute verbatim copies of
this manual provided the copyright notice and this permission notice
your source files --> [autoscan*] --> [configure.scan] --> configure.in
configure.in --. .------> autoconf* -----> configure
- +---+
+ +---+
[aclocal.m4] --+ `---.
[acsite.m4] ---' |
+--> [autoheader*] -> [config.h.in]
@item --verbose
Print the name of each directory where @code{autoreconf} runs
@code{autoconf} (and @code{autoheader}, if appropriate).
-
+
@item --version
Print the version number of Autoconf and exit.
@end table
@example
#! /bin/sh
-# From configure.in Revision: 1.30
+# From configure.in Revision: 1.30
@end example
@end defmac
These macros check for the presence or behavior of particular programs.
They are used to choose between several alternative programs and to
-decide what to do once one has been chosen.
+decide what to do once one has been chosen.
If there is no macro specifically defined to check for a program you need,
and you don't need to check for any special properties of
it, then you can use one of the general program check macros.
instead, like this:
@example
-AC_PATH_PROG(INETD, inetd, /usr/libexec/inetd,
+AC_PATH_PROG(INETD, inetd, /usr/libexec/inetd,
$PATH:/usr/libexec:/usr/sbin:/usr/etc:etc)
@end example
Makefiles, standards, GNU Coding Standards}, for the list. This
restriction allows users to start out with a fairly small set of
programs and build the rest, avoiding too many interdependencies between
-packages.
+packages.
Some of these external utilities have a portable subset of features, as
well; for example, don't rely on @code{ln} having a @samp{-f} option or
An abbreviation for your package or organization; the same prefix you
begin local Autoconf macros with, except lowercase by convention.
For cache values used by the distributed Autoconf macros, this value is
-@samp{ac}.
+@samp{ac}.
@item @code{_cv_}
Indicates that this shell variable is a cache value.
@item SYS
Operating system features.
@item TYPE
-C builtin or declared types.
+C builtin or declared types.
@item VAR
C variables in libraries.
@end table
@code{config.sub} to canonicalize system type aliases.
@node Canonicalizing, System Type Variables, Specifying Names, Manual Configuration
-@section Getting the Canonical System Type
+@section Getting the Canonical System Type
The following macros make the system type available to @code{configure}
scripts. They run the shell script @code{config.guess} to determine any
@c @setchapternewpage odd
@c %**end of header
-@set EDITION 2.4.2
-@set VERSION 2.4.2
+@set EDITION 2.5
+@set VERSION 2.5
@set UPDATED July 1995
@iftex
configure source code packages using templates and an @code{m4} macro
package.
-Copyright (C) 1992, 1993, 1994 Free Software Foundation, Inc.
+Copyright (C) 1992, 1993, 1994, 1995 Free Software Foundation, Inc.
Permission is granted to make and distribute verbatim copies of
this manual provided the copyright notice and this permission notice
your source files --> [autoscan*] --> [configure.scan] --> configure.in
configure.in --. .------> autoconf* -----> configure
- +---+
+ +---+
[aclocal.m4] --+ `---.
[acsite.m4] ---' |
+--> [autoheader*] -> [config.h.in]
@item --verbose
Print the name of each directory where @code{autoreconf} runs
@code{autoconf} (and @code{autoheader}, if appropriate).
-
+
@item --version
Print the version number of Autoconf and exit.
@end table
@example
#! /bin/sh
-# From configure.in Revision: 1.30
+# From configure.in Revision: 1.30
@end example
@end defmac
These macros check for the presence or behavior of particular programs.
They are used to choose between several alternative programs and to
-decide what to do once one has been chosen.
+decide what to do once one has been chosen.
If there is no macro specifically defined to check for a program you need,
and you don't need to check for any special properties of
it, then you can use one of the general program check macros.
instead, like this:
@example
-AC_PATH_PROG(INETD, inetd, /usr/libexec/inetd,
+AC_PATH_PROG(INETD, inetd, /usr/libexec/inetd,
$PATH:/usr/libexec:/usr/sbin:/usr/etc:etc)
@end example
Makefiles, standards, GNU Coding Standards}, for the list. This
restriction allows users to start out with a fairly small set of
programs and build the rest, avoiding too many interdependencies between
-packages.
+packages.
Some of these external utilities have a portable subset of features, as
well; for example, don't rely on @code{ln} having a @samp{-f} option or
An abbreviation for your package or organization; the same prefix you
begin local Autoconf macros with, except lowercase by convention.
For cache values used by the distributed Autoconf macros, this value is
-@samp{ac}.
+@samp{ac}.
@item @code{_cv_}
Indicates that this shell variable is a cache value.
@item SYS
Operating system features.
@item TYPE
-C builtin or declared types.
+C builtin or declared types.
@item VAR
C variables in libraries.
@end table
@code{config.sub} to canonicalize system type aliases.
@node Canonicalizing, System Type Variables, Specifying Names, Manual Configuration
-@section Getting the Canonical System Type
+@section Getting the Canonical System Type
The following macros make the system type available to @code{configure}
scripts. They run the shell script @code{config.guess} to determine any
projects / thirdparty / autoconf.git / commitdiff
