summaryrefslogtreecommitdiff
path: root/doc
Commit message (Collapse)AuthorAgeFilesLines
* multilib: deprecate, will be moved to contribStefano Lattarini2012-01-211-21/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As of 2012-01-17, according to Google codesarch, almost no active package is using the 'multilib' feature offered by automake. The only major exception seems to be GCC... But on a closer look, it become clear that GCC basically carries its own version of multilib support. In fact, Automake syncs its 'config-ml.in' and 'symlink-tree' scripts from GCC; and the GCC repository contains a version of the 'multi.m4' file that is *more* updated than the one in the automake repository (the former having being modified the last time in 2008, the latter only in 2006). The 'multilib' feature was anyway hardly documented at all, only being briefly cited in the manual as an "obscure feature", "still experimental", that was only for users "familiar with multilibs" and which "can debug problems they might encounter". We expect such users to be motivated and knowledgeable enough to make the minor adjustments required to start using the contrib version of multilib, if they really need to. * NEWS (Future backward incompatibility): Update. * doc/automake.texi: Deprecate multilib support. State that it will be removed from automake core in the next major release. * m4/multi.m4 (AM_ENABLE_MULTILIB): Deprecate. If called, now gives a proper warning in the 'obsolete' category (while still retaining its former behaviour for the rest). * tests/multilib.test: Update. * contrib/multilib/multi.m4: New, verbatim copy of the earlier version of multi.m4, without the new deprecation warning. * Makefile.am (fetch): Don't sync the 'config-ml.in' file nor the 'symlink-tree' script from GCC SVN repository anymore. (FETCHFILES): Adjust. (WGET_GCC): Remove, it's not needed anymore.
* docs: deprecate .log -> .html conversion by parallel-testsStefano Lattarini2012-01-161-22/+16
| | | | | | | | | | | | | That feature is to be deprecated in the 1.11.x series, and removed in the 1.12 release. Reference: <http://lists.gnu.org/archive/html/automake/2012-01/msg00005.html> * doc/automake.texi (Simple Tests using parallel-tests): Deprecate the '.log' -> '.html' conversion and the targets 'check-html' and 'recheck-html'. Related rewording and reformatting. * NEWS (Future backward-incompatibilities): Update.
* build: silence automake build systemStefano Lattarini2012-01-151-2/+4
| | | | | | | | | | | | | | | | * configure.ac (AM_SILENT_RULES): Invoke with "yes" as a parameter, to activate silent rules by default. * NEWS: Update. * Makefile.am (sc_perl_syntax): Silence its recipe unconditionally, similarly to what is done for other syntax checks. (release-stats): Be silent by default *but not unconditionally*, thanks to the use of $(AM_V_GEN). (path-check, git-diff): Be silent by default, thanks to the use of $(AM_V_GEN). * m4/Makefile.am ($(top_srcdir)/m4/amversion.m4): Likewise. * doc/Makefile.am ($(srcdir)/amhello-1.0.tar.gz): Likewise. * tests/Makefile.am ($(srcdir)/parallel-tests.am): Likewise. ($(parallel_tests)): Likewise.
* install: pkglibexec_SCRIPTS is a valid prefix/primary combinationStefano Lattarini2012-01-031-1/+2
| | | | | | | | | | | | | | | | | | | | It makes little sense for `libexec_SCRIPTS' to be accepted as valid while `pkglibexec_SCRIPTS' is not. So fix this inconsistency by explicitly allowing `pkglibexec_SCRIPTS' as well. It is worth noting that the inconsistency has been there for a long time, but only the quite recent commit `v1.11-373-g9ca6326' "Warnings about primary/prefix mismatch fixed and extended" has made it noisy enough to be noticed. * automake.in (handle_scripts): Also list `pkglibexec' among the prefixes valid for the `SCRIPTS' primary. * doc/automake.texi (Scripts): Likewise. * tests/primary-prefix-valid-couples.test: Update. * THANKS: Likewise. * NEWS: Likewise. Reported by Dennis Schridde on the automake list: <http://lists.gnu.org/archive/html/automake/2012-01/msg00002.html>
* progs, libs: implement EXTRA_foo_DEPENDENCIESStefano Lattarini2012-01-031-7/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Backported from commit `v1.11-377-g6edafbb'. The feature implemented by that change is quite unobtrusive, so adding it to a maintenance release is acceptable. Also, there have been requests from real-world users for this feature since it has been implemented in master; see automake bug#9320: <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9320> and this short discussion on the automake list: <http://lists.gnu.org/archive/html/automake/2010-11/msg00099.html> It would be a pity to make such users wait even more (until Automake 1.12 is out) before they could start using this feature. Thus we backport it, so that it will appear in the next maintenance version of automake (1.11.3). * automake.in (handle_programs, handle_libraries) (handle_ltlibraries): Mark EXTRA_*_DEPENDENCIES as recognized. * doc/automake.texi (Linking, Program and Library Variables) (LIBOBJS): Document EXTRA_*_DEPENDENCIES. * lib/am/library.am (%LIBRARY%): Also depend on $(EXTRA_%XLIBRARY%_DEPENDENCIES). * lib/am/ltlibrary.am (%LTLIBRARY%): Also depend on (%XLTLIBRARY%_DEPENDENCIES). * lib/am/program.am (%PROGRAM%%EXEEXT%): Also depend on $(EXTRA_%XPROGRAM%_DEPENDENCIES). * tests/extradep.test, tests/extradep2.test: New tests. * tests/Makefile.am (TESTS): Update. * NEWS: Update.
* Merge branch 'deprecate-lzma' into maintStefano Lattarini2012-01-011-3/+3
|\ | | | | | | | | * deprecate-lzma: dist: obsolete support for lzma (superseded by xz and lzip)
| * dist: obsolete support for lzma (superseded by xz and lzip)Stefano Lattarini2012-01-011-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The lzma utilities are today superseded by the xz utilities; in fact, the official site at <http://tukaani.org/lzma/> reads: ``LZMA Utils are legacy data compression software with high compression ratio. LZMA Utils are no longer developed, ... Users of LZMA Utils should move to XZ Utils.'' and the existing automake manual (as of 1.11.2) already says: ``dist-xz Generate an 'xz' tar archive of the distribution. xz archives are frequently smaller than bzip2-compressed archives. The 'xz' format will soon (early 2009) displace the 'lzma' format'' Also, the `dist-lzma' target still suffers of never-solved bugs, due to the too-high compression ratio its uses by default, which might cause an unacceptable memory consumption when one tries to compress or, worse, decompress the created tarballs; see also: <http://lists.gnu.org/archive/html/automake/2011-12/msg00025.html> <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9658> * NEWS: Update. * doc/automake.texi (Dist, Options): State that `dist-lzma' will go away in the next major automake version. * lib/Automake/Options.pm (_process_option_list): Deprecate `dist-lzma'. * tests/lzma.test: Update.
* | Merge branch 'dist-lzip' into maintStefano Lattarini2011-12-311-2/+14
|\ \ | | | | | | | | | | | | * dist-lzip: dist: add support for lzip compression
| * | dist: add support for lzip compressionAntonio Diaz Diaz2011-12-301-2/+14
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * NEWS: Update. * automake.in (handle_dist): Recognize dist-lzip. (make_paragraphs): Map LZIP to dist-lzip. * doc/automake.texi (Dist, Options): Describe dist-lzip. * lib/Automake/Options.pm (_process_option_list): Recognize `dist-lzip'. * lib/am/distdir.am (dist-lzip): New target. (DIST_ARCHIVES) [?LZIP?]: Add `dist-lzip'. (dist, dist-all) [?LZIP?]: Add command to create an lzip-compressed tarball. (distcheck): Handle lzip-compressed tarballs just like the others. * tests/lzip.test: New test. * tests/Makefile.am (TESTS): Add it.
* | docs: fix a couple broken anchorsStefano Lattarini2011-12-301-6/+6
|/ | | | | | | | | | | | | | * doc/automake.texi: In previous commit v1.11-605-g5f71f2b (related to automake bug#8071), we had renamed the chapters about aclocal and automake invocation, and added anchors to the old names as not to break hyperlinks to our on-line manual. Unfortunately, these anchors had been erroneously placed *before* the relevant `@node' commands, instead that just after, so that they ended up pointing to the wrong chapters. Fix this. Since we are at it, tweak the wording of the comments to the anchors to better match that used in the autoconf manual. Report and suggestion by Eric Blake.
* Merge remote-tracking branch 'silent-fixes' into maintStefano Lattarini2011-12-301-10/+15
|\ | | | | | | | | | | | | * origin/silent-fixes: fix: last entry in ChangeLog tests: tweak tests on silent-rules for makes without nested vars silent-rules: fallback for makes without nested vars
| * Merge branch 'maint' into silent-fixesStefano Lattarini2011-12-281-5/+4
| |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | * maint: maint: autogenerate ChangeLog fix: last ChangeLog entry tests: drop unnecessary requirement in 'subpkg.test' gitlog-to-changelog: new auxiliary script, synced from gnulib docs: "aclocal --install -I /abs/dir" actually copies files docs: fix node names for automake and aclocal invocations
| * | silent-rules: fallback for makes without nested varsPaul Eggert2011-12-251-10/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes two problems reported for Automake (Bug#9928, Bug#10237) and is in response to a bug report for building coreutils on HP NonStop OS (Bug#10234). The problem is that HP NonStop 'make' treats a line like "AM_V_CC = $(am__v_CC_$(V))" as one that expands a macro with the funny name am__v_CC_$(V instead of the desired name am__v_CC_1 or am__v_CC_0, and since the funny macro is not defined the line is equivalent to "AM_V_CC = )"; this inserts a stray ")" when $(AM_V_CC) is used, which eventually causes 'make' to fail. The basic idea is that instead of generating Makefile.in lines like "AM_V_CC = $(am__v_CC_$(V))", we generate "AM_V_CC = $(am__v_CC_@AM_V@)". We then AC_SUBST $(V) for @AM_V@ in the usual case where `make' supports nested variables, and substitute 1 (or 0) otherwise. Similarly for usages like $(am__v_CC_$(AM_DEFAULT_VERBOSITY)). With this change, make implementations that doesn't grasp nested variable expansions will still be able to run Makefiles generated using the silent-rules option. They won't allow the user to override the make verbosity at runtime through redefinition of $(V) (as in "make V=0"); but this is still an improvement over not being able to work at all. * NEWS: Document this. * automake.in (define_verbose_var): When defining the variables, use @AM_V@ rather than $(V), and use @AM_DEFAULT_V@ rather than $(AM_DEFAULT_VERBOSITY). * doc/automake.texi (Automake silent-rules Option): Explain new system. * m4/silent.m4 (AM_SILENT_RULES): Check whether `make' supports nested variables, and substitute AM_V and AM_DEFAULT_V accordingly. * tests/silent-nested-vars.test: New test. * tests/Makefile.am (TESTS): Add it.
* | | docs: fix paragraph names for automake and aclocal invocationsStefano Lattarini2011-12-281-17/+24
| |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | All the other autotools entitle their invocation nodes "autofoo Invocation", whereas automake used to call its "Invoking Automake" and "Invoking aclocal". So let's try to be more consistent. This change is related to automake bug#8071. Suggestion by Reuben Thomas and Eric Blake. * doc/automake.texi (Invoking Automake): Node renamed ... (automake Invocation): ... to this. (Invoking aclocal): Node renamed ... (aclocal Invocation): ... to this. Add proper @anchor directives to avoid breaking existing web hyperlinks still using the old names of the renamed nodes.
* | docs: "aclocal --install -I /abs/dir" actually copies filesStefano Lattarini2011-12-271-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change is for automake bug#8407. In the past, there had been some debate and confusion about whether "aclocal --install" should copy third-party .m4 files in the first directory passed to the `-I' option even when such directory was given as an absolute path, or whether it was better to do so only for directories specified with a relative path. The rationale for this latter behaviour was that, before the existence of the `ACLOCAL_PATH' variable, the only way (a poor way, I might add) for a common user to extend the search path of a system-wide installation of aclocal was to export something like ACLOCAL="aclocal -I /my/extra/macros" in the environment. Today, the correct way to proceed is undoubtedly through the use of ACLOCAL_PATH, so we can settle the question once and for all, and start verifying the correct behaviour of `-I' with a new test. * tests/aclocal-install-absdir.test: New test. * tests/Makefile.am (TESTS): Add it. * doc/automake.texi (aclocal Options): Be more explicit about this part of `--install' semantics.
* | docs: fix node names for automake and aclocal invocationsStefano Lattarini2011-12-261-5/+2
|/ | | | | | | | | | | | | | | | | | | | | | | | | With the older node names, an "info automake" command issued from the command line would have opened the node about the invocation of the automake program, rather than the Top node of the automake documentation. To invoke the Top node, one had to issue the command "info Automake" instead (note the different capitalization). This was suboptimal, and certainly confusing. With this change, "info automake" will open the Top node of the automake documentation; to access the nodes about the invocation of the automake and aclocal program, one has now to issue "info automake-invocation" and "info aclocal-invocation" respectively. This change fixes automake bug#8071. See also commits `v2.61a-22-ge9215d1' and `v2.61a-72-g8c07b48' in the autoconf git repository, which tackled a similar issue. * doc/automake.texi (@direntry): Rename nodes `aclocal' and `automake' to `aclocal-invocation' and `automake-invocation' respectively. * NEWS: Update.
* gitignore: use only one .gitignore file, in the top-level directoryStefano Lattarini2011-12-242-35/+0
| | | | | | | | * doc/.gitignore, doc/amhello/.gitignore, lib/Automake/.gitignore, lib/Automake/tests/.gitignore, tests/.gitignore: Deleted, their contents merged into ... * .gitignore: ... this top-level file. Since we are at it, improve it by anchoring files where it makes sense.
* regex: deprecate the obsolete macro AM_WITH_REGEXStefano Lattarini2011-12-221-13/+15
| | | | | | | | | | | | | | | | | | | | | | | | This is a backport of commit v1.11-433-g37b0aee. Today, practically nobody uses the GNU rx library, which, according to its own website <http://www.gnu.org/software/rx/rx.html>, has been "decommissioned". Consequently, the automake-provided macro AM_WITH_REGEX is not used nor required anymore. Deprecate it, so that it will be possible to safely remove it in the next major automake version. * m4/regex.m4 (AM_WITH_REGEX): Give a warning of the class `obsolete' when this macro is used. * doc/automake.texi (Public Macros): Move description of `AM_WITH_REGEX' from here ... (Obsolete Macros): ... to here, and declare it as obsolete and "to be removed in a future version". * tests/regex-obsolete.test: New test. * tests/Makefile.am (TESTS): Add it. * NEWS: Update. See also: <http://lists.gnu.org/archive/html/automake-patches/2010-11/msg00131.html>
* repo: don't commit generated files in the git repository anymoreStefano Lattarini2011-12-221-847/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It has been quite some time since autoconf and libtool have stopped committing the generated autotools files in their git repositories, with no significant ill effects we're aware of. It's true that the autoconf bootstrap process has now the minor annoyance that a pre-installed autoconf is required to complete it; but luckily automake will not have a similar annoyance, since our bootstrap script take care, through some hoops, to use the very automake and aclocal versions from the current git checkout to generate the required aclocal.m4 and Makefile.in files. In fact, this has been a necessity also in the past, because automake has been known to use in its own build system new development features that hadn't been present in any previously released automake distribution. * aclocal.m4: Delete. * configure: Likewise. * Makefile.in: Likewise. * doc/Makefile.in: Likewise. * lib/Automake/Makefile.in: Likewise. * lib/Automake/tests/Makefile.in: Likewise. * lib/Makefile.in: Likewise. * lib/am/Makefile.in: Likewise. * m4/Makefile.in: Likewise. * tests/Makefile.in: Likewise. * .gitignore: Ignore configure, aclocal.m4, and all the Makefile.in files. * configure.ac (AC_PREREQ): New macro call, to require the latest autoconf (2.68 for the moment).
* dist-xz, dist-bzip2: don't hard-code -9, honor envvar settingsJim Meyering2011-12-101-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before the present change, automake-generated `dist-xz' rule used a hard-coded `xz -9'. That was a problem because on this front, xz differs from gzip and bzip2. While the latter two don't incur any run-time decompression penalty for using a higher compression level, specifying -9 with xz imposes a potentially fatal virtual memory requirement on any client that wants to decompress your tar.xz file. People have complained that a tarball compressed with -9 cannot be uncompressed in a low-memory environment (wrt-based embedded). Hence, instead of defaulting to -9, which is useful only for very large tarballs, it defaults to -e (equivalent to -6e). This limits the default memory requirements imposed on decompressors, yet still gives very good compression ratios. * lib/am/distdir.am (dist-xz): Do not hard-code xz's -9: that made it impossible to override. Actually don't default to -9, either, since that induced inordinately large virtual memory usage when merely decompressing. Instead, use its XZ_OPT envvar, defaulting to -e if not defined. Suggested by Lasse Collin. (dist, dist-all) [?XZ?]: Likewise (dist-bzip2): Similarly, do not hard-code -9, but do continue to use -9 by default. Honor the BZIP2 envvar. (dist, dist-all) [?BZIP2?]: Likewise * NEWS: Update. * doc/automake.texi (The Types of Distributions): Describe the newly enabled environment variables. This is inspired to commit v1.11-389-g6da46f3, with additional changes to reflect that the xz compression level should default to -e, not -9.
* fix: regenerate doc/MakefileStefano Lattarini2011-11-221-4/+5
|
* fix: regenerate MakefilesStefano Lattarini2011-10-301-2/+7
|
* info: allow user to inhibit creation/update of '${infodir}/dir'Stefano Lattarini2011-10-231-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | With this change, we allow the user to request the install-info rules not to update the `${infodir}/dir' file, by exporting the environment variable `AM_UPDATE_INFO_DIR' to the value "no". This is especially useful to distro packagers, and is a definite improvement over our previous hack of looking whether the `install-info' program was the Debian or GNU version -- hack which had been silently broken with recent versions of debian install-info BTW (probably since dpkg 1.15.4, 2009-09-06). This change fixes automake bug#9773. See also Debian Bug#543992. * lib/am/texinfos.am: Don't look anymore at the output of `install-info --version' to decide whether to use it to update the `${infodir}/dir' or not; instead, honour the environment variable `AM_UPDATE_INFO_DIR'. * tests/install-info-dir.test: New test. * tests/Makefile.am (TESTS): Add it. * tests/defs: Also unset `AM_UPDATE_INFO_DIR', to avoid unwanted interferences from the environment. * doc/automake.texi (Texinfo): Update. * NEWS: Likewise. * THANKS: Likewise. Report by Jonathan Nieder.
* Merge branch 'dejagnu-siteexp-extend' into maintStefano Lattarini2011-10-221-0/+8
|\ | | | | | | | | * dejagnu-siteexp-extend: dejagnu: allow the package developer to extend site.exp
| * dejagnu: allow the package developer to extend site.expStefano Lattarini2011-10-221-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes automake bug#7873. * lib/am/dejagnu.am (site.exp): Depend from the files listed in $(EXTRA_DEJAGNU_SITE_CONFIG), if any. Append their contents to the generated site.exp (still preserving user edits). * doc/automake.texi (Dejagnu Tests): Update. * tests/dejagnu-siteexp-append.test: New test. * tests/dejagnu-siteexp-extend.test: Likewise. * tests/dejagnu-siteexp-useredit.test: Likewise.ù * NEWS: Update. * tests/Makefile.am (TESTS): Update. Suggestion by Rainer Orth.
* | docs: avoid using colon character inside arguments of @pxrefStefano Lattarini2011-10-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Fixes automake bug#9753 * doc/automake.texi (VPATH Builds): Avoid using colon character `:' inside arguments of @pxref, as this can cause problems in the generated `.info' files, and such an usage will be explicitly forbidden by future texinfo documentation. * THANKS: Update. Reported by Дилян Палаузов.
* | Merge branch 'fix-pr9400' into maintStefano Lattarini2011-10-061-3/+9
|\ \ | | | | | | | | | | | | * fix-pr9400: parallel-tests: automake error our on invalid TEST_EXTENSIONS
| * | parallel-tests: automake error our on invalid TEST_EXTENSIONSStefano Lattarini2011-10-011-3/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change fixes automake bug#9400. * automake.in (handle_tests): Bail out if a suffix specified in TEST_EXTENSIONS would produce an invalid `xxx_LOG_COMPILER' variable or an invalid suffix rule. Before this change, automake would have issued a confusing error messages (about invalid or non-POSIX variables being defined), and in some situations would have even produced a broken `Makefile.in' file. ($TEST_EXTENSION_PATTERN): New helper variable. * doc/automake.texi (Simple Tests using parallel-tests): Document the limitations on TEST_EXTENSIONS explicitly. * NEWS: Update. * tests/test-extensions.test: New test. * tests/Makefile.am (TESTS): Update.
* | | Merge branch 'fix-pr7988' into maintStefano Lattarini2011-10-011-4/+13
|\ \ \ | | | | | | | | | | | | | | | | * fix-pr7988: docs: don't suggest installing `.m4' files in hard-coded location
| * | | docs: don't suggest installing `.m4' files in hard-coded locationStefano Lattarini2011-09-281-4/+13
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change fixes automake bug#7988. * doc/automake.texi (aclocal Options): State that the use of the `--print-ac-dir' option to determine the directory where third-party packages can install their `.m4' files is discouraged now. (Extending aclocal): Suggest telling the user about ACLOCAL_PATH. * THANKS: Update. Report by Peter Johansson.
* | | fix: regenerate Makefile.in filesStefano Lattarini2011-09-281-1/+1
| | |
* | | uninstall: "make uninstall" before "make install" worksStefano Lattarini2011-09-261-6/+8
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change fixes automake bug#9578. * lib/am/inst-vars.am (am__uninstall_files_from_dir): New internal macro, that defines a shell code fragment to uninstall files from a given directory. * lib/am/data.am (uninstall-%DIR%%PRIMARY%): Use it, to reduce code duplication and improve consistency and correctness. * lib/am/libs.am (uninstall-%DIR%LIBRARIES): Likewise. * lib/am/lisp.am (uninstall-%DIR%LISP): Likewise. * lib/am/mans.am (uninstall-man%SECTION%): Likewise. * lib/am/python.am (uninstall-%DIR%LIBRARIES): Likewise. * lib/am/scripts.am (uninstall-%DIR%SCRIPTS): Likewise. * tests/uninstall-pr9578.test: New test. * tests/uninstall-fail.test: New test. * tests/Makefile.am (TESTS): Add them. * NEWS, THANKS: Update. Report by Nick Bowler.
* | Merge branch 'aclocal-path' into maintStefano Lattarini2011-09-201-0/+34
|\ \ | | | | | | | | | | | | | | | * aclocal-path: docs: document planned precedence changes in aclocal search path aclocal: handle ACLOCAL_PATH environment variable
| * | docs: document planned precedence changes in aclocal search pathStefano Lattarini2011-09-201-0/+10
| | | | | | | | | | | | | | | | | | | | | * doc/automake.texi (Macro Search Path): Explicitly state that the lookup order for extra directories of `.m4' files will be changed in the next major release. * NEWS: Likewise.
| * | aclocal: handle ACLOCAL_PATH environment variablePaolo Bonzini2011-09-201-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * aclocal.in (parse_ACLOCAL_PATH): New function, parse ACLOCAL_PATH as a colon-separated list of directories to be included in the search path. * doc/automake.texi (Macro Search Path): Document new behavior and the precedence rules for various elements of the search path. * tests/aclocal-path.test: New test. * tests/aclocal-path-install.test: Likewise. * tests/aclocal-path-install-serial.test: Likewise. * tests/aclocal-path-precedence.test: Likewise. * tests/aclocal-path-nonexistent.test: Likewise. * tests/Makefile.am (TESTS): Add them. * NEWS: Update. * tests/distcheck-missing-m4.test: Extend by also checking interactions with ACLOCAL_PATH. * tests/distcheck-outdated-m4.test: Likewise, and fix a couple of botched comments since we are at it.
* | | docs: deprecate JAVA primaryStefano Lattarini2011-09-191-6/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * doc/automake.texi (Java): Deprecate the JAVA primary, stating that it will become obsolete in automake 1.12 and probably removed altogether in automake 1.13. Reflect this in the section title, by appending the string "(deprecated feature)". (@menu, @detailmenu): Update. (Java Support with gcj): The cross-referenced support for bytecode compilation with the JAVA primary is rudimentary and deprecated. State that explicitly.
* | | docs: clearer distinction between `.java' with javac and with gcjStefano Lattarini2011-09-191-12/+17
|/ / | | | | | | | | | | | | | | | | | | * doc/automake.texi (Java support): Rename this node ... (Java support with gcj): ... to this, and change its title from "Compiling Java sources" to "Compiling Java sources using gcj". (@detailmenu, @menu, @cindex): Update and make more precise. (Java): Change the title of this node from simply "Java" to "Java bytecode compilation". (@detailmenu, @menu, @cindex): Update and make more precise.
* | aclocal: more granularity in acdir overridingStefano Lattarini2011-09-081-28/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before this change, using the `--acdir' option caused aclocal to redefine both the directory of automake-provided m4 macros and the directory of third-party system-wide m4 macros. With this change, we deprecate the `--acdir' aclocal option, and introduce two new options `--automake-acdir' and `--system-acdir', to allow for more granularity. * aclocal.in (@automake_includes, @system_includes, @user_includes): Fix and extend comments. (usage): Update. (handle_acdir_option): New function. (parse_arguments): Recognize new options `--system-acdir' and `automake-acdir', and handle `--acdir' using the new function above. Simplify logic by assuming that the directory of third-party system-wide m4 files always exists. * tests/aclocal.in: Update to use the new options, instead of the deprecated. `--acdir'. * m4/dirlist: Move ... * m4/acdir/dirlist: ... here. * m4/Makefile.am (EXTRA_DIST): Update. (m4datadir): Rename ... (automake_acdir): ... to this. Accordingly, ... (dist_m4data_DATA): ... rename this ... (dist_automake_ac_DATA): ... to this. (system_acdir): New, directory. (dist_system_ac_DATA): New, defined to an empty value; this will ensure that the $(system_acdir) directory will be created by "make install". * tests/aclocal.test: Remove check about the `--print-ac-dir' option of aclocal, it has been moved into ... * tests/aclocal-print-acdir.test: ... this new test, and quite extended. * tests/aclocal-acdir.test: New test. * tests/Makefile.am (TESTS): Add the new tests. * NEWS, bootstrap: Update. * doc/automake.texi (aclocal Options, Macro Search Path): Update.
* | docs: report few more automake parsing limitationsStefano Lattarini2011-09-011-5/+21
| | | | | | | | | | | | | | | | | | | | | | Partly motivated by automake bug#8360. * doc/automake.texi (General Operation): Report few more automake limitations w.r.t. parsing of unusual makefile constructs. Related minor reorderings. * tests/doc-parsing-buglets-colneq-subst.test: New test. * tests/doc-parsing-buglets-tabs.test: Likewise. * tests/Makefile.am (TESTS): Update.
* | docs: how to use '-I' option in AM_CPPFLAGS for best VPATH supportBruno Haible2011-08-031-0/+12
| | | | | | | | | | * doc/automake.texi (Program Variables): Recommend -I options to both the build directory and the source directory when needed.
* | docs: add references between the 2 sections on java supportBenoit Sigoure2011-07-221-4/+7
| | | | | | | | * doc/automake.texi (Java Support, Java): Add cross-references.
* | docs, tests: synchronize examples on silent-rules from config.siteStefano Lattarini2011-07-081-0/+1
| | | | | | | | | | * doc/automake.texi (Automake silent-rules Option): Reference test 'silent-configsite.test' in comments.
* | docs, tests: synchronize examples from docs to testsStefano Lattarini2011-07-011-12/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * tests/README (Writing test cases): Give suggestions on how to keep test cases and examples in the documentation synchronized. * doc/automake.texi: Improve or fix existing testcase-referencing comments, and add many new ones. * HACKING (Administrivia): Suggest to test complex examples and idioms from the manual. * tests/specflg8.test: Improve synchronization with the example in the manual. * tests/output11.test:Likewise. * tests/txinfo21.test:Likewise. * tests/interp.test: Likewise. Since we are at it, and enable the `errexit' shell flag, do related changes, and add trailing `:'command. * tests/amhello-cflags.test: New test. * tests/amhello-cross-compile.test: Likewise. * tests/amhello-binpkg.test: Likewise. * tests/tests-environment-backcompat: Likewise. * tests/parallel-tests-log-compiler-example.test: Likewise. * tests/Makefile.am (TESTS): Update.
* | Merge branch 'parallel-tests-maint' into maintStefano Lattarini2011-06-281-0/+17
|\ \ | | | | | | | | | | | | | | | | | | | | | * parallel-tests-maint: Revert "docs: parallel-tests is not experimental anymore" parallel-tests: stricter checks on DISABLE_HARD_ERRORS support docs: parallel-tests is not experimental anymore check: document and test $(TEST_SUITE_LOG) overriding
| * | Revert "docs: parallel-tests is not experimental anymore"Stefano Lattarini2011-06-241-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit a9eef973b5ea47cc3495f1a8307d4f7b85aea46f. It turned out that the current work to introduce TAP and SubUnit support in Automake-generated testsuite harnesses will probably require the introduction of slight incompatibilities in the 'parallel-tests' behaviour, starting from release 1.12 onward. So it's advisable to continue to characterize the 'parallel-tests' support as "experimental" in maintenance release 1.11.2. Suggestion from Ralf Wildenhues.
| * | Merge branch 'maint' into parallel-tests-maintStefano Lattarini2011-06-201-33/+43
| |\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * maint: check: don't use multi-line coloring for the report ansi2knr: deprecate, it will go away in the next major release docs: primary/prefix combination "pkglib_PROGRAMS" is now invalid docs: replace obsolete @vindex entry with a useful one docs: AM_DISTCHECK_CONFIGURE_FLAGS is for corner cases
| * \ \ Merge branch 'maint' into parallel-tests-maintStefano Lattarini2011-06-161-84/+309
| |\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * maint: news: update w.r.t. introduction of AM_DISTCHECK_CONFIGURE_FLAGS tests: optimize tests on primary/prefix mismatch for speed Warnings about primary/prefix mismatch fixed and extended. maintcheck: DISTCHECK_CONFIGURE_FLAGS can be defined on make cmdline distcheck: add support for AM_DISTCHECK_CONFIGURE_FLAGS docs: better documentation for silent make rules
| * \ \ \ Merge branch 'maint' into parallel-tests-maintStefano Lattarini2011-06-033-5/+20
| |\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * maint: maintcheck: fix some failures, extend some checks automake, aclocal: honour configure-time AUTOCONF and AUTOM4TE build: the user can override AUTOM4TE, AUTORECONF and AUTOUPDATE too remake: behave better with non-GNU make in subdirectories tests/README: fix example about `make -e' usage
| * | | | | docs: parallel-tests is not experimental anymoreStefano Lattarini2011-05-111-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The parallel-tests driver has now been used quite extensively by a fair number of real-world applications (e.g., GNU coreutils, GNU libtool, GNU grep, and various packages using Gnulib), and thus exposed to adequate on-field testing. So there's no point in declaring it experimental anymore (which would risk to make potential users shy away from it). * doc/automake.texi (Simple Tests using parallel-tests): Do not declare the parallel-tests driver as "experimental" anymore.
| * | | | | check: document and test $(TEST_SUITE_LOG) overridingStefano Lattarini2011-05-111-0/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * doc/automake.texi (Simple Tests using parallel-tests): Explain how and why TEST_SUITE_LOG can be overridden at runtime. * tests/parallel-tests-log-override-1.test: New test, check that the newly documented idiom and similar usages are truly supported. * tests/parallel-tests-log-override-2.test: Likewise. * tests/parallel-tests-log-override-recheck.test: Likewise. * tests/Makefile.am (TESTS): Update.
View Lorry Controller Status