Lines Matching full:autoconf
55 describes how autoconf, automake, libtool, and make fit together. It
64 This document draws on several sources, including the autoconf
65 manual by David MacKenzie (*note autoconf overview: (autoconf)Top.),
110 autoconf
126 autoconf requires the GNU version of m4; the standard Unix m4 does
154 * The autoconf program, by David MacKenzie.
160 In 1994, David MacKenzie and others modified autoconf to incorporate
163 autoconf. gcc has been converted, eliminating the gcc configure script.
165 GNU autoconf was regularly maintained until late 1996. As of this
298 You must first write the file `configure.in'. This is an autoconf
299 input file, and the autoconf manual describes in detail what this file
319 that you will want to use. *Note Invoking autoscan: (autoconf)Invoking
324 uses. *Note Invoking ifnames: (autoconf)Invoking ifnames.
335 `autoconf' that you are using. This will prevent users from
336 running an earlier version of `autoconf' and perhaps getting an
372 versions of autoconf, automake, or others are in the builder's
388 autoconf to support compiling with Visual C++. Older programs use
405 This is essentially a bug in autoconf, and there will probably be
449 Macros which start with `AC_' are part of autoconf. Macros which start
574 possibly `acinclude.m4', you must use autoconf and automake programs to
579 autoconf
584 package, and the `autoconf' and `autoheader' commands are part of the
585 autoconf package.
596 used with the autoconf and automake packages. You must do this before
603 script which will have been created by `autoconf' with the
628 We'll first see what this looks like without using autoconf and
715 names which autoconf will use).
862 The other macros are standard autoconf macros.
878 See the autoconf manual for a more complete description.
914 autoconf
1004 *autoconf*
1019 invocations of autoconf macros. It may also contain ordinary
1046 This file is not always required. It defines local autoconf
1048 don't need any local autoconf macros, then you don't need this
1049 file at all. In fact, in general, you never need local autoconf
1084 package. This is generated by `autoconf' from `configure.in' and
1098 subdirectory). This file contains definitions of autoconf macros
1099 which `autoconf' will use when generating the file `configure'.
1100 These autoconf macros may be defined by you in `acinclude.m4' or
1104 standard autoconf macros, this file will not be needed at all.
1201 The autoconf manual explains how to set up a site specific cache
1323 translate these shortened strings into the canonical form. autoconf
1371 standard autoconf feature test.
1607 The autoconf macro `AC_ARG_PROGRAM' will handle this for you. If
1610 the autoconf documentation for `AC_ARG_PROGRAM'.
1622 Cygnus configure system, not autoconf. The top level `Makefile.in' is
1734 useful autoconf macros, such as `AC_CHECK_FUNCS'. autoconf macros
1742 As of this writing, the autoconf macro `AC_PROG_CC' does a link to
2166 Most autoconf macros will work correctly for a Canadian Cross. The
2174 not present, you will get a warning when you run `autoconf':
2184 There are a few other autoconf macros which will not work correctly
2231 The Cygnus configure script predates autoconf. All of its interesting
2232 features have been incorporated into autoconf. No new programs should
2237 Cygnus tree. Until those uses have been replaced with autoconf, some
2254 corresponding to `autoconf'. Instead, there is a single shell script
2257 autoconf, and it is incorrect, and indeed harmful, to run `autoconf' in
2315 Cygnus configure, unlike autoconf, normally does not do feature tests,
2318 The `Makefile' fragment support is similar to the autoconf
2327 Like an autoconf generated `configure' script, Cygnus configure will
2336 autoconf `AC_LINK_FILES' macro.
2344 has a `configure' file, Cygnus configure assumes that it is an autoconf
2355 like that done by autoconf generated `configure' scripts. This
2520 Which do I run first, `autoconf' or `automake'?
2521 Except when you first add autoconf or automake support to a
2526 `autoconf' says something about undefined macros.
2528 not defined by `autoconf'. You may be using an old version of
2529 `autoconf'; try building and installing a newer one. Make sure the
2530 newly installled `autoconf' is first on your `PATH'. Also, see
2544 This may mean that you tried to use an autoconf substitution in
2573 configure scripts in the tree are being converted to autoconf, but
