[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
FYI: doc's indices overhaul
|
From: |
Alexandre Duret-Lutz |
|
Subject: |
FYI: doc's indices overhaul |
|
Date: |
Sun, 05 Dec 2004 16:35:18 +0100 |
|
User-agent: |
Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux) |
I'm installing this on HEAD and branch-1-9.
2004-12-05 Alexandre Duret-Lutz <address@hidden>
* doc/automake.texi: Use @acindex for Autoconf macros, and @vindex
for variables (@cvindex was previously used for both). Separate
these two indices in the output. Use @code, @file, and @command
in @cindex lines wherever appropriate so they render nicely.
Index: doc/automake.texi
===================================================================
RCS file: /cvs/automake/automake/doc/automake.texi,v
retrieving revision 1.70
diff -u -r1.70 automake.texi
--- doc/automake.texi 5 Dec 2004 13:10:16 -0000 1.70
+++ doc/automake.texi 5 Dec 2004 15:33:06 -0000
@@ -53,10 +53,8 @@
@insertcopying
@end titlepage
address@hidden Define an index of configure output variables.
address@hidden ov
address@hidden Define an index of configure variables.
address@hidden cv
address@hidden Define an index of configure macros.
address@hidden ac
@c Define an index of options.
@defcodeindex op
@c Define an index of targets.
@@ -64,11 +62,8 @@
@c Define an index of commands.
@defcodeindex cm
address@hidden Put the macros and variables into their own index.
address@hidden @syncodeindex fn cp
address@hidden ov vr
address@hidden cv vr
address@hidden fn vr
address@hidden Put the macros in the function index.
address@hidden ac fn
@c Put everything else into one index (arbitrarily chosen to be the concept
index).
@syncodeindex op cp
@@ -271,7 +266,8 @@
Indices
-* Macro and Variable Index:: Index of Autoconf macros and Automake variables
+* Macro Index:: Index of Autoconf macros
+* Variable Index:: Index of Makefile variables
* General Index:: General index
@end detailmenu
@@ -324,8 +320,8 @@
fully GNU standards-compliant, and do not require @code{perl} in order
to be built.
address@hidden BUGS, reporting
address@hidden Reporting BUGS
address@hidden Bugs, reporting
address@hidden Reporting bugs
@cindex E-mail, bug reports
Mail suggestions and bug reports for Automake to
@@ -358,7 +354,7 @@
for compiling and linking programs to be generated.
@cindex Non-standard targets
address@hidden cvs-dist, non-standard example
address@hidden @code{cvs-dist}, non-standard example
@trindex cvs-dist
The variable definitions and rules in the @file{Makefile.am} are
@@ -375,6 +371,7 @@
behavior.
@cindex Append operator
address@hidden +=
A special exception is that the GNU make append operator, @samp{+=}, is
supported. This operator appends its right hand argument to the variable
specified on the left. Automake will translate the operator into
@@ -421,7 +418,7 @@
it would use the files @file{a.c}, @file{b.c}, and @file{c.c} as the
contents of @code{foo_SOURCES}.
address@hidden ## (special Automake comment)
address@hidden @code{##} (special Automake comment)
@cindex Special Automake comment
@cindex Comment, special to Automake
@@ -454,12 +451,12 @@
not want to use all the GNU conventions.
@cindex Strictness, defined
address@hidden Strictness, foreign
address@hidden foreign strictness
address@hidden Strictness, gnu
address@hidden gnu strictness
address@hidden Strictness, gnits
address@hidden gnits strictness
address@hidden Strictness, @code{foreign}
address@hidden @code{foreign} strictness
address@hidden Strictness, @code{gnu}
address@hidden @code{gnu} strictness
address@hidden Strictness, @code{gnits}
address@hidden @code{gnits} strictness
To this end, Automake supports three levels of @dfn{strictness}---the
strictness indicating how stringently Automake should check standards
@@ -507,10 +504,11 @@
built, and how they are installed. This scheme also supports
@code{configure} time determination of what should be built.
address@hidden _PROGRAMS primary variable
address@hidden PROGRAMS primary variable
address@hidden Primary variable, PROGRAMS
address@hidden @code{_PROGRAMS} primary variable
address@hidden @code{PROGRAMS} primary variable
address@hidden Primary variable, @code{PROGRAMS}
@cindex Primary variable, defined
address@hidden _PROGRAMS
At @code{make} time, certain variables are used to determine which
objects are to be built. The variable names are made of several pieces
@@ -521,14 +519,15 @@
list of programs which are to be compiled and linked.
@vindex PROGRAMS
address@hidden pkglibdir, defined
address@hidden pkgincludedir, defined
address@hidden pkgdatadir, defined
address@hidden @code{pkglibdir}, defined
address@hidden @code{pkgincludedir}, defined
address@hidden @code{pkgdatadir}, defined
@vindex pkglibdir
@vindex pkgincludedir
@vindex pkgdatadir
address@hidden @code{PACKAGE}, directory
A different set of names is used to decide where the built objects
should be installed. These names are prefixes to the primary which
indicate which standard directory should be used as the installation
@@ -538,10 +537,8 @@
and @code{pkgdatadir}; these are the same as the address@hidden
versions, but with @samp{$(PACKAGE)} appended. For instance,
@code{pkglibdir} is defined as @code{$(libdir)/$(PACKAGE)}.
address@hidden PACKAGE, directory
-
address@hidden EXTRA_, prepending
address@hidden @code{EXTRA_}, prepending
For each primary, there is one additional variable named by prepending
@samp{EXTRA_} to the primary name. This variable is used to list
objects which may or may not be built, depending on what
@@ -549,9 +546,9 @@
must statically know the entire list of objects that may be built in
order to generate a @file{Makefile.in} that will work in all cases.
address@hidden EXTRA_PROGRAMS, defined
address@hidden Example, EXTRA_PROGRAMS
address@hidden cpio example
address@hidden @code{EXTRA_PROGRAMS}, defined
address@hidden Example, @code{EXTRA_PROGRAMS}
address@hidden @command{cpio} example
For instance, @code{cpio} decides at configure time which programs are
built. Some of the programs are installed in @code{bindir}, and some
@@ -594,14 +591,16 @@
html_DATA = automake.html
@end example
address@hidden noinst primary prefix, definition
address@hidden @code{noinst_} primary prefix, definition
address@hidden noinst_
The special prefix @samp{noinst} indicates that the objects in question
should be built but not installed at all. This is usually used for
objects required to build the rest of your package, for instance static
libraries (@pxref{A Library}), or helper scripts.
address@hidden check primary prefix, definition
address@hidden @code{check_} primary prefix, definition
address@hidden check_
The special prefix @samp{check} indicates that the objects in question
should not be built until the @code{make check} command is run. Those
@@ -775,7 +774,7 @@
provide a portability framework, but your @file{Makefile.in}s have been
ad-hoc. You want to make them bulletproof, so you turn to Automake.
address@hidden AM_INIT_AUTOMAKE, example use
address@hidden @code{AM_INIT_AUTOMAKE}, example use
The first step is to update your @file{configure.ac} to include the
commands that @code{automake} needs. The way to do this is to add an
@@ -791,9 +790,9 @@
doesn't use @code{gettext}, it doesn't want to build a shared library),
you're done with this part. That was easy!
address@hidden aclocal program, introduction
address@hidden aclocal.m4, preexisting
address@hidden acinclude.m4, defined
address@hidden @command{aclocal} program, introduction
address@hidden @file{aclocal.m4}, preexisting
address@hidden @file{acinclude.m4}, defined
Now you must regenerate @file{configure}. But to do that, you'll need
to tell @code{autoconf} how to find the new macro you've used. The
@@ -809,7 +808,7 @@
autoconf
@end example
address@hidden zardoz example
address@hidden @command{zardoz} example
Now it is time to write your @file{Makefile.am} for @code{zardoz}.
Since @code{zardoz} is a user program, you want to install it where the
@@ -848,9 +847,9 @@
two-liner. GNU Hello is internationalized, does option processing, and
has a manual and a test suite.
address@hidden configure.ac, from GNU Hello
address@hidden GNU Hello, configure.ac
address@hidden Hello, configure.ac
address@hidden @file{configure.ac}, from GNU Hello
address@hidden GNU Hello, @file{configure.ac}
address@hidden Hello, @file{configure.ac}
Here is the @file{configure.ac} from GNU Hello.
@strong{Please note:} The calls to @code{AC_INIT} and @code{AM_INIT_AUTOMAKE}
@@ -933,7 +932,8 @@
The script @file{hello} is generated by @code{configure}, and is the
only test case. @code{make check} will run this test.
address@hidden INCLUDES, example usage
address@hidden @code{INCLUDES}, example usage
address@hidden INCLUDES
Last we have @file{src/Makefile.am}, where all the real work is done:
@c FIXME: As all the Hello World excerpts in this manual, this
@@ -951,9 +951,9 @@
@node true
@section Building true and false
address@hidden Example, false and true
address@hidden false Example
address@hidden true Example
address@hidden Example, @command{false} and @command{true}
address@hidden @command{false} Example
address@hidden @command{true} Example
Here is another, trickier example. It shows how to generate two
programs (@code{true} and @code{false}) from the same source file
@@ -1036,9 +1036,9 @@
@node Invoking Automake
@chapter Creating a @file{Makefile.in}
address@hidden Multiple configure.ac files
address@hidden Invoking Automake
address@hidden Automake, invoking
address@hidden Multiple @file{configure.ac} files
address@hidden Invoking @command{automake}
address@hidden @command{automake}, invoking
To create all the @file{Makefile.in}s for a package, run the
@code{automake} program in the top level directory, with no arguments.
@@ -1074,15 +1074,15 @@
@file{configure} and you still have to run @code{autoconf} yourself for
this purpose.
address@hidden Automake options
address@hidden Options, Automake
address@hidden @command{automake} options
address@hidden Options, @command{automake}
@cindex Strictness, command line
address@hidden accepts the following options:
address@hidden accepts the following options:
@cindex Extra files distributed with Automake
@cindex Files distributed with Automake
address@hidden config.guess
address@hidden @file{config.guess}
@table @samp
@item -a
@@ -1242,8 +1242,8 @@
@node configure
@chapter Scanning @file{configure.ac}
address@hidden configure.ac, scanning
address@hidden Scanning configure.ac
address@hidden @file{configure.ac}, scanning
address@hidden Scanning @file{configure.ac}
Automake scans the package's @file{configure.ac} to determine certain
information about the package. Some @code{autoconf} macros are required
@@ -1274,10 +1274,10 @@
@cindex Automake requirements
@cindex Requirements of Automake
address@hidden AM_INIT_AUTOMAKE
The one real requirement of Automake is that your @file{configure.ac}
call @code{AM_INIT_AUTOMAKE}. This macro does several things which are
required for proper Automake operation (@pxref{Macros}).
address@hidden AM_INIT_AUTOMAKE
Here are the other macros which Automake requires but which are not run
by @code{AM_INIT_AUTOMAKE}:
@@ -1285,6 +1285,8 @@
@table @code
@item AC_CONFIG_FILES
@itemx AC_OUTPUT
address@hidden AC_CONFIG_FILES
address@hidden AC_OUTPUT
Automake uses these to determine which files to create (@pxref{Output, ,
Creating Output Files, autoconf, The Autoconf Manual}). A listed file
is considered to be an Automake generated @file{Makefile} if there
@@ -1299,8 +1301,6 @@
to be Automake generated.
Files created by @code{AC_CONFIG_FILES} are removed by @code{make distclean}.
address@hidden AC_CONFIG_FILES
address@hidden AC_OUTPUT
@end table
@@ -1315,18 +1315,16 @@
macros and tailor the generated @file{Makefile.in} appropriately.
Currently recognized macros and their effects are:
address@hidden @code
address@hidden @code
@item AC_CONFIG_HEADERS
Automake will generate rules to rebuild these headers. Older versions
of Automake required the use of @code{AM_CONFIG_HEADER}
(@pxref{Macros}); this is no longer the case today.
address@hidden AC_CONFIG_HEADERS
@item AC_CONFIG_LINKS
Automake will generate rules to remove @file{configure} generated links on
@code{make distclean} and to distribute named source files as part of
@code{make dist}.
address@hidden AC_CONFIG_LINKS
@item AC_CONFIG_AUX_DIR
Automake will look for various helper scripts, such as
@@ -1338,10 +1336,9 @@
@file{py-compile}, @file{texinfo.tex}, and @file{ylwrap}.) Not all
scripts are always searched for; some scripts will only be sought if the
generated @file{Makefile.in} requires them.
address@hidden AC_CONFIG_AUX_DIR
If @code{AC_CONFIG_AUX_DIR} is not given, the scripts are looked for in
-their @samp{standard} locations. For @file{mdate-sh},
+their standard locations. For @file{mdate-sh},
@file{texinfo.tex}, and @file{ylwrap}, the standard location is the
source directory corresponding to the current @file{Makefile.am}. For
the rest, the standard location is the first one of @file{.}, @file{..},
@@ -1355,21 +1352,19 @@
@item AC_CANONICAL_BUILD
@itemx AC_CANONICAL_HOST
@itemx AC_CANONICAL_TARGET
address@hidden build_triplet
address@hidden host_triplet
address@hidden target_triplet
Automake will ensure that @file{config.guess} and @file{config.sub}
exist. Also, the @file{Makefile} variables @samp{build_triplet},
@samp{host_triplet} and @samp{target_triplet} are introduced. See
@ref{Canonicalizing, , Getting the Canonical System Type, autoconf,
The Autoconf Manual}.
address@hidden AC_CANONICAL_BUILD
address@hidden AC_CANONICAL_HOST
address@hidden AC_CANONICAL_TARGET
address@hidden build_triplet
address@hidden host_triplet
address@hidden target_triplet
@item AC_LIBSOURCE
@itemx AC_LIBSOURCES
@itemx AC_LIBOBJ
address@hidden LIBOBJS
Automake will automatically distribute any file listed in
@code{AC_LIBSOURCE} or @code{AC_LIBSOURCES}.
@@ -1378,66 +1373,53 @@
@file{file.c} will be distributed automatically by Automake. This
encompasses many macros like @code{AC_FUNC_ALLOCA},
@code{AC_FUNC_MEMCMP}, @code{AC_REPLACE_FUNCS}, and others.
address@hidden AC_LIBOBJ
address@hidden AC_LIBSOURCE
address@hidden AC_LIBSOURCES
By the way, direct assignments to @code{LIBOBJS} are no longer
supported. You should always use @code{AC_LIBOBJ} for this purpose.
@xref{AC_LIBOBJ vs LIBOBJS, , @code{AC_LIBOBJ} vs. @code{LIBOBJS},
autoconf, The Autoconf Manual}.
address@hidden LIBOBJS
@item AC_PROG_RANLIB
This is required if any libraries are built in the package.
@xref{Particular Programs, , Particular Program Checks, autoconf, The
Autoconf Manual}.
address@hidden AC_PROG_RANLIB
@item AC_PROG_CXX
This is required if any C++ source is included. @xref{Particular
Programs, , Particular Program Checks, autoconf, The Autoconf Manual}.
address@hidden AC_PROG_CXX
@item AC_PROG_F77
This is required if any Fortran 77 source is included. This macro is
distributed with Autoconf version 2.13 and later. @xref{Particular
Programs, , Particular Program Checks, autoconf, The Autoconf Manual}.
address@hidden AC_PROG_F77
@item AC_F77_LIBRARY_LDFLAGS
This is required for programs and shared libraries that are a mixture of
languages that include Fortran 77 (@pxref{Mixing Fortran 77 With C and
C++}). @xref{Macros, , Autoconf macros supplied with Automake}.
address@hidden AC_F77_LIBRARY_LDFLAGS
@item AC_PROG_FC
This is required if any Fortran 90/95 source is included. This macro is
distributed with Autoconf version 2.58 and later. @xref{Particular
Programs, , Particular Program Checks, autoconf, The Autoconf Manual}.
address@hidden AC_PROG_FC
@item AC_PROG_LIBTOOL
Automake will turn on processing for @code{libtool} (@pxref{Top, ,
Introduction, libtool, The Libtool Manual}).
address@hidden AC_PROG_LIBTOOL
@item AC_PROG_YACC
address@hidden YACC
If a Yacc source file is seen, then you must either use this macro or
define the variable @samp{YACC} in @file{configure.ac}. The former is
preferred (@pxref{Particular Programs, , Particular Program Checks,
autoconf, The Autoconf Manual}).
address@hidden AC_PROG_YACC
address@hidden YACC
@item AC_PROG_LEX
If a Lex source file is seen, then this macro must be used.
@xref{Particular Programs, , Particular Program Checks, autoconf, The
Autoconf Manual}.
address@hidden AC_PROG_LEX
@item AC_REQUIRE_AUX_FILE
address@hidden AC_REQUIRE_AUX_FILE
@command{automake} will ensure each file for which this macro is
called exists in the aux directory, and will complain otherwise. It
will also automatically distribute the file. This macro should be
@@ -1447,7 +1429,6 @@
The Autoconf Manual}.
@item AC_SUBST
address@hidden AC_SUBST
The first argument is automatically defined as a variable in each
generated @file{Makefile.in}. @xref{Setting Output Variables, , Setting
Output Variables, autoconf, The Autoconf Manual}.
@@ -1461,27 +1442,23 @@
@item AM_C_PROTOTYPES
This is required when using automatic de-ANSI-fication; see @ref{ANSI}.
address@hidden AM_C_PROTOTYPES
@item AM_GNU_GETTEXT
This macro is required for packages which use GNU gettext
(@pxref{gettext}). It is distributed with gettext. If Automake sees
this macro it ensures that the package meets some of gettext's
requirements.
address@hidden AM_GNU_GETTEXT
@item AM_MAINTAINER_MODE
@opindex --enable-maintainer-mode
This macro adds a @samp{--enable-maintainer-mode} option to
@code{configure}. If this is used, @code{automake} will cause
@samp{maintainer-only} rules to be turned off by default in the
-generated @file{Makefile.in}s. This macro defines the
+generated @file{Makefile.in}s. This macro defines the
@samp{MAINTAINER_MODE} conditional, which you can use in your own
address@hidden
address@hidden AM_MAINTAINER_MODE
address@hidden @xref{maintainer-mode}.
@item m4_include
address@hidden m4_include
Files included by @file{configure.ac} using this macro will be
detected by Automake and automatically distributed. They will also
appear as dependencies in @file{Makefile} rules.
@@ -1492,14 +1469,14 @@
opposed to macros installed in a system-wide directory, see
@ref{Invoking aclocal}).
address@hidden table
address@hidden ftable
@node Invoking aclocal
@section Auto-generating aclocal.m4
address@hidden Invoking aclocal
address@hidden aclocal, Invoking
address@hidden Invoking @command{aclocal}
address@hidden @command{aclocal}, Invoking
Automake includes a number of Autoconf macros which can be used in
your package (@pxref{Macros}); some of them are actually required by
@@ -1561,8 +1538,8 @@
@node aclocal options
@section aclocal options
address@hidden aclocal, Options
address@hidden Options, aclocal
address@hidden @command{aclocal}, Options
address@hidden Options, @command{aclocal}
@code{aclocal} accepts the following options:
@@ -1637,7 +1614,7 @@
@section Macro search path
@cindex Macro search path
address@hidden aclocal search path
address@hidden @command{aclocal} search path
By default, @command{aclocal} searches for @file{.m4} files in the following
directories, in this order:
@@ -1795,12 +1772,13 @@
@table @code
@item AM_CONFIG_HEADER
address@hidden AM_CONFIG_HEADER
Automake will generate rules to automatically regenerate the config
header. This obsolete macro is a synonym of @code{AC_CONFIG_HEADERS}
today (@pxref{Optional}).
address@hidden AM_CONFIG_HEADER
@item AM_ENABLE_MULTILIB
address@hidden AM_ENABLE_MULTILIB
This is used when a ``multilib'' library is being built. The first
optional argument is the name of the @file{Makefile} being generated; it
defaults to @samp{Makefile}. The second option argument is used to find
@@ -1809,29 +1787,35 @@
@xref{Multilibs}.
@item AM_C_PROTOTYPES
address@hidden AM_C_PROTOTYPES
address@hidden ANSI2KNR
address@hidden U
Check to see if function prototypes are understood by the compiler. If
so, define @samp{PROTOTYPES} and set the output variables @samp{U} and
@samp{ANSI2KNR} to the empty string. Otherwise, set @samp{U} to
@samp{_} and @samp{ANSI2KNR} to @samp{./ansi2knr}. Automake uses these
values to implement automatic de-ANSI-fication.
address@hidden AM_C_PROTOTYPES
@item AM_HEADER_TIOCGWINSZ_NEEDS_SYS_IOCTL
address@hidden AM_HEADER_TIOCGWINSZ_NEEDS_SYS_IOCTL
If the use of @code{TIOCGWINSZ} requires @file{<sys/ioctl.h>}, then
define @code{GWINSZ_IN_SYS_IOCTL}. Otherwise @code{TIOCGWINSZ} can be
-found in @file{<termios.h>}.
address@hidden AM_HEADER_TIOCGWINSZ_NEEDS_SYS_IOCTL
+found in @file{<termios.h>}. This macro is obsolete, you should
+use Autoconf's @code{AC_HEADER_TIOCGWINSZ} instead.
@item AM_INIT_AUTOMAKE([OPTIONS])
@itemx AM_INIT_AUTOMAKE(PACKAGE, VERSION, [NO-DEFINE])
address@hidden AM_INIT_AUTOMAKE
Runs many macros required for proper operation of the generated Makefiles.
address@hidden AUTOMAKE_OPTIONS
This macro has two forms, the first of which is preferred.
In this form, @code{AM_INIT_AUTOMAKE} is called with a
single argument --- a space-separated list of Automake options which should
be applied to every @file{Makefile.am} in the tree. The effect is as if
-each option were listed in @code{AUTOMAKE_OPTIONS}.
+each option were listed in @code{AUTOMAKE_OPTIONS} (@pxref{Options}).
address@hidden AC_INIT
The second, deprecated, form of @code{AM_INIT_AUTOMAKE} has two required
arguments: the package and the version number. This form is
obsolete because the @var{package} and @var{version} can be obtained
@@ -1839,11 +1823,15 @@
form).
If your @file{configure.ac} has:
+
@example
AC_INIT(src/foo.c)
AM_INIT_AUTOMAKE(mumble, 1.5)
@end example
+
address@hidden
you can modernize it as follows:
+
@example
AC_INIT(mumble, 1.5)
AC_CONFIG_SRCDIR(src/foo.c)
@@ -1862,6 +1850,9 @@
four-argument form of @code{AC_INIT} --- supported in Autoconf versions
greater than 2.52g --- to provide the tarball name explicitly).
address@hidden @code{PACKAGE}, prevent definition
address@hidden @code{VERSION}, prevent definition
address@hidden no-define
By default this macro @code{AC_DEFINE}'s @samp{PACKAGE} and
@samp{VERSION}. This can be avoided by passing the @samp{no-define}
option, as in:
@@ -1870,10 +1861,10 @@
@end example
or by passing a third non-empty argument to the obsolete form.
address@hidden PACKAGE, prevent definition
address@hidden VERSION, prevent definition
-
@item AM_PATH_LISPDIR
address@hidden AM_PATH_LISPDIR
address@hidden EMACS
address@hidden lispdir
Searches for the program @code{emacs}, and, if found, sets the output
variable @code{lispdir} to the full path to Emacs' site-lisp directory.
@@ -1887,44 +1878,54 @@
use the @samp{--with-lispdir} option to @command{configure} to
explicitly set the correct path (if you're sure you have an @code{emacs}
that supports Emacs Lisp.
address@hidden AM_PATH_LISPDIR
@item AM_PROG_AS
address@hidden AM_PROG_AS
address@hidden CCAS
address@hidden CCASFLAGS
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}, and will also set @code{CCASFLAGS} if required.
@item AM_PROG_CC_C_O
address@hidden AM_PROG_CC_C_O
address@hidden AC_PROG_CC_C_O
This is like @code{AC_PROG_CC_C_O}, but it generates its results in
the manner required by automake. You must use this instead of
@code{AC_PROG_CC_C_O} when you need this functionality, that is, when
using per-target flags or subdir-objects with C sources.
@item AM_PROG_LEX
address@hidden HP-UX 10, lex problems
address@hidden lex problems with HP-UX 10
address@hidden AM_PROG_LEX
address@hidden AC_PROG_LEX
address@hidden HP-UX 10, @command{lex} problems
address@hidden @command{lex} problems with HP-UX 10
Like @code{AC_PROG_LEX} (@pxref{Particular Programs, , Particular
Program Checks, autoconf, The Autoconf Manual}), but uses the
@code{missing} script on systems that do not have @code{lex}.
@samp{HP-UX 10} is one such system.
@item AM_PROG_GCJ
address@hidden AM_PROG_GCJ
address@hidden GCJ
address@hidden GCJFLAGS
This macro finds the @code{gcj} program or causes an error. It sets
@samp{GCJ} and @samp{GCJFLAGS}. @code{gcj} is the Java front-end to the
GNU Compiler Collection.
address@hidden AM_PROG_GCJ
@item AM_SYS_POSIX_TERMIOS
address@hidden am_cv_sys_posix_termios
address@hidden AM_SYS_POSIX_TERMIOS
@cindex POSIX termios headers
@cindex termios POSIX headers
Check to see if POSIX termios headers and functions are available on the
system. If so, set the shell variable @code{am_cv_sys_posix_termios} to
address@hidden If not, set the variable to @samp{no}.
address@hidden If not, set the variable to @samp{no}. This macro is obsolete,
+you should use Autoconf's @code{AC_SYS_POSIX_TERMIOS} instead.
@item AM_WITH_DMALLOC
address@hidden WITH_DMALLOC
address@hidden dmalloc, support for
address@hidden AM_WITH_DMALLOC
address@hidden @command{dmalloc}, support for
address@hidden WITH_DMALLOC
@opindex --with-dmalloc
Add support for the
@uref{ftp://ftp.letters.com/src/dmalloc/dmalloc.tar.gz, dmalloc}
@@ -1932,7 +1933,8 @@
@code{WITH_DMALLOC} and add @samp{-ldmalloc} to @code{LIBS}.
@item AM_WITH_REGEX
address@hidden WITH_REGEX
address@hidden AM_WITH_REGEX
address@hidden WITH_REGEX
@opindex --with-regex
@cindex regex package
@cindex rx package
@@ -1954,7 +1956,7 @@
them as implementation details; or better, do not consider them at all:
skip this section!
address@hidden @code
address@hidden @code
@item _AM_DEPENDENCIES
@itemx AM_SET_DEPDIR
@itemx AM_DEP_TRACK
@@ -1979,14 +1981,14 @@
where the clock is set incorrectly. This macro is automatically run
from @code{AM_INIT_AUTOMAKE}.
address@hidden table
address@hidden ftable
@node Extending aclocal
@section Writing your own aclocal macros
address@hidden aclocal, extending
address@hidden Extending aclocal
address@hidden @command{aclocal}, extending
address@hidden Extending @command{aclocal}
The @command{aclocal} program doesn't have any built-in knowledge of any
macros, so it is easy to extend it with your own macros.
@@ -2014,9 +2016,9 @@
Especially, any call to @code{AC_PREREQ} should be done inside the
defined macro, not at the beginning of the file.
address@hidden underquoted AC_DEFUN
address@hidden AC_DEFUN
address@hidden AC_PREREQ
address@hidden underquoted @code{AC_DEFUN}
address@hidden AC_DEFUN
address@hidden AC_PREREQ
Starting with Automake 1.8, @command{aclocal} will warn about all
underquoted calls to @code{AC_DEFUN}. We realize this will annoy a
@@ -2139,7 +2141,7 @@
@node Future of aclocal
@section The Future of @command{aclocal}
address@hidden aclocal's scheduled death
address@hidden @command{aclocal}'s scheduled death
@command{aclocal} is expected to disappear. This feature really
should not be offered by Automake. Automake should focus on generating
@@ -2213,7 +2215,7 @@
@node Subdirectories
@section Recursing subdirectories
address@hidden SUBDIRS, explained
address@hidden @code{SUBDIRS}, explained
In packages with subdirectories, the top level @file{Makefile.am} must
tell Automake which subdirectories are to be built. This is done via
@@ -2511,7 +2513,8 @@
include_HEADERS = inc/stdio.h
@end example
address@hidden nobase_
address@hidden nobase_
address@hidden @code{nobase_} prefix
@cindex Path stripping, avoiding
@cindex Avoiding path stripping
@@ -2523,9 +2526,11 @@
nobase_include_HEADERS = sys/types.h
@end example
address@hidden nobase_ and dist_ or nodist_
address@hidden dist_ and nobase_
address@hidden nodist_ and nobase_
address@hidden @code{nobase_} and @code{dist_} or @code{nodist_}
address@hidden @code{dist_} and @code{nobase_}
address@hidden @code{nodist_} and @code{nobase_}
address@hidden dist_
address@hidden nodist_
@samp{nobase_} should be specified first when used in conjunction with
either @samp{dist_} or @samp{nodist_} (@pxref{Dist}). For instance:
@@ -2539,8 +2544,8 @@
@section Nesting Packages
@cindex Nesting packages
@cindex Subpackages
address@hidden AC_CONFIG_SUBDIRS
address@hidden AC_CONFIG_AUX_DIR
address@hidden AC_CONFIG_SUBDIRS
address@hidden AC_CONFIG_AUX_DIR
In the GNU Build System, packages can be nested to arbitrary depth.
@@ -2686,7 +2691,8 @@
@node Program Sources
@subsection Defining program sources
address@hidden PROGRAMS, bindir
address@hidden @code{PROGRAMS}, @code{bindir}
address@hidden _PROGRAMS
@vindex bin_PROGRAMS
@vindex sbin_PROGRAMS
@vindex libexec_PROGRAMS
@@ -2725,9 +2731,10 @@
This causes each mentioned @samp{.c} file to be compiled into the
corresponding @samp{.o}. Then all are linked to produce @file{hello}.
address@hidden _SOURCES primary, defined
address@hidden SOURCES primary, defined
address@hidden Primary variable, SOURCES
address@hidden @code{_SOURCES} primary, defined
address@hidden @code{SOURCES} primary, defined
address@hidden Primary variable, @code{SOURCES}
address@hidden _SOURCES
If @samp{hello_SOURCES} is not specified, then it defaults to the single
file @file{hello.c} (@pxref{Default _SOURCES}).
@@ -2738,8 +2745,8 @@
can share a single source file, which must be listed in each
@samp{_SOURCES} definition.
address@hidden Header files in _SOURCES
address@hidden _SOURCES and header files
address@hidden Header files in @code{_SOURCES}
address@hidden @code{_SOURCES} and header files
Header files listed in a @samp{_SOURCES} definition will be included in
the distribution but otherwise ignored. In case it isn't obvious, you
@@ -2760,7 +2767,7 @@
@vindex LDADD
@vindex AM_LDFLAGS
address@hidden prog_LDADD, defined
address@hidden @code{prog_LDADD}, defined
Sometimes, multiple programs are built in one directory but do not share
the same link-time requirements. In this case, you can use the
@@ -2769,7 +2776,7 @@
written in lowercase) to override the global @code{LDADD}. If this
variable exists for a given program, then that program is not linked
using @code{LDADD}.
address@hidden _LDADD
address@hidden maude_LDADD
For instance, in GNU cpio, @code{pax}, @code{cpio} and @code{mt} are
linked against the library @file{libcpio.a}. However, @code{rmt} is
@@ -2791,16 +2798,15 @@
rmt_SOURCES = @dots{}
@end example
address@hidden _LDFLAGS, defined
-
address@hidden @code{_LDFLAGS}, defined
address@hidden maude_LDFLAGS
@address@hidden is inappropriate for passing program-specific
linker flags (except for @samp{-l}, @samp{-L}, @samp{-dlopen} and
@samp{-dlpreopen}). So, use the @address@hidden variable for
this purpose.
address@hidden _LDFLAGS
-
address@hidden _DEPENDENCIES, defined
address@hidden @code{_DEPENDENCIES}, defined
address@hidden maude_DEPENDENCIES
It is also occasionally useful to have a program depend on some other
target which is not actually part of that program. This can be done
using the @address@hidden variable. Each program depends
@@ -2832,7 +2838,7 @@
@subsubsection Conditional compilation using @code{_LDADD} substitutions
address@hidden EXTRA_prog_SOURCES, defined
address@hidden @code{EXTRA_prog_SOURCES}, defined
Automake must know all the source files that could possibly go into a
program, even if not all the files are built in every circumstance. Any
@@ -2916,14 +2922,14 @@
@subsubsection Conditional programs using @code{configure} substitutions
address@hidden EXTRA_PROGRAMS
address@hidden @code{EXTRA_PROGRAMS}, defined
In this case, you must notify Automake of all the programs that can
possibly be built, but at the same time cause the generated
@file{Makefile.in} to use the programs specified by @code{configure}.
This is done by having @code{configure} substitute values into each
@samp{_PROGRAMS} definition, while listing all optionally built programs
in @code{EXTRA_PROGRAMS}.
address@hidden EXTRA_PROGRAMS
address@hidden EXTRA_PROGRAMS, defined
@example
bin_PROGRAMS = cpio pax $(MT)
@@ -2959,9 +2965,10 @@
@node A Library
@section Building a library
address@hidden _LIBRARIES primary, defined
address@hidden LIBRARIES primary, defined
address@hidden Primary variable, LIBRARIES
address@hidden @code{_LIBRARIES} primary, defined
address@hidden @code{LIBRARIES} primary, defined
address@hidden Primary variable, @code{LIBRARIES}
address@hidden _LIBRARIES
@vindex lib_LIBRARIES
@vindex pkglib_LIBRARIES
@@ -2988,15 +2995,10 @@
variable corresponding to @file{liblob.a} is @samp{liblob_a_SOURCES},
not @samp{liblob.a_SOURCES}.
address@hidden _LIBADD primary, defined
address@hidden LIBADD primary, defined
address@hidden Primary variable, LIBADD
-
address@hidden maude_LIBADD
Extra objects can be added to a library using the
@address@hidden variable. This should be used for objects
determined by @code{configure}. Again from @code{cpio}:
address@hidden _LIBADD
address@hidden LIBADD
@example
libcpio_a_LIBADD = $(LIBOBJS) $(ALLOCA)
@@ -3043,10 +3045,10 @@
@node Libtool Concept
@subsection The Libtool Concept
address@hidden libtool, introduction
address@hidden @command{libtool}, introduction
@cindex libtool library, definition
address@hidden suffix .la, defined
address@hidden .la suffix, defined
address@hidden suffix @file{.la}, defined
address@hidden @file{.la} suffix, defined
Libtool abstracts shared and static libraries into a unified
concept henceforth called @dfn{libtool libraries}. Libtool libraries
@@ -3058,7 +3060,7 @@
tune the default, @xref{AC_PROG_LIBTOOL, , The @code{AC_PROG_LIBTOOL}
macro, libtool, The Libtool Manual}.)
address@hidden suffix .lo, defined
address@hidden suffix @file{.lo}, defined
Because object files for shared and static libraries must be compiled
differently, libtool is also used during compilation. Object files
built by libtool are called @dfn{libtool objects}: these are files
@@ -3075,7 +3077,7 @@
building source files conditionally (@pxref{Conditional Libtool
Sources}).
address@hidden libltdl, introduction
address@hidden @file{libltdl}, introduction
People considering writing a plug-in system, with dynamically loaded
modules, should look into @file{libltdl}: libtool's dlopening library
@@ -3091,12 +3093,13 @@
@node Libtool Libraries
@subsection Building Libtool Libraries
address@hidden _LTLIBRARIES primary, defined
address@hidden LTLIBRARIES primary, defined
address@hidden Primary variable, LTLIBRARIES
address@hidden @code{_LTLIBRARIES} primary, defined
address@hidden @code{LTLIBRARIES} primary, defined
address@hidden Primary variable, @code{LTLIBRARIES}
@cindex Example of shared libraries
@vindex lib_LTLIBRARIES
@vindex pkglib_LTLIBRARIES
address@hidden _LTLIBRARIES
Automake uses libtool to build libraries declared with the
@samp{LTLIBRARIES} primary. Each @samp{_LTLIBRARIES} variable is a
@@ -3310,7 +3313,7 @@
@subsection Libtool Modules
@cindex modules, libtool
@cindex libtool modules
address@hidden -module, libtool
address@hidden @code{-module}, libtool
These are libtool libraries meant to be dlopened. They are
indicated to libtool by passing @code{-module} at link-time.
@@ -3340,8 +3343,8 @@
@node Libtool Flags
@subsection _LIBADD and _LDFLAGS
address@hidden _LIBADD, libtool
address@hidden _LDFLAGS, libtool
address@hidden @code{_LIBADD}, libtool
address@hidden @code{_LDFLAGS}, libtool
As shown in previous sections, the @address@hidden
variable should be used to list extra libtool objects (@file{.lo}
@@ -3362,7 +3365,7 @@
@vindex LIBOBJS
@vindex LTALLOCA
@vindex ALLOCA
address@hidden AC_LIBOBJ
address@hidden AC_LIBOBJ
Where an ordinary library might include @code{$(LIBOBJS)} or
@code{$(ALLOCA)} (@pxref{LIBOBJS}), a libtool library must use
@@ -3378,12 +3381,12 @@
@subsection Common Issues Related to Libtool's Use
@subsubsection @code{required file `./ltmain.sh' not found}
address@hidden ltmain.sh not found
address@hidden libtoolize, no longer run by Automake
address@hidden libtoolize and autoreconf
address@hidden autoreconf and libtoolize
address@hidden bootstrap.sh and autoreconf
address@hidden autogen.sh and autoreconf
address@hidden @file{ltmain.sh} not found
address@hidden @command{libtoolize}, no longer run by @command{automake}
address@hidden @command{libtoolize} and @command{autoreconf}
address@hidden @command{autoreconf} and @command{libtoolize}
address@hidden @file{bootstrap.sh} and @command{autoreconf}
address@hidden @file{autogen.sh} and @command{autoreconf}
Libtool comes with a tool called @command{libtoolize} that will
install libtool's supporting files into a package. Running this
@@ -3474,7 +3477,7 @@
libraries; the documentation below notes situations where programs and
libraries differ.
address@hidden @samp
address@hidden @samp
@item maude_SOURCES
This variable, if it exists, lists all the source files which are
compiled to build the program. These files are added to the
@@ -3665,7 +3668,7 @@
This facility is rarely needed in practice,
and we recommend avoiding it until you find it is required.
address@hidden table
address@hidden vtable
@node Default _SOURCES
@section Default @code{_SOURCES}
@@ -3758,7 +3761,7 @@
implementation for functions that are missing or broken on the host
system. They are substituted by @file{configure}.
address@hidden AC_LIBOBJ
address@hidden AC_LIBOBJ
These variables are defined by Autoconf macros such as
@code{AC_LIBOBJ}, @code{AC_REPLACE_FUNCS} (@pxref{Generic Functions, ,
@@ -3768,7 +3771,7 @@
macros call @code{AC_LIBOBJ} or @code{AC_REPLACE_FUNCS} to
populate @code{$(LIBOBJS)}.
address@hidden AC_LIBSOURCE
address@hidden AC_LIBSOURCE
Using these variables is very similar to doing conditional compilation
using @code{AC_SUBST} variables, as described in @ref{Conditional
@@ -3804,7 +3807,7 @@
AC_OUTPUT
@end example
address@hidden AC_CONFIG_LIBOBJ_DIR
address@hidden AC_CONFIG_LIBOBJ_DIR
The @code{AC_CONFIG_LIBOBJ_DIR} tells Autoconf that the source files
of these object files are to be found in the @file{lib/} directory.
@@ -3962,6 +3965,8 @@
the macro @samp{AC_PROG_YACC} (@pxref{Particular Programs, , Particular
Program Checks, autoconf, The Autoconf Manual}).
address@hidden YFLAGS
address@hidden AM_YFLAGS
When @code{yacc} is invoked, it is passed @samp{YFLAGS} and
@samp{AM_YFLAGS}. The former is a user variable and the latter is
intended for the @file{Makefile.am} author.
@@ -3989,6 +3994,8 @@
autoconf, The Autoconf Manual}), but using @code{AM_PROG_LEX} macro
(@pxref{Macros}) is recommended.
address@hidden LFLAGS
address@hidden AM_LFLAGS
When @code{lex} is invoked, it is passed @samp{LFLAGS} and
@samp{AM_LFLAGS}. The former is a user variable and the latter is
intended for the @file{Makefile.am} author.
@@ -3998,11 +4005,11 @@
@code{maintainer-mode} is enabled, or when the files have been erased.
address@hidden ylwrap
address@hidden yacc, multiple parsers
address@hidden Multiple yacc parsers
address@hidden Multiple lex lexers
address@hidden lex, multiple lexers
address@hidden @command{ylwrap}
address@hidden @command{yacc}, multiple parsers
address@hidden Multiple @command{yacc} parsers
address@hidden Multiple @command{lex} lexers
address@hidden @command{lex}, multiple lexers
Automake makes it possible to include multiple @code{yacc} (or
@@ -4112,19 +4119,22 @@
of assembler files: normal (@file{*.s}) and preprocessed by @code{CPP}
(@file{*.S}).
-The variable @code{CCAS} holds the name of the compiler used to build
-assembly code. This compiler must work a bit like a C compiler; in
-particular it must accept @samp{-c} and @samp{-o}. The value of
address@hidden (and @code{CPPFLAGS} for preprocessed files) is passed
-to the compilation.
@vindex CCAS
@vindex CCASFLAGS
@vindex CPPFLAGS
-
-You are required to set @code{CCAS} and @code{CCASFLAGS} via
address@hidden The autoconf macro @code{AM_PROG_AS} will do this
-for you. Unless they are already set, it simply sets @code{CCAS} to the
-C compiler and @code{CCASFLAGS} to the C compiler flags.
address@hidden AM_CCASFLAGS
address@hidden AM_CPPFLAGS
+The variable @code{CCAS} holds the name of the compiler used to build
+assembly code. This compiler must work a bit like a C compiler; in
+particular it must accept @samp{-c} and @samp{-o}. The values of
address@hidden and @code{AM_CCASFLAGS} (or its per-target
+definition) is passed to the compilation. For preprocessed files,
address@hidden and @code{AM_CPPFLAGS} are also used.
+
+The autoconf macro @code{AM_PROG_AS} will define @code{CCAS} and
address@hidden for you (unless they are already set, it simply sets
address@hidden to the C compiler and @code{CCASFLAGS} to the C compiler
+flags), but you are free to define these variables by other means.
Only the suffixes @file{.s} and @file{.S} are recognized by
@code{automake} as being files containing assembly code.
@@ -4272,7 +4282,8 @@
@samp{-l}) to pass to the automatically selected linker in order to link
in the appropriate Fortran 77 intrinsic and run-time libraries.
address@hidden FLIBS, defined
address@hidden @code{FLIBS}, defined
address@hidden FLIBS
These extra Fortran 77 linker flags are supplied in the output variable
@code{FLIBS} by the @code{AC_F77_LIBRARY_LDFLAGS} Autoconf macro
supplied with newer versions of Autoconf (Autoconf version 2.13 and
@@ -4508,12 +4519,12 @@
code will be formatted in a particular way; see the @code{ansi2knr} man
page for details.
address@hidden AM_C_PROTOTYPES
Support for de-ANSI-fication requires the source files @file{ansi2knr.c}
and @file{ansi2knr.1} to be in the same package as the ANSI C source;
these files are distributed with Automake. Also, the package
@file{configure.ac} must call the macro @code{AM_C_PROTOTYPES}
(@pxref{Macros}).
address@hidden AM_C_PROTOTYPES
Automake also handles finding the @code{ansi2knr} support files in some
other directory in the current package. This is done by prepending the
@@ -4568,7 +4579,7 @@
invoke your compiler, dependency tracking will simply be disabled for
your build.
address@hidden depcomp
address@hidden @command{depcomp}
Experience with earlier versions of Automake (@pxref{Dependency
Tracking Evolution}) taught us that it is not reliable to generate
@@ -4671,9 +4682,10 @@
@node Scripts
@section Executable Scripts
address@hidden _SCRIPTS primary, defined
address@hidden SCRIPTS primary, defined
address@hidden Primary variable, SCRIPTS
address@hidden @code{_SCRIPTS} primary, defined
address@hidden @code{SCRIPTS} primary, defined
address@hidden Primary variable, @code{SCRIPTS}
address@hidden _SCRIPTS
It is possible to define and install programs which are scripts. Such
programs are listed using the @samp{SCRIPTS} primary name. Automake
@@ -4713,7 +4725,7 @@
dist_sbin_SCRIPTS = my_script
@end example
address@hidden SCRIPTS, installation directories
address@hidden @code{SCRIPTS}, installation directories
@cindex Installing scripts
@vindex bin_SCRIPTS
@@ -4734,12 +4746,12 @@
@node Headers
@section Header files
address@hidden _HEADERS primary, defined
address@hidden HEADERS primary, defined
address@hidden Primary variable, HEADERS
-
address@hidden @code{_HEADERS} primary, defined
address@hidden @code{HEADERS} primary, defined
address@hidden Primary variable, @code{HEADERS}
address@hidden _HEADERS
@vindex noinst_HEADERS
address@hidden HEADERS, installation directories
address@hidden @code{HEADERS}, installation directories
@cindex Installing headers
@vindex include_HEADERS
@vindex oldinclude_HEADERS
@@ -4795,9 +4807,10 @@
@node Data
@section Architecture-independent data files
address@hidden _DATA primary, defined
address@hidden DATA primary, defined
address@hidden Primary variable, DATA
address@hidden @code{_DATA} primary, defined
address@hidden @code{DATA} primary, defined
address@hidden Primary variable, @code{DATA}
address@hidden _DATA
Automake supports the installation of miscellaneous data files using the
@samp{DATA} family of variables.
@@ -4850,7 +4863,7 @@
rule to build @file{foo.h} first by lack of dependency information.
@vindex BUILT_SOURCES
address@hidden BUILT_SOURCES, defined
address@hidden @code{BUILT_SOURCES}, defined
The @code{BUILT_SOURCES} variable is a workaround for this problem. A
source file listed in @code{BUILT_SOURCES} is made on @code{make all}
@@ -5102,11 +5115,11 @@
@node Emacs Lisp
@section Emacs Lisp
address@hidden _LISP primary, defined
address@hidden LISP primary, defined
address@hidden Primary variable, LISP
address@hidden @code{_LISP} primary, defined
address@hidden @code{LISP} primary, defined
address@hidden Primary variable, @code{LISP}
address@hidden LISP
address@hidden _LISP
@vindex lisp_LISP
@vindex noinst_LISP
@@ -5184,9 +5197,9 @@
@node Java
@section Java
address@hidden _JAVA primary, defined
address@hidden JAVA primary, defined
address@hidden Primary variable, JAVA
address@hidden @code{_JAVA} primary, defined
address@hidden @code{JAVA} primary, defined
address@hidden Primary variable, @code{JAVA}
Automake provides some minimal support for Java compilation with the
@samp{JAVA} primary.
@@ -5195,8 +5208,8 @@
compiled with @code{JAVAC} at build time. By default, @file{.class}
files are not included in the distribution.
address@hidden JAVA restrictions
address@hidden Restrictions for JAVA
address@hidden @code{JAVA} restrictions
address@hidden Restrictions for @code{JAVA}
Currently Automake enforces the restriction that only one @samp{_JAVA}
primary can be used in a given @file{Makefile.am}. The reason for this
@@ -5236,10 +5249,10 @@
@node Python
@section Python
address@hidden _PYTHON primary, defined
address@hidden PYTHON primary, defined
address@hidden Primary variable, PYTHON
-
address@hidden @code{_PYTHON} primary, defined
address@hidden @code{PYTHON} primary, defined
address@hidden Primary variable, @code{PYTHON}
address@hidden _PYTHON
Automake provides support for Python compilation with the @samp{PYTHON}
primary.
@@ -5361,13 +5374,15 @@
@node Texinfo
@section Texinfo
address@hidden _TEXINFOS primary, defined
address@hidden TEXINFOS primary, defined
address@hidden Primary variable, TEXINFOS
address@hidden @code{_TEXINFOS} primary, defined
address@hidden @code{TEXINFOS} primary, defined
address@hidden Primary variable, @code{TEXINFOS}
@cindex HTML output using Texinfo
@cindex PDF output using Texinfo
@cindex PS output using Texinfo
@cindex DVI output using Texinfo
address@hidden _TEXINFOS
address@hidden info_TEXINFOS
If the current directory contains Texinfo source, you must declare it
with the @samp{TEXINFOS} primary. Generally Texinfo files are converted
@@ -5375,8 +5390,6 @@
here. Any Texinfo source file must end in the @file{.texi},
@file{.txi}, or @file{.texinfo} extension. We recommend @file{.texi}
for new manuals.
address@hidden TEXINFOS
address@hidden info_TEXINFOS
Automake generates rules to build @file{.info}, @file{.dvi}, @file{.ps},
@file{.pdf} and @file{.html} files from your Texinfo sources.
@@ -5385,17 +5398,17 @@
The other files can be built on request by @code{make dvi}, @code{make ps},
@code{make pdf} and @code{make html}.
address@hidden Texinfo flag, VERSION
address@hidden Texinfo flag, UPDATED
address@hidden Texinfo flag, EDITION
address@hidden Texinfo flag, UPDATED-MONTH
-
address@hidden VERSION Texinfo flag
address@hidden UPDATED Texinfo flag
address@hidden EDITION Texinfo flag
address@hidden UPDATED-MONTH Texinfo flag
address@hidden Texinfo flag, @code{VERSION}
address@hidden Texinfo flag, @code{UPDATED}
address@hidden Texinfo flag, @code{EDITION}
address@hidden Texinfo flag, @code{UPDATED-MONTH}
+
address@hidden @code{VERSION} Texinfo flag
address@hidden @code{UPDATED} Texinfo flag
address@hidden @code{EDITION} Texinfo flag
address@hidden @code{UPDATED-MONTH} Texinfo flag
address@hidden mdate-sh
address@hidden @file{mdate-sh}
If the @file{.texi} file @code{@@include}s @file{version.texi}, then
that file will be automatically generated. The file @file{version.texi}
@@ -5439,7 +5452,7 @@
hello_TEXINFOS = gpl.texi
@end example
address@hidden texinfo.tex
address@hidden @file{texinfo.tex}
By default, Automake requires the file @file{texinfo.tex} to appear in
the same directory as the Texinfo source (this can be changed using the
@@ -5456,12 +5469,10 @@
@code{TEXINFO_TEX} is preferable, however, because that allows the
@code{dvi}, @code{ps}, and @code{pdf} targets to still work.
address@hidden Rule, install-info
address@hidden Rule, noinstall-info
address@hidden Target, install-info
address@hidden Target, noinstall-info
address@hidden install-info target
address@hidden noinstall-info target
address@hidden Option, @code{noinstall-info}
address@hidden Target, @code{install-info}
address@hidden @code{install-info} target
address@hidden @code{noinstall-info} option
@opindex no-installinfo
@trindex install-info
@@ -5539,17 +5550,17 @@
@node Man pages
@section Man pages
address@hidden _MANS primary, defined
address@hidden MANS primary, defined
address@hidden Primary variable, MANS
address@hidden @code{_MANS} primary, defined
address@hidden @code{MANS} primary, defined
address@hidden Primary variable, @code{MANS}
address@hidden _MANS
address@hidden man_MANS
A package can also include man pages (but see the GNU standards on this
matter, @ref{Man Pages, , , standards, The GNU Coding Standards}.) Man
pages are declared using the @samp{MANS} primary. Generally the
@code{man_MANS} variable is used. Man pages are automatically installed in
the correct subdirectory of @code{mandir}, based on the file extension.
address@hidden MANS
address@hidden man_MANS
File extensions such as @samp{.1c} are handled by looking for the valid
part of the extension and using that to determine the correct
@@ -5574,12 +5585,12 @@
In this case, @file{rename.man} will be renamed to @file{rename.1} when
installed, but the other files will keep their names.
address@hidden Rule, install-man
address@hidden Rule, noinstall-man
address@hidden Target, install-man
address@hidden Target, noinstall-man
address@hidden install-man target
address@hidden noinstall-man target
address@hidden Target, @code{install-man}
address@hidden Option, @code{noinstall-man}
address@hidden @code{install-man} target
address@hidden @code{noinstall-man} option
address@hidden no-installman
address@hidden install-man
@c Use @samp{make install} per documentation: (texi)code.
By default, man pages are installed by @samp{make install}. However,
@@ -5588,11 +5599,9 @@
@code{no-installman} option will prevent the man pages from being
installed by default. The user can still explicitly install them via
@samp{make install-man}.
address@hidden no-installman
address@hidden install-man
-Here is how the man pages are handled in GNU @code{cpio} (which includes
-both Texinfo documentation and man pages):
+Here is how the man pages are handled in GNU @command{cpio} (which
+includes both Texinfo documentation and man pages):
@example
man_MANS = cpio.1 mt.1
@@ -5612,7 +5621,7 @@
@chapter What Gets Installed
@cindex Installation support
address@hidden make install support
address@hidden @code{make install} support
@section Basics of installation
@@ -5742,7 +5751,7 @@
@node Clean
@chapter What Gets Cleaned
address@hidden make clean support
address@hidden @code{make clean} support
The GNU Makefile Standards specify a number of different clean rules.
See @xref{Standard Targets, , Standard Targets for Users, standards,
@@ -5807,20 +5816,25 @@
@section Basics of distribution
address@hidden make dist
address@hidden @code{make dist}
address@hidden PACKAGE
address@hidden VERSION
address@hidden dist
The @code{dist} rule in the generated @file{Makefile.in} can be used
to generate a gzip'd @code{tar} file and other flavors of archive for
distribution. The files is named based on the @samp{PACKAGE} and
@samp{VERSION} variables defined by @code{AM_INIT_AUTOMAKE}
(@pxref{Macros}); more precisely the gzip'd @code{tar} file is named
@address@hidden@var{version}.tar.gz}.
address@hidden PACKAGE
address@hidden VERSION
address@hidden dist
address@hidden GZIP_ENV
You can use the @code{make} variable @samp{GZIP_ENV} to control how gzip
is run. The default setting is @samp{--best}.
address@hidden @code{m4_include}, distribution
address@hidden @code{include}, distribution
address@hidden m4_include
address@hidden include
For the most part, the files to distribute are automatically found by
Automake: all source files are automatically included in a distribution,
as are all @file{Makefile.am}s and @file{Makefile.in}s. Automake also
@@ -5835,8 +5849,7 @@
helper scripts installed with @samp{automake --add-missing} are also
distributed.
address@hidden m4_include, distribution
-
address@hidden EXTRA_DIST
Still, sometimes there are files which must be distributed, but which
are not covered in the automatic rules. These files should be listed in
the @code{EXTRA_DIST} variable. You can mention files from
@@ -5847,8 +5860,9 @@
Please note that this will also copy @emph{everything} in the directory,
including CVS/RCS version control files. We recommend against using
this feature.
address@hidden EXTRA_DIST
address@hidden SUBDIRS
address@hidden DIST_SUBDIRS
If you define @code{SUBDIRS}, Automake will recursively include the
subdirectories in the distribution. If @code{SUBDIRS} is defined
conditionally (@pxref{Conditionals}), Automake will normally include
@@ -5857,11 +5871,12 @@
conditionally, you can set the variable @code{DIST_SUBDIRS} to the
exact list of subdirectories to include in the distribution
(@pxref{Conditional Subdirectories}).
address@hidden DIST_SUBDIRS
@section Fine-grained distribution control
address@hidden dist_
address@hidden nodist_
Sometimes you need tighter control over what does @emph{not} go into the
distribution; for instance you might have source files which are
generated and which you do not want to distribute. In this case
@@ -5870,8 +5885,6 @@
prefixed with @samp{dist_} to add the listed files to the distribution.
Similarly, @samp{nodist_} can be used to omit the files from the
distribution.
address@hidden dist_
address@hidden nodist_
As an example, here is how you would cause some data to be distributed
while leaving some source code out of the distribution:
@@ -5934,25 +5947,26 @@
@section Checking the distribution
address@hidden make distcheck
address@hidden make distcleancheck
address@hidden @code{make distcheck}
address@hidden @code{make distcleancheck}
@vindex distcleancheck_listfiles
address@hidden make distuninstallcheck
address@hidden @code{make distuninstallcheck}
@vindex distuninstallcheck_listfiles
address@hidden distcheck
Automake also generates a @code{distcheck} rule which can be of help
to ensure that a given distribution will actually work.
@code{distcheck} makes a distribution, then tries to do a @code{VPATH}
build, run the test suite, and finally make another tarfile to ensure the
distribution is self-contained.
address@hidden distcheck
address@hidden DISTCHECK_CONFIGURE_FLAGS
Building the package involves running @code{./configure}. If you need
to supply additional flags to @code{configure}, define them in the
@code{DISTCHECK_CONFIGURE_FLAGS} variable, either in your top-level
@file{Makefile.am}, or on the command line when invoking @code{make}.
address@hidden DISTCHECK_CONFIGURE_FLAGS
address@hidden distcheck-hook
If the @code{distcheck-hook} rule is defined in your top-level
@file{Makefile.am}, then it will be invoked by @code{distcheck} after
the new distribution has been unpacked, but before the unpacked copy
@@ -5964,7 +5978,9 @@
@file{Makefile.am}, but the @code{DISTCHECK_CONFIGURE_FLAGS} are
passed down to the @code{configure} script of the subpackage.
-
address@hidden distcleancheck
address@hidden DISTCLEANFILES
address@hidden distcleancheck_listfiles
Speaking about potential distribution errors, @code{distcheck} will also
ensure that the @code{distclean} rule actually removes all built
files. This is done by running @code{make distcleancheck} at the end of
@@ -5973,7 +5989,6 @@
running @code{$(distcleancheck_listfiles)}. Usually this check will
find generated files that you forgot to add to the @code{DISTCLEANFILES}
variable (@pxref{Clean}).
address@hidden distcleancheck
The @code{distcleancheck} behavior should be OK for most packages,
otherwise you have the possibility to override the definition of
@@ -5981,7 +5996,6 @@
@code{$(distcleancheck_listfiles)} variable. For instance to disable
@code{distcleancheck} completely, add the following rule to your
top-level @file{Makefile.am}:
address@hidden distcleancheck_listfiles
@example
distcleancheck:
@@ -6063,7 +6077,8 @@
@chapter Support for test suites
@cindex Test suites
address@hidden make check
address@hidden @code{make check}
address@hidden check
Automake supports two forms of test suites.
@@ -6167,7 +6182,7 @@
Automake generates rules to automatically rebuild @file{Makefile}s,
@file{configure}, and other derived files like @file{Makefile.in}.
address@hidden AM_MAINTAINER_MODE
address@hidden AM_MAINTAINER_MODE
If you are using @code{AM_MAINTAINER_MODE} in @file{configure.ac}, then
these automatic rebuilding rules are only enabled in maintainer mode.
@@ -6271,17 +6286,22 @@
@itemx @code{gnu}
@itemx @code{foreign}
@itemx @code{cygnus}
address@hidden Option, gnits
address@hidden Option, gnu
address@hidden Option, foreign
address@hidden Option, cygnus
address@hidden Option, @code{gnits}
address@hidden Option, @code{gnu}
address@hidden Option, @code{foreign}
address@hidden Option, @code{cygnus}
address@hidden gnits
address@hidden gnu
address@hidden foreign
address@hidden cygnus
Set the strictness as appropriate. The @code{gnits} option also implies
@code{readme-alpha} and @code{check-news}.
@item @code{ansi2knr}
@itemx @address@hidden/ansi2knr}
address@hidden Option, ansi2knr
address@hidden Option, @code{ansi2knr}
address@hidden ansi2knr
Turn on automatic de-ANSI-fication. @xref{ANSI}. If preceded by a
path, the generated @file{Makefile.in} will look in the specified
directory to find the @file{ansi2knr} program. The path should be a
@@ -6289,37 +6309,43 @@
currently does not check this).
@item @code{check-news}
address@hidden Option, check-news
address@hidden Option, @code{check-news}
address@hidden check-news
Cause @code{make dist} to fail unless the current version number appears
in the first few lines of the @file{NEWS} file.
@item @code{dejagnu}
address@hidden Option, dejagnu
address@hidden Option, @code{dejagnu}
address@hidden dejagnu
Cause @code{dejagnu}-specific rules to be generated. @xref{Tests}.
@item @code{dist-bzip2}
address@hidden Option, dist-bzip2
address@hidden Option, @code{dist-bzip2}
address@hidden dist-bzip2
Hook @code{dist-bzip2} to @code{dist}.
@trindex dist-bzip2
@item @code{dist-shar}
address@hidden Option, dist-shar
address@hidden Option, @code{dist-shar}
address@hidden dist-shar
Hook @code{dist-shar} to @code{dist}.
@trindex dist-shar
@item @code{dist-zip}
address@hidden Option, dist-zip
address@hidden Option, @code{dist-zip}
address@hidden dist-zip
Hook @code{dist-zip} to @code{dist}.
@trindex dist-zip
@item @code{dist-tarZ}
address@hidden Option, dist-tarZ
address@hidden Option, @code{dist-tarZ}
address@hidden dist-tarZ
Hook @code{dist-tarZ} to @code{dist}.
@trindex dist-tarZ
@item @code{filename-length-max=99}
address@hidden Option, filename-length-max=99
address@hidden filename-length-max=99
address@hidden Option, @code{filename-length-max=99}
address@hidden filename-length-max=99
Abort if filenames longer than 99 characters are found during
@code{make dist}. Such long filenames are generally considered not to
be portable in tarballs. See the @code{tar-v7} and @code{tar-ustar}
@@ -6328,30 +6354,35 @@
@file{configure.ac}, it will be ignored otherwise.
@item @code{no-define}
address@hidden Option, no-define
address@hidden Option, @code{no-define}
address@hidden no-define
This options is meaningful only when passed as an argument to
@code{AM_INIT_AUTOMAKE}. It will prevent the @code{PACKAGE} and
@code{VERSION} variables to be @code{AC_DEFINE}d.
@item @code{no-dependencies}
address@hidden Option, no-dependencies
address@hidden Option, @code{no-dependencies}
address@hidden no-dependencies
This is similar to using @samp{--include-deps} on the command line, but
is useful for those situations where you don't have the necessary bits
to make automatic dependency tracking work @xref{Dependencies}. In this
case the effect is to effectively disable automatic dependency tracking.
@item @code{no-dist}
address@hidden Option, no-dist
address@hidden Option, @code{no-dist}
address@hidden no-dist
Don't emit any code related to @code{dist} target. This is useful
when a package has its own method for making distributions.
@item @code{no-dist-gzip}
address@hidden Option, no-dist-gzip
address@hidden Option, @code{no-dist-gzip}
address@hidden no-dist-gzip
Do not hook @code{dist-gzip} to @code{dist}.
@trindex no-dist-gzip
@item @code{no-exeext}
address@hidden Option, no-exeext
address@hidden Option, @code{no-exeext}
address@hidden no-exeext
If your @file{Makefile.am} defines a rule for target @samp{foo}, it
will override a rule for a target named @samp{foo$(EXEEXT)}. This is
necessary when @code{EXEEXT} is found to be empty. However, by
@@ -6362,7 +6393,8 @@
executables.
@item @code{no-installinfo}
address@hidden Option, no-installinfo
address@hidden Option, @code{no-installinfo}
address@hidden no-installinfo
The generated @file{Makefile.in} will not cause info pages to be built
or installed by default. However, @code{info} and @code{install-info}
targets will still be available. This option is disallowed at
@@ -6371,7 +6403,8 @@
@trindex install-info
@item @code{no-installman}
address@hidden Option, no-installman
address@hidden Option, @code{no-installman}
address@hidden no-installman
The generated @file{Makefile.in} will not cause man pages to be
installed by default. However, an @code{install-man} target will still
be available for optional installation. This option is disallowed at
@@ -6379,17 +6412,20 @@
@trindex install-man
@item @code{nostdinc}
address@hidden Option, nostdinc
address@hidden Option, @code{nostdinc}
address@hidden nostdinc
This option can be used to disable the standard @samp{-I} options which
are ordinarily automatically provided by Automake.
@item @code{no-texinfo.tex}
address@hidden Option, no-texinfo
address@hidden Option, @code{no-texinfo.tex}
address@hidden no-texinfo.tex
Don't require @file{texinfo.tex}, even if there are texinfo files in
this directory.
@item @code{readme-alpha}
address@hidden Option, readme-alpha
address@hidden Option, @code{readme-alpha}
address@hidden readme-alpha
If this release is an alpha release, and the file @file{README-alpha}
exists, then it will be added to the distribution. If this option is
given, version numbers are expected to follow one of two forms. The
@@ -6400,8 +6436,12 @@
letter; it should be omitted for non-alpha releases.
@item @code{std-options}
address@hidden Options, std-options
address@hidden make installcheck
address@hidden Options, @code{std-options}
address@hidden @code{make installcheck}, testing @code{--help} and
@code{--version}
address@hidden @code{--help} check
address@hidden @code{--version} check
address@hidden std-options
+
Make the @code{installcheck} rule check that installed scripts and
programs support the @code{--help} and @code{--version} options.
This also provides a basic check that the program's
@@ -6425,6 +6465,8 @@
@end example
@item @code{subdir-objects}
address@hidden Options, @code{subdir-objects}
address@hidden subdir-objects
If this option is specified, then objects are placed into the
subdirectory of the build directory corresponding to the subdirectory of
the source file. For instance if the source file is
@@ -6437,16 +6479,16 @@
@item @code{tar-v7}
@itemx @code{tar-ustar}
@itemx @code{tar-pax}
address@hidden Option, tar-v7
address@hidden Option, tar-ustar
address@hidden Option, tar-pax
address@hidden tar formats
address@hidden v7 tar format
address@hidden Option, @code{tar-v7}
address@hidden Option, @code{tar-ustar}
address@hidden Option, @code{tar-pax}
address@hidden @command{tar} formats
address@hidden v7 @command{tar} format
@cindex ustar format
@cindex pax format
address@hidden tar-v7
address@hidden tar-ustar
address@hidden tar-pax
address@hidden tar-v7
address@hidden tar-ustar
address@hidden tar-pax
These three mutually exclusive options select the tar format to use
when generating tarballs with @code{make dist}. (The tar file created
@@ -6493,13 +6535,15 @@
package can still be built), but @code{make dist} will fail.
@item @var{version}
address@hidden Option, version
address@hidden Option, @var{version}
A version number (e.g. @samp{0.30}) can be specified. If Automake is not
newer than the version specified, creation of the @file{Makefile.in}
will be suppressed.
@item @address@hidden or @address@hidden
@cindex Option, warnings
address@hidden Option, @address@hidden
address@hidden Option, @address@hidden
These options behave exactly like their command-line counterpart
(@pxref{Invoking Automake}). This allows you to enable or disable some
warning categories on a per-file basis. You can also setup some warnings
@@ -6530,7 +6574,7 @@
@node Tags
@section Interfacing to @code{etags}
address@hidden TAGS support
address@hidden @file{TAGS} support
Automake will generate rules to generate @file{TAGS} files for use with
GNU Emacs under some circumstances.
@@ -6593,8 +6637,8 @@
@node Suffixes
@section Handling new file extensions
address@hidden Adding new SUFFIXES
address@hidden SUFFIXES, adding
address@hidden Adding new @code{SUFFIXES}
address@hidden @code{SUFFIXES}, adding
@vindex SUFFIXES
It is sometimes useful to introduce a new implicit rule to handle a file
@@ -6659,8 +6703,8 @@
@chapter Include
@cmindex include
address@hidden Including Makefile fragment
address@hidden Makefile fragment, including
address@hidden Including @file{Makefile} fragment
address@hidden @file{Makefile} fragment, including
Automake supports an @code{include} directive which can be used to
include other @file{Makefile} fragments when @code{automake} is run.
@@ -6692,7 +6736,7 @@
Automake supports a simple type of conditionals.
address@hidden AM_CONDITIONAL
address@hidden AM_CONDITIONAL
Before using a conditional, you must define it by using
@code{AM_CONDITIONAL} in the @code{configure.ac} file (@pxref{Macros}).
@@ -6710,9 +6754,9 @@
will confuse automake.
@end defmac
address@hidden --enable-debug, example
address@hidden Example conditional --enable-debug
address@hidden Conditional example, --enable-debug
address@hidden @code{--enable-debug}, example
address@hidden Example conditional @code{--enable-debug}
address@hidden Conditional example, @code{--enable-debug}
Conditionals typically depend upon options which the user provides to
the @code{configure} script. Here is an example of how to write a
@@ -6781,8 +6825,8 @@
@node Gnits
@chapter The effect of @code{--gnu} and @code{--gnits}
address@hidden --gnu, required files
address@hidden --gnu, complete description
address@hidden @code{--gnu}, required files
address@hidden @code{--gnu}, complete description
The @samp{--gnu} option (or @samp{gnu} in the @samp{AUTOMAKE_OPTIONS}
variable) causes @code{automake} to check the following:
@@ -6805,7 +6849,7 @@
rules; for instance in the future @code{pathchk} might be required for
@samp{make dist}.
address@hidden --gnits, complete description
address@hidden @code{--gnits}, complete description
The @samp{--gnits} option does everything that @samp{--gnu} does, and
checks the following as well:
@@ -6826,7 +6870,7 @@
@c FIXME xref when standards are finished
@item
address@hidden README-alpha
address@hidden @file{README-alpha}
If @samp{VERSION} indicates that this is an alpha release, and the file
@file{README-alpha} appears in the topmost directory of a package, then
it is included in the distribution. This is done in @samp{--gnits}
@@ -6843,7 +6887,7 @@
@node Cygnus
@chapter The effect of @code{--cygnus}
address@hidden Cygnus strictness
address@hidden @code{cygnus} strictness
Some packages, notably GNU GCC and GNU gdb, have a build environment
originally written at Cygnus Support (subsequently renamed Cygnus
@@ -6955,7 +6999,7 @@
possible to append new dependencies to an @code{automake}-defined
target without redefining the entire rule.
address@hidden -local targets
address@hidden @code{-local} targets
@cindex local targets
However, various useful targets have a @samp{-local} version you can
@@ -7010,7 +7054,7 @@
$(INSTALL_DATA) $(srcdir)/afile $(DESTDIR)/etc/afile
@end example
address@hidden -hook targets
address@hidden @code{-hook} targets
@cindex hook targets
Some rule also have a way to run another rule, called a @dfn{hook},
@@ -7042,7 +7086,7 @@
@cindex versioned binaries, installing
@cindex installing versioned binaries
address@hidden LN_S example
address@hidden @code{LN_S} example
For instance, here is how you could install a versioned copy of a
program using @code{$(LN_S)}:
@@ -7217,10 +7261,10 @@
subdir && $(MAKE) $(AM_MAKEFLAGS) target} (if it's OK to store the
subdirectory project one directory deeper). The good news is that
this proxy @file{Makefile} can be generated with Automake. All we
-need are -local targets (@pxref{Extending}) that perform the dispatch.
-Of course the other Automake features are available, so you could
-decide to let Automake perform distribution or installation. Here is
-a possible @file{Makefile.am}:
+need are @code{-local} targets (@pxref{Extending}) that perform the
+dispatch. Of course the other Automake features are available, so you
+could decide to let Automake perform distribution or installation.
+Here is a possible @file{Makefile.am}:
@example
all-local:
@@ -7564,7 +7608,7 @@
@section @command{missing} and @code{AM_MAINTAINER_MODE}
@subsection @command{missing}
address@hidden missing, purpose
address@hidden @command{missing}, purpose
The @command{missing} script is a wrapper around several maintainer
tools, designed to warn users if a maintainer tool is required but
@@ -7593,8 +7637,8 @@
@code{AM_MAINTAINER_MODE} advocates.
@subsection @code{AM_MAINTAINER_MODE}
address@hidden AM_MAINTAINER_MODE, purpose
address@hidden AM_MAINTAINER_MODE
address@hidden @code{AM_MAINTAINER_MODE}, purpose
address@hidden AM_MAINTAINER_MODE
@code{AM_MAINTAINER_MODE} disables the so called "rebuild rules" by
default. If you have @code{AM_MAINTAINER_MODE} in
@@ -7718,7 +7762,8 @@
@node distcleancheck
@section Files left in build directory after distclean
address@hidden distclean, diagnostic
address@hidden @code{distclean}, diagnostic
address@hidden @code{make distclean}, diagnostic
@cindex dependencies and distributed files
@trindex distclean
@trindex distcleancheck
@@ -7886,6 +7931,8 @@
@end display
@subsection Compile Flag Variables
address@hidden Flag Variables, Ordering
address@hidden Compile Flag Variables
@cindex @code{AM_CCASFLAGS} and @code{CCASFLAGS}
@cindex @code{AM_CFLAGS} and @code{CFLAGS}
@cindex @code{AM_CPPFLAGS} and @code{CPPFLAGS}
@@ -9467,12 +9514,18 @@
@appendix Indices
@menu
-* Macro and Variable Index:: Index of Autoconf macros and Automake variables
+* Macro Index:: Index of Autoconf macros
+* Variable Index:: Index of Makefile variables
* General Index:: General index
@end menu
address@hidden Macro and Variable Index
address@hidden Macro and Variable Index
address@hidden Macro Index
address@hidden Macro Index
+
address@hidden fn
+
address@hidden Variable Index
address@hidden Variable Index
@printindex vr
@@ -9492,7 +9545,7 @@
@c LocalWords: dir Automake's ac Dist Gnits gnits cygnus dfn Autoconf's pxref
@c LocalWords: cindex Autoconf autoconf perl samp cvs dist trindex SUBST foo
@c LocalWords: xs emph FIXME ref vindex pkglibdir pkgincludedir pkgdatadir mt
address@hidden LocalWords: pkg libdir cvindex cpio bindir sbindir rmt pax
sbin zar zardir
address@hidden LocalWords: pkg libdir cpio bindir sbindir rmt pax sbin zar
zardir acindex
@c LocalWords: HTML htmldir html noinst TEXINFOS nodist nobase strudel CFLAGS
@c LocalWords: libmumble CC YFLAGS ansi knr itemx de fication config url comp
@c LocalWords: depcomp elisp sh mdate mkinstalldirs mkdir py tex dvi ps pdf
@@ -9561,4 +9614,5 @@
@c LocalWords: syscalls perlhist acl pm multitable headitem fdl appendixsec
@c LocalWords: LTALLOCA MALLOC malloc memcmp strdup alloca libcompat xyz DFOO
@c LocalWords: unprefixed buildable preprocessed DBAZ DDATADIR WARNINGCFLAGS
address@hidden LocalWords: LIBFOOCFLAGS LIBFOOLDFLAGS
address@hidden LocalWords: LIBFOOCFLAGS LIBFOOLDFLAGS ftable maintainerclean
testSubDir
address@hidden LocalWords: barexec Pinard's
--
Alexandre Duret-Lutz
- FYI: doc's indices overhaul,
Alexandre Duret-Lutz <=