Lines Matching full:macro
312 define the preprocessor macro `HAVE_GETTIMEOFDAY' to the value 1 if the
313 `gettimeofday' function is available, and to not define the macro at
330 This macro takes a single argument, which is the name of a file in
334 This macro is optional. It may be used to indicate the version of
340 This macro takes two arguments: the name of the package, and a
342 macro is not needed if you are not using automake).
345 This macro names the header file which will hold the preprocessor
346 macro definitions at run time. Normally this should be
350 This macro may optionally name the input file for that header
362 This macro always appears in Cygnus configure scripts. Other
365 If this macro is used, the `--enable-maintainer-mode' option is
370 If this macro is not used, then the generated files will always be
375 (If you are not using automake, you do not need to use this macro).
378 Either this macro or `AM_EXEEXT' always appears in Cygnus configure
381 This macro looks for the executable suffix used on the host
383 systems, this is `.exe'. This macro directs automake to use the
385 macro does not take any arguments.
396 macro. It locates the C compiler to use. It does not take any
402 variant which does not call the macro `AC_PROG_CC_WORKS'. Examples
409 If you are writing C++ code, you will want to use this macro. It
416 using libtool, then you will need this macro. This macro is
427 feature tests. This defines the macro `_GNU_SOURCE' when
430 this macro is not defined, certain GNU extensions may not be
434 This macro takes a list of file names which the configure process
448 The different macro prefixes indicate which tool defines the macro.
473 in the `AC_OUTPUT' macro in `configure.in'.
547 for any unusual macros in the `configure.in' file, including any macro
548 which appears in a `AC_DEFINE' macro.
714 features are available. (I've cheated a bit by using the same macro
1022 an `AC_OUTPUT' macro listing which files to create when the
1051 sometimes a local macro is convenient.
1055 -I m4' in `Makefile.am' to force `aclocal' to look there for macro
1056 definitions. The macro definitions are then placed in separate
1226 macro in `configure.in' to tell `automake' and the `configure' script
1377 name, you should define a macro which describes the feature, rather than
1378 defining a macro which describes the particular system you are on.
1384 uses the `AC_CANONICAL_HOST' or `AC_CANONICAL_SYSTEM' macro).
1493 `configure.in'. This macro will arrange to define a few shell
1607 The autoconf macro `AC_ARG_PROGRAM' will handle this for you. If
1742 As of this writing, the autoconf macro `AC_PROG_CC' does a link to
2145 it by using the macro `AC_CANONICAL_SYSTEM', the same macro that is
2146 used to determine the target system. This macro will set the variables
2167 main exception is `AC_TRY_RUN'. This macro tries to compile and run a
2172 The `AC_TRY_RUN' macro provides an optional argument to tell the
2187 `AC_SYS_RESTARTABLE_SYSCALLS'. The `AC_CHECK_SIZEOF' macro is
2319 `AC_SUBST_FILE' macro.
2336 autoconf `AC_LINK_FILES' macro.
