diff options
Diffstat (limited to 'doc/automake.texi')
| -rw-r--r-- | doc/automake.texi | 49 |
1 files changed, 31 insertions, 18 deletions
diff --git a/doc/automake.texi b/doc/automake.texi index da0aa2942..2df214a01 100644 --- a/doc/automake.texi +++ b/doc/automake.texi @@ -25,7 +25,7 @@ This manual is for GNU Automake (version @value{VERSION}, @value{UPDATED}), a program that creates GNU standards-compliant Makefiles from template files. -Copyright @copyright{} 1995-2017 Free Software Foundation, Inc. +Copyright @copyright{} 1995-2018 Free Software Foundation, Inc. @quotation Permission is granted to copy, distribute and/or modify this document @@ -2277,7 +2277,7 @@ support new architectures and fix probes broken by changes in new kernel versions. Each new release of Automake comes with up-to-date copies of these programs. If your copy of Automake is getting old, you are encouraged to fetch the latest versions of these files from -@url{http://savannah.gnu.org/git/?group=config} before making a +@url{https://savannah.gnu.org/git/?group=config} before making a release. @item depcomp @@ -2321,7 +2321,7 @@ testsuite harness. Not a program, this file is required for @samp{make dvi}, @samp{make ps} and @samp{make pdf} to work when Texinfo sources are in the package. The latest version can be downloaded from -@url{http://www.gnu.org/software/texinfo/}. +@url{https://www.gnu.org/software/texinfo/}. @item ylwrap This program wraps @command{lex} and @command{yacc} to rename their @@ -2579,6 +2579,11 @@ for more information. Look for Automake data files in directory @var{dir} instead of in the installation directory. This is typically used for debugging. +@vindex AUTOMAKE_LIBDIR +The environment variable @env{AUTOMAKE_LIBDIR} provides another way to +set the directory containing Automake data files. However +@option{--libdir} takes precedence over it. + @item --print-libdir @opindex --print-libdir Print the path of the installation directory containing Automake-provided @@ -3216,6 +3221,11 @@ overridden using the @env{AUTOM4TE} environment variable. Look for the automake-provided macro files in @var{dir} instead of in the installation directory. This is typically used for debugging. +@vindex ACLOCAL_AUTOMAKE_DIR +The environment variable @env{ACLOCAL_AUTOMAKE_DIR} provides another +way to set the directory containing automake-provided macro files. +However @option{--automake-acdir} takes precedence over it. + @item --system-acdir=@var{dir} @opindex --system-acdir Look for the system-wide third-party macro files (and the special @@ -8576,7 +8586,7 @@ to supply additional flags to @command{configure}, define them in the provided there by defining the @code{DISTCHECK_CONFIGURE_FLAGS} variable, on the command line when invoking @command{make}. @c See automake bug#14991 for more details about how the following holds. -It's worth nothing that @command{make distcheck} needs complete control +It's worth noting that @command{make distcheck} needs complete control over the @command{configure} options @option{--srcdir} and @option{--prefix}, so those options cannot be overridden by @code{AM_DISTCHECK_CONFIGURE_FLAGS} nor by @@ -8896,7 +8906,7 @@ Note however that, for tests based on more complex test protocols, the exact effects of @code{XFAIL_TESTS} and @code{DISABLE_HARD_ERRORS} might change, or they might even have no effect at all (for example, @c Keep this in sync with tap-no-disable-hard-errors.sh -in tests using TAP, there is not way to disable hard errors, and the +in tests using TAP, there is no way to disable hard errors, and the @code{DISABLE_HARD_ERRORS} variable has no effect on them). @anchor{Testsuite progress on console} @@ -9164,7 +9174,7 @@ as a side-effect. It's important to note that, differently from what we've seen for the serial test harness (@pxref{Serial Test Harness}), the @code{AM_TESTS_ENVIRONMENT} and @code{TESTS_ENVIRONMENT} variables -@emph{cannot} be use to define a custom test runner; the +@emph{cannot} be used to define a custom test runner; the @code{LOG_COMPILER} and @code{LOG_FLAGS} (or their extension-specific counterparts) should be used instead: @@ -9847,7 +9857,7 @@ a Java-based project implementing both a TAP producer and a TAP consumer. @node DejaGnu Tests @section DejaGnu Tests -If @uref{ftp://ftp.gnu.org/gnu/dejagnu/, @command{dejagnu}} appears in +If @uref{https://ftp.gnu.org/gnu/dejagnu/, @command{dejagnu}} appears in @code{AUTOMAKE_OPTIONS}, then a @command{dejagnu}-based test suite is assumed. The variable @code{DEJATOOL} is a list of names that are passed, one at a time, as the @option{--tool} argument to @@ -10322,20 +10332,23 @@ directories. When using this format, consider using the @option{filename-length-max=99} option to catch file names too long. @option{tar-ustar} selects the ustar format defined by POSIX -1003.1-1988. This format is believed to be old enough to be portable. +1003.1-1988. This format is old enough to be portable: +As of 2018, it is supported by the native @code{tar} command on +GNU, FreeBSD, NetBSD, OpenBSD, AIX, HP-UX, Solaris, at least. It fully supports empty directories. It can store file names with up to 256 characters, provided that the file name can be split at directory separator in two parts, first of them being at most 155 bytes long. So, in most cases the maximum file name length will be -shorter than 256 characters. However you may run against broken tar -implementations that incorrectly handle file names longer than 99 -characters (please report them to @email{@value{PACKAGE_BUGREPORT}} so we -can document this accurately). +shorter than 256 characters. @option{tar-pax} selects the new pax interchange format defined by POSIX 1003.1-2001. It does not limit the length of file names. However, this format is very young and should probably be restricted to -packages that target only very modern platforms. There are moves to +packages that target only very modern platforms. +As of 2018, this format is supported by the native @code{tar} command only +on GNU, FreeBSD, OpenBSD system; it is not supported by the native +@code{tar} command on NetBSD, AIX, HP-UX, Solaris. +There are moves to change the pax format in an upward-compatible way, so this option may refer to a more recent version in the future. @@ -10451,7 +10464,7 @@ performing @ref{Automatic Rule Rewriting, , VPATH rewrites, autoconf, The Autoconf Manual}). Finally, Automake also emits rules to support the -@uref{http://www.gnu.org/software/global/, GNU Global Tags program}. +@uref{https://www.gnu.org/software/global/, GNU Global Tags program}. The @code{GTAGS} rule runs Global Tags and puts the result in the top build directory. The variable @code{GTAGS_ARGS} holds arguments that are passed to @command{gtags}. @@ -11040,7 +11053,7 @@ If the @option{--add-missing} option is given, @command{automake} will add a generic version of the @file{INSTALL} file as well as the @file{COPYING} file containing the text of the current version of the GNU General Public License existing at the time of this Automake release -(version 3 as this is written, @uref{http://www.gnu.org/@/copyleft/@/gpl.html}). +(version 3 as this is written, @uref{https://www.gnu.org/@/copyleft/@/gpl.html}). However, an existing @file{COPYING} file will never be overwritten by @command{automake}. @@ -13067,8 +13080,8 @@ To make it possible for us to fix a bug, please report it. In order to do so effectively, it helps to know when and how to do it. Before reporting a bug, it is a good idea to see if it is already known. -You can look at the @uref{http://debbugs.gnu.org/, GNU Bug Tracker} -and the @uref{http://lists.gnu.org/@/archive/@/html/@/bug-automake/, +You can look at the @uref{https://debbugs.gnu.org/, GNU Bug Tracker} +and the @uref{https://lists.gnu.org/@/archive/@/html/@/bug-automake/, bug-automake mailing list archives} for previous bug reports. We previously used a @uref{http://sourceware.org/@/cgi-bin/@/gnatsweb.pl?database=automake, @@ -13087,7 +13100,7 @@ features. For a bug report, a feature request or other suggestions, please send email to @email{@value{PACKAGE_BUGREPORT}}. This will then open a new -bug in the @uref{http://debbugs.gnu.org/@/automake, bug tracker}. Be +bug in the @uref{https://debbugs.gnu.org/@/automake, bug tracker}. Be sure to include the versions of Autoconf and Automake that you use. Ideally, post a minimal @file{Makefile.am} and @file{configure.ac} that reproduces the problem you encounter. If you have encountered test |