]> This is used when a ``multilib'' library is being built. The first optional argument is the name of the <TT>Makefile</TT> being generated; it defaults to <samp>Makefile</samp>. The second optional argument is used to find the top source directory; it defaults to the empty string (generally this should not be used unless you are familiar with the internals). . Runs many macros required for proper operation of the generated Makefiles. This macro has two forms, the first of which is preferred. In this form, <CODE>AM_INIT_AUTOMAKE</CODE> is called with a single argument: a space-separated list of Automake options that should be applied to every <TT>Makefile.am</TT> in the tree. The effect is as if each option were listed in <CODE>AUTOMAKE_OPTIONS</CODE> (Options). The second, deprecated, form of <CODE>AM_INIT_AUTOMAKE</CODE> has two required arguments: the package and the version number. This form is obsolete because the <VAR>package</VAR> and <VAR>version</VAR> can be obtained from Autoconf's <CODE>AC_INIT</CODE> macro (which itself has an old and a new form). If your <TT>configure.ac</TT> has: <TABLE><tr><td> </td><td class=example><pre> AC_INIT([src/foo.c]) AM_INIT_AUTOMAKE([mumble], [1.5]) </pre></td></tr></table> you can modernize it as follows: <TABLE><tr><td> </td><td class=example><pre> AC_INIT([mumble], [1.5]) AC_CONFIG_SRCDIR([src/foo.c]) AM_INIT_AUTOMAKE </pre></td></tr></table> Note that if you're upgrading your <TT>configure.ac</TT> from an earlier version of Automake, it is not always correct to simply move the package and version arguments from <CODE>AM_INIT_AUTOMAKE</CODE> directly to <CODE>AC_INIT</CODE>, as in the example above. The first argument to <CODE>AC_INIT</CODE> should be the name of your package (e.g., @samp{GNU Automake}), not the tarball name (e.g., <samp>automake</samp>) that you used to pass to <CODE>AM_INIT_AUTOMAKE</CODE>. Autoconf tries to derive a tarball name from the package name, which should work for most but not all package names. (If it doesn't work for yours, you can use the four-argument form of <CODE>AC_INIT</CODE> to provide the tarball name explicitly). By default this macro <CODE>AC_DEFINE</CODE>'s <CODE>PACKAGE</CODE> and <CODE>VERSION</CODE>. This can be avoided by passing the <samp>no-define</samp> option, as in: <TABLE><tr><td> </td><td class=example><pre> AM_INIT_AUTOMAKE([gnits 1.5 no-define dist-bzip2]) </pre></td></tr></table> or by passing a third non-empty argument to the obsolete form. Searches for the program <CODE>emacs</CODE>, and, if found, sets the output variable <CODE>lispdir</CODE> to the full path to Emacs' site-lisp directory. Note that this test assumes the <CODE>emacs</CODE> found to be a version that supports Emacs Lisp (such as gnu Emacs or XEmacs). Other emacsen can cause this test to hang (some, like old versions of MicroEmacs, start up in interactive mode, requiring <KBD>C-x C-c</KBD> to exit, which is hardly obvious for a non-emacs user). In most cases, however, you should be able to use <KBD>C-c</KBD> to kill the test. In order to avoid problems, you can set EMACS to ``no'' in the environment, or use the <samp>--with-lispdir</samp> option to <CODE>configure</CODE> to explicitly set the correct path (if you're sure you have an <CODE>emacs</CODE> that supports Emacs Lisp). Use this macro when you have assembly code in your project. This will choose the assembler for you (by default the C compiler) and set <CODE>CCAS</CODE>, and will also set <CODE>CCASFLAGS</CODE> if required. This is like <CODE>AC_PROG_CC_C_O</CODE>, but it generates its results in the manner required by Automake. You must use this instead of <CODE>AC_PROG_CC_C_O</CODE> when you need this functionality, that is, when using per-target flags or subdir-objects with C sources. Like <CODE>AC_PROG_LEX</CODE> (@pxref{Particular Programs, , Particular Program Checks, autoconf, The Autoconf Manual}), but uses the <CODE>missing</CODE> script on systems that do not have <CODE>lex</CODE>. HP-UX 10 is one such system. This macro finds the <CODE>gcj</CODE> program or causes an error. It sets <CODE>GCJ</CODE> and <CODE>GCJFLAGS</CODE>. <CODE>gcj</CODE> is the Java front-end to the GNU Compiler Collection. Find a compiler for Unified Parallel C and define the <CODE>UPC</CODE> variable. The default <VAR>compiler-search-list</VAR> is <samp>upcc upc</samp>. This macro will abort <CODE>configure</CODE> if no Unified Parallel C compiler is found. Enable the machinery for less verbose build output (Options). Add support for the <A HREF="http://dmalloc.com/>Dmalloc package</A>. If the user runs <CODE>configure</CODE> with <samp>--with-dmalloc</samp>, then define <CODE>WITH_DMALLOC</CODE> and add <samp>-ldmalloc</samp> to <CODE>LIBS</CODE>. Adds <samp>--with-regex</samp> to the <CODE>configure</CODE> command line. If specified (the default), then the <samp>regex</samp> regular expression library is used, <TT>regex.o</TT> is put into <CODE>LIBOBJS</CODE>, and <CODE>WITH_REGEX</CODE> is defined. If <samp>--without-regex</samp> is given, then the <CODE>rx</CODE> regular expression library is used, and <TT>rx.o</TT> is put into <CODE>LIBOBJS</CODE>. </DL> @node Obsolete Macros