3 * Version requirements:
5 - Autoconf 2.65 or greater is required.
7 - The rules to build PDF and DVI output from Texinfo input now
8 requires Texinfo 4.9 or later.
10 - Support for the "Cygnus-style" trees (once enabled by the 'cygnus'
11 option) has been removed. See discussion about automake bug#11034
14 - The automake-provided '@mkdir_p@' configure substitution and
15 AM_PROG_MKDIR m4 macro have been removed. They had been obsolete
16 since automake 1.10, and actively deprecated since Automake 1.12.1.
17 However, to maintain a degree of backward-compatibility, the make
18 variable '$(mkdir_p)' is still defined (now simple as an alias to
19 '$(MKDIR_P)'). It will probably be removed in future major versions
20 of Automake (probably 1.14).
22 - The deprecated aclocal option '--acdir' has been removed. You
23 should use the options '--automake-acdir' and '--system-acdir'
24 instead (which have been introduced in Automake 1.11.2).
26 - The following long-obsolete m4 macros have been removed:
28 AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002
29 fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC
30 fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC
31 AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002
32 ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR
33 jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
34 ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT
35 gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL
36 fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part
37 of the now-removed automatic de-ANSI-fication
40 - All the "old alias" macros in 'm4/obsolete.m4' have been removed.
42 * Obsolescent features:
44 - Use of the long-deprecated two- and three-arguments invocation forms
45 of the AM_INIT_AUTOMAKE is not documented anymore. It's still
46 supported though (albeit with a warning in the 'obsolete' category),
47 to cater for people who want to define the version number for their
48 package dynamically (e.g., from the current VCS revision). We'll
49 have to continue this support until Autoconf itself is fixed to allow
50 better support for such dynamic version numbers.
52 * Elisp byte-compilation:
54 - The byte compilation of '.el' files into '.elc' files is now done
55 with a suffix rule. This has simplified the compilation process, and
56 more importantly made it less brittle. The downside is that emacs is
57 now invoked once for each '.el' files, which cause some noticeable
58 slowdowns. These should however be mitigated on multicore machines
59 (which are becoming the norm today) if concurrent make ("make -j")
62 - Elisp files placed in a subdirectory are now byte-compiled to '.elc'
63 files in the same subdirectory; for example, byte-compiling of file
64 'sub/foo.el' file will result in 'sub/foo.elc' rather than in
65 'foo.elc'. This behaviour is backward-incompatible with older
66 Automake versions, but it is more natural and more sane. See also
69 - The Emacs invocation performing byte-compilation of '.el' files honors
70 the $(AM_ELCFLAGS) and $(ELCFLAGS) variables; as typical, the former
71 one is developer-reserved and the latter one user-reserved.
73 - The 'elisp-comp' script, once provided by Automake, has been rendered
74 obsoleted by the just-described changes, and thus removed.
76 * Changes to Automake-generated testsuite harnesses:
78 - The parallel testsuite harness (previously only enabled by the
79 'parallel-tests' option) is the default one; the older serial
80 testsuite harness will still be available through the use of the
81 'serial-tests' option (introduced in Automake 1.12).
83 - The 'color-tests' option is now unconditionally activated by default.
84 In particular, this means that testsuite output is now colorized by
85 default if the attached terminal seems to support ANSI escapes, and
86 that the user can force output colorization by setting the variable
87 AM_COLOR_TESTS to "always". The 'color-tests' is still recognized
88 for backward-compatibility, although it's a handled as a no-op now.
90 * Silent rules support:
92 - Support for silent rules is now always active in Automake-generated
93 Makefiles. So, although the verbose output is still the default,
94 the user can now always use "./configure --enable-silent-rules" or
95 "make V=0" to enable quieter output in the package he's building.
97 - The 'silent-rules' option has now become a no-op, preserved for
98 backward-compatibility only. In particular, its use does not disable
99 the warnings in the 'portability-recursive' category anymore.
103 - The rules to build PDF and DVI files from Texinfo input now use the
104 '--build-dir' option, to keep the auxiliary files used by texi2dvi
105 and texi2pdf around without cluttering the build directory, and to
106 make it possible to run the "dvi" and "pdf" recipes in parallel.
108 * Automatic remake rules and 'missing' script:
110 - The 'missing' script does not try anymore to update the timestamp
111 of out-of-date files that require a maintainer-specific tool to be
112 remade, in case the user lacks such a tool (or has a too-old version
113 of it). It just give a useful warning, and in some cases also a tip
114 about how to obtain such a tool.
116 - The missing script has thus become useless as a (poor) way to work
117 around the sketched-timestamps issues that can happen for projects
118 that keep generated files committed in their VCS repository. Such
119 projects are now encouraged to write a custom "fix-timestamps.sh"
120 script to avoid such issues; a simple example is provided in the
121 "CVS and generated files" chapter of the automake manual.
125 - The user can now define his own recursive targets that recurse
126 in the directories specified in $(SUBDIRS). This can be done by
127 specifying the name of such targets in invocations of the new
128 'AM_EXTRA_RECURSIVE_TARGETS' m4 macro.
132 - Any failure in the recipe of the "tags", "ctags", "cscope" or
133 "cscopelist" targets in a subdirectory is now propagated to the
134 top-level make invocation.
136 - Tags are correctly computed also for files in _SOURCES variables that
137 only list files with non-standard suffixes (see automake bug#12372).
139 * Improvements to aclocal and related rebuilds rules:
141 - The Autoconf-provided macro AC_CONFIG_MACRO_DIR is now traced by
142 aclocal, and can be used to declare the local m4 include directory.
143 Formerly, one had to specify it with an explicit '-I' option to the
144 'aclocal' invocation.
146 - The special make variable ACLOCAL_AMFLAGS is deprecated; future
147 Automake versions will warn about its use, and later version will
148 remove support for it altogether.
150 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
154 * WARNING: Future backward-incompatibilities!
156 - Future versions of Automake will likely drop support for the
157 long-deprecated 'configure.in' name for the Autoconf input file.
158 You are advised to use the recommended name 'configure.ac' instead.
160 - Support for the "Cygnus-style" trees (as enabled by the 'cygnus'
161 option) will be removed in the next major Automake release (1.13).
163 - The long-obsolete (since automake 1.10) AM_PROG_MKDIR m4 macro will
164 be removed in Automake 1.13. The $(mkdir_p) make variable and the
165 @mkdir_p@ substitution will still remain available (as aliases of
166 $(MKDIR_P)) for the moment, for better backward compatibility.
168 - Autoconf 2.65 or later will be required by the next major Automake
169 version (1.13). Until now, Automake has required Autoconf version
172 - Starting from the next major Automake version (1.13), the rules
173 to build pdf, ps and dvi output from Texinfo input will use the
174 '--build-dir' option by default. Since such an option was only
175 introduced in Texinfo 4.9, this means that Makefiles generated by
176 future Automake versions will require at least that version of
179 - Starting from the next major Automake version (1.13), the parallel
180 testsuite harness (previously only enabled by the 'parallel-tests'
181 option) will become the default one; the older serial testsuite
182 harness will still be available through the use of the 'serial-tests'
185 - The following long-obsolete m4 macros will be removed in the
186 next major Automake version (1.13):
188 AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002
189 fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC
190 fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC
191 AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002
192 ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR
193 jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
194 ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT
195 gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL
196 fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part
197 of the now-removed automatic de-ANSI-fication
200 - All the "old alias" macros in 'm4/obsolete.m4' will be removed in
201 the next major Automake version (1.13).
203 - The '--acdir' option of aclocal is deprecated, and will probably
204 be removed in the next major Automake release (1.13). You should
205 use the options '--automake-acdir' and '--system-acdir' instead
206 (which have been introduced in Automake 1.11.2).
208 - The 'missing' script will no longer try to update the timestamp
209 of out-of-date files that require a maintainer-specific tool to be
210 remade, in case the user lacks such a tool (or has a too-old version
211 of it). In fact, starting from Automake 1.13, all it'll do will be
212 giving more useful warnings than a bare "command not found" from a
217 - The AM_PROG_VALAC macro has been enhanced to takes two further
218 optional arguments; it's signature now being
220 AM_PROG_VALAC([MINIMUM-VERSION], [ACTION-IF-FOUND],
221 [ACTION-IF-NOT-FOUND])
223 - By default, AM_PROG_VALAC no longer aborts the configure invocation
224 if the Vala compiler found is too old, but simply prints a warning
225 messages (as it did when the Vala compiler was not found). This
226 should avoid unnecessary difficulties for end users that just want
227 to compile the unmodified, distributed Vala-generated C sources,
228 but happens to have an old Vala compiler in their PATH. This fixes
231 - If no proper Vala compiler is found at configure runtime, AM_PROG_VALAC
232 will set the AC_SUBST'd variable 'VALAC' to 'valac' rather than to ':'.
233 This is a better default, because with it a triggered makefile rule
234 invoking a Vala compilation will clearly fail with an informative error
235 message like "valac: command not found", rather than silently, with
236 the error possibly going unnoticed or triggering harder-to-diagnose
237 fallout failures in later steps.
239 Bugs fixed in 1.12.5:
241 * Long-standing bugs:
243 - Automake no longer generates spurious remake rules invoking autoheader
244 to regenerate the template corresponding to header files specified after
245 the first one in AC_CONFIG_HEADERS (automake bug#12495).
247 - When wrapping Microsoft tools, the 'compile' script falls back to
248 finding classic 'libname.a' style libraries when 'name.lib' and
249 'name.dll.lib' aren't available.
251 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
255 * Warnings and deprecations:
257 - Warnings in the 'obsolete' category are enabled by default both in
258 automake and aclocal.
260 * Miscellaneous changes:
262 - Some testsuite weaknesses and spurious failures have been fixed.
264 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
268 * Miscellaneous changes:
270 - The '.m4' files provided by Automake no longer define serial numbers.
271 This should cause no difference in the behaviour of aclocal though.
273 - Some testsuite weaknesses and spurious failures have been fixed.
275 - There is initial support for automatic dependency tracking with the
276 Portland Group C/C++ compilers, thanks to the new new depmode 'pgcc'.
278 Bugs fixed in 1.12.3:
280 * Long-standing bugs:
282 - Instead of renaming only self-references of files (typically for
283 #lines), ylwrap now also renames references to the other generated
284 files. This fixes support for GLR and C++ parsers from Bison (PR
285 automake/491 and automake bug#7648): 'parser.c' now properly
286 #includes 'parser.h' instead of 'y.tab.h'.
288 - Generated files unknown to ylwrap are now preserved. This fixes
289 C++ support for Bison (automake bug#7648): location.hh and the
290 like are no longer discarded.
292 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
296 * Warnings and deprecations:
298 - Automake now issues a warning (in the 'portability' category) if
299 'configure.in' is used instead of 'configure.ac' as the Autoconf
300 input file. Such a warning will also be present in the next
301 Autoconf version (2.70).
305 - Recursive cleaning rules descends into the $(SUBDIRS) in the natural
306 order (as done by the other recursive rules), rather than in the
307 inverse order. They used to do that in order to work a round a
308 limitation in an older implementation of the automatic dependency
309 tracking support, but that limitation had been lifted years ago
310 already, when the automatic dependency tracking based on side-effects
311 of compilation had been introduced.
313 - Cleaning rules for compiled objects (both "plain" and libtool) work
314 better when subdir objects are involved, not triggering a distinct
315 'rm' invocation for each such object. They do so by removing *any*
316 compiled object file that is in the same directory of a subdir
317 object. See automake bug#10697.
319 * Silent rules support:
321 - A new predefined $(AM_V_P) make variable is provided; it expands
322 to a shell conditional that can be used in recipes to know whether
323 make is being run in silent or verbose mode.
325 Bugs fixed in 1.12.2:
327 * SECURITY VULNERABILITIES!
329 - The 'distcheck' recipe no longer grants temporary world-write
330 permissions on the extracted distdir. Even if such rights were
331 only granted for a vanishingly small time window, the implied
332 race condition proved to be enough to allow a local attacker
333 to run arbitrary code with the privileges of the user running
334 "make distcheck". This is CVE-2012-3386.
336 * Long-standing bugs:
338 - The "recheck" targets behaves better in the face of build failures
339 related to previously failed tests. For example, if a test is a
340 compiled program that must be rerun by "make recheck", and its
341 compilation fails, it will still be rerun by further "make recheck"
342 invocations. See automake bug#11791.
344 * Bugs introduced by 1.12.1:
346 - Automake provides once again the '$(mkdir_p)' make variable and the
347 '@mkdir_p@' substitution (both as simple aliases for '$(MKDIR_P)'),
348 for better backward-compatibility.
350 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
354 * New supported languages:
356 - Support for Objective C++ has been added; it should work similarly to
357 the support for Objective C.
359 * Deprecated obsolescent features:
361 - Use of the long-deprecated two- and three-arguments invocation forms
362 of the AM_INIT_AUTOMAKE macro now elicits a warning in the 'obsolete'
363 category. Starting from some future major Automake release (likely
364 post-1.13), such usages will no longer be allowed.
366 - Support for the "Cygnus-style" trees (enabled by the 'cygnus' option) is
367 now deprecated (its use triggers a warning in the 'obsolete' category).
368 It will be removed in the next major Automake release (1.13).
370 - The long-obsolete (since 1.10) automake-provided $(mkdir_p) make
371 variable, @mkdir_p@ configure-time substitution and AM_PROG_MKDIR
372 m4 macro are deprecated, eliciting a warning in the 'obsolete'
375 * Miscellaneous changes:
377 - The Automake test cases now require a proper POSIX-conforming shell.
378 Older non-POSIX Bourne shells (like Solaris 10 /bin/sh) will no longer
379 be accepted. In most cases, the user shouldn't have to specify such
380 POSIX shell explicitly, since it will be looked up at configure time.
381 Still, when this lookup fails, or when the user wants to override its
382 conclusion, the variable 'AM_TEST_RUNNER_SHELL' can be used (pointing
383 to the shell that will be used to run the Automake test cases).
385 Bugs fixed in 1.12.1:
387 * Bugs introduced by 1.12:
389 - Several weaknesses in Automake's own build system and test suite
392 * Bugs introduced by 1.11.3:
394 - When given non-option arguments, aclocal rejects them, instead of
395 silently ignoring them.
397 * Long-standing bugs:
399 - When the 'color-tests' option is in use, forcing of colored testsuite
400 output through "AM_COLOR_TESTS=always" works even if the terminal is
401 a non-ANSI one, i.e., if the TERM environment variable has a value of
404 - Several inefficiencies and poor performances in the implementation
405 of the parallel-tests 'check' and 'recheck' targets have been fixed.
407 - The post-processing of output "#line" directives done the ylwrap
408 script is more faithful w.r.t. files in a subdirectory; for example,
409 if the processed file is "src/grammar.y", ylwrap will correctly
410 produce directives like:
411 #line 7 "src/grammar.y"
416 * Bugs with new Perl versions:
418 - Aclocal works correctly with perl 5.16.0 (automake bug#11543).
420 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
424 * Obsolete features removed:
426 - The never documented nor truly used script 'acinstall' has been
429 - Support for automatic de-ANSI-fication has been removed.
431 - The support for the "obscure" multilib feature has been removed
432 from Automake core (but remains available in the 'contrib/'
433 directory of the Automake distribution).
435 - Support for ".log -> .html" conversion and the check-html and
436 recheck-html targets has been removed from Automake core (but
437 remains available in the 'contrib/' directory of the Automake
440 - The deprecated 'lzma' compression format for distribution archives
441 has been removed, in favor of 'xz' and 'lzip'.
443 - The obsolete AM_WITH_REGEX macro has been removed.
445 - The long-deprecated options '--output-dir', '--Werror' and
446 '--Wno-error' have been removed.
448 - The chapter on the history of Automake has been moved out of the
449 reference manual, into a new dedicated Texinfo file.
453 - New 'cscope' target to build a cscope database for the source tree.
455 * Changes to Automake-generated testsuite harnesses:
457 - The new automake option 'serial-tests' has been introduced. It can
458 be used to explicitly instruct automake to use the older serial
459 testsuite harness. This is still the default at the moment, but it
460 might change in future versions.
462 - The 'recheck' target (provided by the parallel testsuite harness) now
463 depends on the 'all' target. This allows for a better user-experience
464 in test-driven development. See automake bug#11252.
466 - Test scripts that exit with status 99 to signal an "hard error" (e.g.,
467 and unexpected or internal error, or a failure to set up the test case
468 scenario) have their outcome reported as an 'ERROR' now. Previous
469 versions of automake reported such an outcome as a 'FAIL' (the only
470 difference with normal failures being that hard errors were counted
471 as failures even when the test originating them was listed in
474 - The testsuite summary displayed by the parallel-test harness has a
475 completely new format, that always list the numbers of passed, failed,
476 xfailed, xpassed, skipped and errored tests, even when these numbers
477 are zero (but using smart coloring when the color-tests option is in
480 - The default testsuite driver offered by the 'parallel-tests' option is
481 now implemented (partly at least) with the help of automake-provided
482 auxiliary scripts (e.g., 'test-driver'), instead of relying entirely
483 on code in the generated Makefile.in.
484 This has two noteworthy implications. The first one is that projects
485 using the 'parallel-tests' option should now either run automake with
486 the '--add-missing' option, or manually copy the 'test-driver' script
487 into their tree. The second, and more important, implication is that
488 now, when the 'parallel-tests' option is in use, TESTS_ENVIRONMENT can
489 no longer be used to define a test runner, and the command specified
490 in LOG_COMPILER (and <ext>_LOG_COMPILER) must be a *real* executable
491 program or script. For example, this is still a valid usage (albeit
494 TESTS_ENVIRONMENT = \
495 if test -n '$(STRICT_TESTS)'; then \
496 maybe_errexit='-e'; \
500 LOG_COMPILER = $(SHELL) $$maybe_errexit
502 OTOH, this is no longer a valid usage:
504 TESTS_ENVIRONMENT = \
505 $(SHELL) `test -n '$(STRICT_TESTS_CHECKING)' && echo ' -e'`
509 TESTS_ENVIRONMENT = \
510 run_with_perl_or_shell () \
512 if grep -q '^#!.*perl' $$1; then
518 LOG_COMPILER = run_with_perl_or_shell
520 - The package authors can now use customary testsuite drivers within
521 the framework provided by the 'parallel-tests' testsuite harness.
522 Consistently with the existing syntax, this can be done by defining
523 special makefile variables 'LOG_DRIVER' and '<ext>_LOG_DRIVER'.
525 - A new developer-reserved variable 'AM_TESTS_FD_REDIRECT' can be used
526 to redirect/define file descriptors used by the test scripts.
528 - The parallel-tests harness generates now, in addition the '.log' files
529 holding the output produced by the test scripts, a new set of '.trs'
530 files, holding "metadata" derived by the execution of the test scripts;
531 among such metadata are the outcomes of the test cases run by a script.
533 - Initial and still experimental support for the TAP test protocol is
536 * Changes to Yacc and Lex support:
538 - C source and header files derived from non-distributed Yacc and/or
539 Lex sources are now removed by a simple "make clean" (while they were
540 previously removed only by "make maintainer-clean").
542 - Slightly backward-incompatible change, relevant only for use of Yacc
543 with C++: the extensions of the header files produced by the Yacc
544 rules are now modelled after the extension of the corresponding
545 sources. For example, yacc files named "foo.y++" and "bar.yy" will
546 produce header files named "foo.h++" and "bar.hh" respectively, where
547 they would have previously produced header files named simply "foo.h"
548 and "bar.h". This change offers better compatibility with 'bison -o'.
550 * Miscellaneous changes:
552 - The AM_PROG_VALAC macro now causes configure to exit with status 77,
553 rather than 1, if the vala compiler found is too old.
555 - The build system of Automake itself now avoids the use of make
556 recursion as much as possible.
558 - Automake now prefers to quote 'like this' or "like this", rather
559 than `like this', in diagnostic message and generated Makefiles,
560 to accommodate the new GNU Coding Standards recommendations.
562 - Automake has a new option '--print-libdir' that prints the path of the
563 directory containing the Automake-provided scripts and data files.
565 - The 'dist' and 'dist-all' targets now can run compressors in parallel.
567 - The rules to create pdf, dvi and ps output from Texinfo files now
568 works better with modern 'texi2dvi' script, by explicitly passing
569 it the '--clean' option to ensure stray auxiliary files are not
570 left to clutter the build directory.
572 - Automake can now generate silenced rules for texinfo outputs.
574 - Some auxiliary files that are automatically distributed by Automake
575 (e.g., 'install-sh', or the 'depcomp' script for packages compiling
576 C sources) might now be listed in the DIST_COMMON variable in many
577 Makefile.in files, rather than in the top-level one.
579 - Messages of types warning or error from 'automake' and 'aclocal'
580 are now prefixed with the respective type, and presence of -Werror
583 - Automake's early configure-time sanity check now tries to avoid
584 sleeping for a second, which slowed down cached configure runs
585 noticeably. In that case, it will check back at the end of the
586 configure script to ensure that at least one second has passed, to
587 avoid time stamp issues with makefile rules rerunning autotools
590 - The warnings in the category 'extra-portability' are now enabled by
591 '-Wall'. In previous versions, one has to use '-Wextra-portability'
596 - Various minor bugfixes for recent or long-standing bugs.
598 * Bugs introduced by 1.11:
600 - The AM_COND_IF macro also works if the shell expression for the
601 conditional is no longer valid for the condition.
603 - The automake-provided parallel testsuite harness no longer fails
604 with BSD make used in parallel mode when there are test scripts in
605 a subdirectory, like in:
607 TESTS = sub/foo.test sub/bar.test
609 * Long-standing bugs:
611 - Automake's own build system finally have a real "installcheck" target.
613 - Vala-related cleanup rules are now more complete, and work better in
616 - Files listed with the AC_REQUIRE_AUX_FILE macro in configure.ac are
617 now automatically distributed also if the directory of the auxiliary
618 files coincides with the top-level directory.
620 - Automake now detects the presence of the '-d' flag in the various
621 '*YFLAGS' variables even when their definitions involve indirections
622 through other variables, such as in:
624 AM_YFLAGS = $(foo_opts)
626 - Automake now complains if a '*YFLAGS' variable has any conditional
627 content, not only a conditional definition.
629 - Explicit enabling and/or disabling of Automake warning categories
630 through the '-W...' options now always takes precedence over the
631 implicit warning level implied by Automake strictness (foreign, gnu
632 or gnits), regardless of the order in which such strictness and
633 warning flags appear. For example, a setting like:
634 AUTOMAKE_OPTIONS = -Wall --foreign
635 will cause the warnings in category 'portability' to be enabled, even
636 if those warnings are by default disabled in 'foreign' strictness.
638 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
640 Bugs fixed in 1.11.5:
642 * Bugs introduced by 1.11.3:
644 - Vala files with '.vapi' extension are now recognized and handled
645 correctly again. See automake bug#11222.
647 - Vala support work again for projects that contain some program
648 built from '.vala' (and possibly '.c') sources and some other
649 program built from '.c' sources *only*. See automake bug#11229.
651 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
655 * Miscellaneous changes:
657 - The 'ar-lib' script now ignores the "s" (symbol index) and "S" (no
658 symbol index) modifiers as well as the "s" action, as the symbol index
659 is created unconditionally by Microsoft lib. Also, the "q" (quick)
660 action is now a synonym for "r" (replace). Also, the script has been
661 ignoring the "v" (verbose) modifier already since Automake 1.11.3.
663 - When the 'compile' script is used to wrap MSVC, it now accepts an
664 optional space between the -I, -L and -l options and their respective
665 arguments, for better POSIX compliance.
667 - There is an initial, experimental support for automatic dependency
668 tracking with tcc (the Tiny C Compiler). Its associated depmode is
669 currently recognized as "icc" (but this and other details are likely
670 to change in future versions).
672 - Automatic dependency tracking now works also with the IBM XL C/C++
673 compilers, thanks to the new new depmode 'xlc'.
675 Bugs fixed in 1.11.4:
677 * Bugs introduced by 1.11.2:
679 - A definition of 'noinst_PYTHON' before 'python_PYTHON' (or similar)
680 no longer cause spurious failures upon "make install".
682 - The user can now instruct the 'uninstall-info' rule not to update
683 the '${infodir}/dir' file by exporting the environment variable
684 'AM_UPDATE_INFO_DIR' to the value "no". This is done for consistency
685 with how the 'install-info' rule operates since automake 1.11.2.
687 * Long-standing bugs:
689 - It is now possible for a foo_SOURCES variable to hold Vala sources
690 together with C header files, as well as with sources and headers for
691 other supported languages (e.g., C++). Previously, only mixing C and
692 Vala sources was supported.
694 - If "aclocal --install" is used, and the first directory specified with
695 '-I' is non-existent, aclocal will now create it before trying to copy
698 - An empty declaration of a "foo_PRIMARY" no longer cause the generated
699 install rules to create an empty $(foodir) directory; for example, if
700 Makefile.am contains something like:
704 pkglibexec_SCRIPTS += bar.sh
707 the $(pkglibexec) directory will not be created upon "make install".
709 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
713 * Miscellaneous changes:
715 - Automake's own build system is more silent by default, making use of
716 the 'silent-rules' option.
718 - The master copy of the 'gnupload' script is now maintained in gnulib,
721 - The 'missing' script no longer tries to wrap calls to 'tar'.
723 - "make dist" no longer wraps 'tar' invocations with the 'missing'
724 script. Similarly, the obsolescent variable '$(AMTAR)' (which you
725 shouldn't be using BTW ;-) no longer invokes the 'missing' script
726 to wrap tar, but simply invokes the 'tar' program itself.
728 - "make dist" can now create lzip-compressed tarballs.
730 - In the Automake info documentation, the Top node and the nodes about
731 the invocation of the automake and aclocal programs have been renamed;
732 now, calling "info automake" will open the Top node, while calling
733 "info automake-invocation" and "info aclocal-invocation" will access
734 the nodes about the invocation of respectively automake and aclocal.
736 - Automake is now distributed as a gzip-compressed and an xz-compressed
737 tarball. Previously, bzip2 was used instead of xz.
739 - The last relics of Python 1.5 support have been removed from the
740 AM_PATH_PYTHON macro.
742 - For programs and libraries, automake now detects EXTRA_foo_DEPENDENCIES
743 and adds them to the normal list of dependencies, but without
744 overwriting the foo_DEPENDENCIES variable, which is normally computed
747 Bugs fixed in 1.11.3:
749 * Bugs introduced by 1.11.2:
751 - Automake now correctly recognizes the prefix/primary combination
752 'pkglibexec_SCRIPTS' as valid.
754 - The parallel-tests harness no longer trips on sed implementations
755 with stricter limits on the length of input lines (problem seen at
758 * Long-standing bugs:
760 - The "deleted header file problem" for *.am files is avoided by stub
761 rules. This allows 'make' to trigger a rerun of 'automake' also if
762 some previously needed '.am' file has been removed.
764 - The 'silent-rules' option now generates working makefiles even
765 for the uncommon 'make' implementations that do not support the
766 nested-variables extension to POSIX 2008. For such 'make'
767 implementations, whether a build is silent is determined at
768 configure time, and cannot be overridden at make time with
769 "make V=0" or "make V=1".
771 - Vala support now works better in VPATH setups.
773 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
777 * Changes to aclocal:
779 - The `--acdir' option is deprecated. Now you should use the new options
780 `--automake-acdir' and `--system-acdir' instead.
782 - The `ACLOCAL_PATH' environment variable is now interpreted as a
783 colon-separated list of additional directories to search after the
784 automake internal acdir (by default ${prefix}/share/aclocal-APIVERSION)
785 and before the system acdir (by default ${prefix}/share/aclocal).
787 * Miscellaneous changes:
789 - The Automake support for automatic de-ANSI-fication has been
790 deprecated. It will probably be removed in the next major Automake
793 - The `lzma' compression scheme and associated automake option `dist-lzma'
794 is obsoleted by `xz' and `dist-xz' due to upstream changes.
796 - You may adjust the compression options used in dist-xz and dist-bzip2.
797 The default is now merely -e for xz, but still -9 for bzip; you may
798 specify a different level via the XZ_OPT and BZIP2 envvars respectively.
799 E.g., "make dist-xz XZ_OPT=-7" or "make dist-bzip2 BZIP2=-5"
801 - The `compile' script now converts some options for MSVC for a better
802 user experience. Similarly, the new `ar-lib' script wraps Microsoft lib.
804 - The py-compile script now accepts empty arguments passed to the options
805 `--destdir' and `--basedir', and complains about unrecognized options.
806 Moreover, a non-option argument or a special `--' argument terminates
809 - A developer that needs to pass specific flags to configure at "make
810 distcheck" time can now, and indeed is advised to, do so by defining
811 the developer-reserved makefile variable AM_DISTCHECK_CONFIGURE_FLAGS,
812 instead of the old DISTCHECK_CONFIGURE_FLAGS.
813 The DISTCHECK_CONFIGURE_FLAGS variable should now be reserved for the
814 user; still, the old Makefile.am files that used to define it will
815 still continue to work as before.
817 - New macro AM_PROG_AR that looks for an archiver and wraps it in the new
818 'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
819 This new macro is required for LIBRARIES and LTLIBRARIES when automake
820 is run with -Wextra-portability and -Werror.
822 - When using DejaGnu-based testsuites, the user can extend the `site.exp'
823 file generated by automake-provided rules by defining the special make
824 variable `$(EXTRA_DEJAGNU_SITE_CONFIG)'.
826 - The `install-info' rule can now be instructed not to create/update
827 the `${infodir}/dir' file, by exporting the new environment variable
828 `AM_UPDATE_INFO_DIR' to the value "no".
830 Bugs fixed in 1.11.2:
832 * Bugs introduced by 1.11:
834 - The parallel-tests driver no longer produces erroneous results with
835 Tru64/OSF 5.1 sh upon unreadable log files.
837 - The `parallel-tests' test driver does not report spurious successes
838 when used with concurrent FreeBSD make (e.g., "make check -j3").
840 - When the parallel-tests driver is in use, automake now explicitly
841 rejects invalid entries and conditional contents in TEST_EXTENSIONS,
842 instead of issuing confusing and apparently unrelated error messages
843 (e.g., "non-POSIX variable name", "bad characters in variable name",
844 or "redefinition of TEST_EXTENSIONS), or even, in some situations,
845 silently producing broken `Makefile.in' files.
847 - The `silent-rules' option now truly silences all compile rules, even
848 when dependency tracking is disabled. Also, when `silent-rules' is
849 not used, `make' output no longer contains spurious backslash-only
850 lines, thus once again matching what Automake did before 1.11.
852 - The AM_COND_IF macro also works if the shell expression for the
853 conditional is no longer valid for the condition.
855 * Long-standing bugs:
857 - The order of Yacc and Lex flags is fixed to be consistent with other
858 languages: $(AM_YFLAGS) comes before $(YFLAGS), and $(AM_LFLAGS) before
859 $(LFLAGS), so that the user variables override the developer variables.
861 - "make distcheck" now correctly complains also when "make uninstall"
862 leaves one and only one file installed in $(prefix).
864 - A "make uninstall" issued before a "make install", or after a mere
865 "make install-data" or a mere "make install-exec" does not spuriously
868 - Automake now warns about more primary/directory invalid combinations,
869 such as "doc_LIBRARIES" or "pkglib_PROGRAMS".
871 - Rules generated by Automake now try harder to not change any files when
872 `make -n' is invoked. Fixes include compilation of Emacs Lisp, Vala, or
873 Yacc source files and the rule to update config.h.
875 - Several scripts and the parallel-tests testsuite driver now exit with
876 the right exit status upon receiving a signal.
878 - A per-Makefile.am setting of -Werror does not erroneously carry over
879 to the handling of other Makefile.am files.
881 - The code for automatic dependency tracking works around a Solaris
882 make bug triggered by sources containing repeated slashes when the
883 `subdir-objects' option was used.
885 - The makedepend and hp depmodes now work better with VPATH builds.
887 - Java sources specified with check_JAVA are no longer compiled for
888 "make all", but only for "make check".
890 - An usage like "java_JAVA = foo.java" will now cause Automake to warn
891 and error out if `javadir' is undefined, instead of silently producing
892 a broken Makefile.in.
894 - aclocal and automake now honour the configure-time definitions of
895 AUTOCONF and AUTOM4TE when they spawn autoconf or autom4te processes.
897 - The `install-info' recipe no longer tries to guess whether the
898 `install-info' program is from Debian or from GNU, and adaptively
899 change its behaviour; this has proven to be frail and easy to
902 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
904 Bugs fixed in 1.11.1:
906 - Lots of minor bugfixes.
908 * Bugs introduced by 1.11:
910 - The `parallel-tests' test driver works around a GNU make 3.80 bug with
911 trailing white space in the test list (`TESTS = foo $(EMPTY)').
913 * Long standing bugs:
915 - On Darwin 9, `pythondir' and `pyexecdir' pointed below `/Library/Python'
916 even if the `--prefix' argument pointed outside of a system directory.
917 AM_PATH_PYTHON has been fixed to ignore the value returned from python's
918 `get_python_lib' function if it points outside the configured prefix,
919 unless the `--prefix' argument was either `/usr' or below `/System'.
921 - The testsuite does not try to change the mode of `ltmain.sh' files from
922 a Libtool installation (symlinked to test directories) any more.
924 - AM_PROG_GCJ uses AC_CHECK_TOOLS to look for `gcj' now, so that prefixed
925 tools are preferred in a cross-compile setup.
927 - The distribution is tarred up with mode 755 now by the `dist*' targets.
928 This fixes a race condition where untrusted users could modify files
929 in the $(PACKAGE)-$(VERSION) distdir before packing if the toplevel
930 build directory was world-searchable. This is CVE-2009-4029.
932 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
936 * Version requirements:
938 - Autoconf 2.62 or greater is required.
940 * Changes to aclocal:
942 - The autoconf version check implemented by aclocal in aclocal.m4
943 (and new in Automake 1.10) is degraded to a warning. This helps
944 in the common case where the Autoconf versions used are compatible.
946 * Changes to automake:
948 - The automake program can run multiple threads for creating most
949 Makefile.in files concurrently, if at least Perl 5.7.2 is available
950 with interpreter-based threads enabled. Set the environment variable
951 AUTOMAKE_JOBS to the maximum number of threads to use, in order to
952 enable this experimental feature.
954 * Changes to Libtool support:
956 - Libtool generic flags are now passed to the install and uninstall
959 - distcheck works with Libtool 2.x even when LT_OUTPUT is used, as
960 config.lt is removed correctly now.
964 - subdir-object mode works now with Fortran (F77, FC, preprocessed
965 Fortran, and Ratfor).
967 - For files with extension .f90, .f95, .f03, or .f08, the flag
968 $(FCFLAGS_f[09]x) computed by AC_FC_SRCEXT is now used in compile rules.
970 - Files with extension .sx are also treated as preprocessed assembler.
972 - The default source file extension (.c) can be overridden with
973 AM_DEFAULT_SOURCE_EXT now.
975 - Python 3.0 is supported now, Python releases prior to 2.0 are no
978 - AM_PATH_PYTHON honors python's idea about the site directory.
980 - There is initial support for the Vala programming language, when using
983 * Miscellaneous changes:
985 - Automake development is done in a git repository on Savannah now, see
987 http://git.sv.gnu.org/gitweb/?p=automake.git
989 A read-only CVS mirror is provided at
991 cvs -d :pserver:anonymous@pserver.git.sv.gnu.org:/automake.git \
992 checkout -d automake HEAD
994 - "make dist" can now create xz-compressed tarballs,
995 as well as (deprecated?) lzma-compressed tarballs.
997 - `automake --add-missing' will by default install the GPLv3 file as
998 COPYING if it is missing. It will also warn that the license file
999 should be added to source control. Note that Automake will never
1000 overwrite an existing COPYING file, even when the `--force-missing'
1003 - The manual is now distributed under the terms of the GNU FDL 1.3.
1005 - Automake ships and installs man pages for automake and aclocal now.
1007 - New shorthand `$(pkglibexecdir)' for `$(libexecdir)/@PACKAGE@'.
1009 - install-sh supports -C, which does not update the installed file
1010 (and its time stamps) if the contents did not change.
1012 - The `gnupload' script has been revamped.
1014 - The `depcomp' and `compile' scripts now work with MSVC under MSYS.
1016 - The targets `install' and `uninstall' are more efficient now, in that
1017 for example multiple files from one Automake variable such as
1018 `bin_SCRIPTS' are copied in one `install' (or `libtool --mode=install')
1019 invocation if they do not have to be renamed.
1021 Both install and uninstall may sometimes enter (`cd' into) the target
1022 installation directory now, when no build-local scripts are used.
1024 Both install and uninstall do not fail anymore but do nothing if an
1025 installation directory variable like `bindir' is set to the empty string.
1027 For built-in rules, `make install' now fails reliably if installation
1028 of a file failed. Conversely, `make uninstall' even succeeds when
1029 issued multiple times.
1031 These changes may need some adjustments from users: For example,
1032 some `install' programs refuse to install multiple copies of the
1033 same file in one invocation, so you may need to remove duplicate
1034 entries from file lists.
1036 Also, within one set of files, say, nobase_data_DATA, the order of
1037 installation may be changed, or even unstable among different hosts,
1038 due to the use of associative arrays in awk. The increased use of
1039 awk matches a similar move in Autoconf to provide for better scaling.
1041 Further, most undocumented per-rule install command variables such as
1042 binSCRIPT_INSTALL have been removed because they are not needed any
1043 more. Packages which use them should be using the appropriate one of
1044 INSTALL_{DATA,PROGRAM,SCRIPT} or their install_sh_{DATA,PROGRAM,SCRIPT}
1045 counterpart, depending on the type of files and the need for automatic
1046 target directory creation.
1048 - The "deleted header file problem" for *.m4 files is avoided by
1049 stub rules. This allows `make' to trigger a rerun of `aclocal'
1050 also if some previously needed macro file has been removed.
1052 - Rebuild rules now also work for a removed `subdir/Makefile.in' in
1053 an otherwise up to date tree.
1055 - The `color-tests' option causes colored test result output on terminals.
1057 - The `parallel-tests' option enables a new test driver that allows for
1058 parallel test execution, inter-test dependencies, lazy test execution
1059 for unit-testing, re-testing only failed tests, and formatted result output
1060 as RST (reStructuredText) and HTML. Enabling this option may require some
1061 changes to your test suite setup; see the manual for details.
1063 - The `silent-rules' option enables Linux kernel-style silent build output.
1064 This option requires the widely supported but non-POSIX `make' feature
1065 of recursive variable expansion, so do not use it if your package needs
1066 to build with `make' implementations that do not support it.
1068 To enable less verbose build output, the developer has to use the Automake
1069 option `silent-rules' in `AM_INIT_AUTOMAKE', or call the `AM_SILENT_RULES'
1070 macro. The user may then set the default verbosity by passing the
1071 `--enable-silent-rules' option to `configure'. At `make' run time, this
1072 default may be overridden using `make V=0' for less verbose, and `make V=1'
1073 for backward-compatible verbose output.
1075 - New prefix `notrans_' for manpages which should not be transformed
1076 by --program-transform.
1078 - New macro AM_COND_IF for conditional evaluation and conditional
1081 - For AC_CONFIG_LINKS, if source and destination are equal, do not
1082 remove the file in a non-VPATH build. Such setups work with Autoconf
1085 - AM_MAINTAINER_MODE now allows for an optional argument specifying
1086 the default setting.
1088 - AM_SUBST_NOTMAKE may prevent substitution of AC_SUBSTed variables,
1089 useful especially for multi-line values.
1091 - Automake's early configure-time sanity check now diagnoses an
1092 unsafe absolute source directory name and makes configure fail.
1094 - The Automake macros and rules cope better with whitespace in the
1095 current directory name, as long as the relative path to `configure'
1096 does not contain whitespace. To this end, the values of `$(MISSING)'
1097 and `$(install_sh)' may contain suitable quoting, and their expansion
1098 might need `eval'uation if used outside of a makefile. These
1099 undocumented variables may be used in several documented macros such
1100 as $(AUTOCONF) or $(MAKEINFO).
1104 * Long-standing bugs:
1106 - Fix aix dependency tracking for libtool objects.
1108 - Work around AIX sh quoting issue in AC_PROG_CC_C_O, leading to
1109 unnecessary use of the `compile' script.
1111 - For nobase_*_LTLIBRARIES with nonempty directory components, the
1112 correct `-rpath' argument is used now.
1114 - `config.status --file=Makefile depfiles' now also works with the
1115 extra quoting used internally by Autoconf 2.62 and newer
1116 (it used to work only without the `--file=' bit).
1118 - The `missing' script works better with versioned tool names.
1120 - Semantics for `missing help2man' have been revamped:
1122 Previously, if `help2man' was not present, `missing help2man' would have
1123 the following semantics: if some man page was out of date but present, then
1124 a warning would be printed, but the exit status was 0. If the man page was
1125 not present at all, then `missing' would create a replacement man page
1126 containing an error message, and exit with a status of 2. This does not play
1127 well with `make': the next run will see this particular man page as being up
1128 to date, and will only error out on the next generated man page, if any;
1129 repeat until all pages are done. This was not desirable.
1131 These are the new semantics: if some man page is not present, and help2man
1132 is not either, then `missing' will warn and generate the replacement page
1133 containing the error message, but exit successfully. However, `make dist'
1134 will ensure that no such bogus man pages are packaged into a tarball.
1136 - Targets provided by automake behave better with `make -n', in that they
1137 take care not to create files.
1139 - `config.status Makefile... depfiles' works fine again in the presence of
1140 disabled dependency tracking.
1142 - The default no-op recursive rules for these targets also work with BSD make
1143 now: html, install-html, install-dvi, install-pdf, install-pdf, install-info.
1145 - `make distcheck' works also when both a directory and some file below it
1146 have been added to a distribution variable, such as EXTRA_DIST or *_SOURCES.
1148 - Texinfo dvi, ps, pdf, and html output files are not removed upon
1149 `make mostlyclean' any more; only the LaTeX by-products are.
1151 - Renamed objects also work with the `subdir-objects' option and
1152 source file languages which Automake does not know itself.
1154 - `automake' now correctly complains about variable assignments which are
1155 preceded by a comment, extend over multiple lines with backslash-escaped
1156 newlines, and end in a comment sign. Previous versions would silently
1157 and wrongly ignore such assignments completely.
1159 * Bugs introduced by 1.10:
1161 - Fix output of dummy dependency files in presence of post-processed
1162 Makefile.in's again, but also cope with long lines.
1164 - $(EXEEXT) is automatically appended to filenames of XFAIL_TESTS
1165 that have been declared as programs in the same Makefile.
1166 This is for consistency with the analogous change to TESTS in 1.10.
1168 - Fix order of standard includes to again be `-I. -I$(srcdir)',
1169 followed by directories containing config headers.
1171 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1175 * Version requirements:
1177 - Autoconf 2.60 or greater is required.
1179 - Perl 5.6 or greater is required.
1181 * Changes to aclocal:
1183 - aclocal now also supports -Wmumble and -Wno-mumble options.
1185 - `dirlist' entries (for the aclocal search path) may use shell
1186 wildcards such as `*', `?', or `[...]'.
1188 - aclocal supports an --install option that will cause system-wide
1189 third-party macros to be installed in the local directory
1190 specified with the first -I flag. This option also uses #serial
1191 lines in M4 files to upgrade local macros.
1193 The new aclocal options --dry-run and --diff help to review changes
1194 before they are installed.
1196 - aclocal now outputs an autoconf version check in aclocal.m4 in
1197 projects using automake.
1199 For a few years, automake and aclocal have been calling autoconf
1200 (or its underlying engine autom4te) to accurately retrieve the
1201 data they need from configure.ac and its siblings. Doing so can
1202 only work if all autotools use the same version of autoconf. For
1203 instance a Makefile.in generated by automake for one version of
1204 autoconf may stop working if configure is regenerated with another
1205 version of autoconf, and vice versa.
1207 This new version check ensures that the whole build system has
1208 been generated using the same autoconf version.
1210 * Support for new Autoconf macros:
1212 - The new AC_REQUIRE_AUX_FILE Autoconf macro is supported.
1214 - If `subdir-objects' is set, and AC_CONFIG_LIBOBJ_DIR is specified,
1215 $(LIBOBJS), $(LTLIBOBJS), $(ALLOCA), and $(LTALLOCA) can be used
1216 in different directories. However, only one instance of such a
1217 library objects directory is supported.
1219 * Change to Libtool support:
1221 - Libtool generic flags (those that go before the --mode=MODE option)
1222 can be specified using AM_LIBTOOLFLAGS and target_LIBTOOLFLAGS.
1224 * Yacc and Lex changes:
1226 - The rebuild rules for distributed Yacc and Lex output will avoid
1227 overwriting existing files if AM_MAINTAINER_MODE and maintainer-mode
1230 - ylwrap is now always used for lex and yacc source files,
1231 regardless of whether there is more than one source per directory.
1233 * Languages changes:
1235 - Preprocessed assembler (*.S) compilation now honors CPPFLAGS,
1236 AM_CPPFLAGS and per-target _CPPFLAGS, and supports dependency
1237 tracking, unlike non-preprocessed assembler (*.s).
1239 - subdir-object mode works now with Assembler. Automake assumes
1240 that the compiler understands `-c -o'.
1242 - Preprocessed assembler (*.S) compilation now also honors
1243 $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES).
1245 - Improved support for Objective C:
1246 - Autoconf's new AC_PROG_OBJC will enable automatic dependency tracking.
1247 - A new section of the manual documents the support.
1249 - New support for Unified Parallel C:
1250 - AM_PROG_UPC looks for a UPC compiler.
1251 - A new section of the manual documents the support.
1253 - Per-target flags are now correctly handled in link rules.
1255 For instance maude_CFLAGS correctly overrides AM_CFLAGS; likewise
1256 for maude_LDFLAGS and AM_LDFLAGS. Previous versions bogusly
1257 preferred AM_CFLAGS over maude_CFLAGS while linking, and they
1258 used both AM_LDFLAGS and maude_LDFLAGS on the same link command.
1260 The fix for compiler flags (i.e., using maude_CFLAGS instead of
1261 AM_CFLAGS) should not hurt any package since that is how _CFLAGS
1262 is expected to work (and actually works during compilation).
1264 However using maude_LDFLAGS "instead of" AM_LDFLAGS rather than
1265 "in addition to" breaks backward compatibility with older versions.
1266 If your package used both variables, as in
1268 AM_LDFLAGS = common flags
1269 bin_PROGRAMS = a b c
1270 a_LDFLAGS = more flags
1273 and assumed *_LDFLAGS would sum up, you should rewrite it as
1275 AM_LDFLAGS = common flags
1276 bin_PROGRAMS = a b c
1277 a_LDFLAGS = $(AM_LDFLAGS) more flags
1280 This new behavior of *_LDFLAGS is more coherent with other
1281 per-target variables, and the way *_LDFLAGS variables were
1282 considered internally.
1284 * New installation targets:
1286 - New targets mandated by GNU Coding Standards:
1291 By default they will only install Texinfo manuals.
1292 You can customize them with *-local variants:
1298 - The undocumented recursive target `uninstall-info' no longer exists.
1299 (`uninstall' is in charge of removing all possible documentation
1300 flavors, including optional formats such as dvi, ps, or info even
1301 when `no-installinfo' is used.)
1303 * Miscellaneous changes:
1305 - Automake no longer complains if input files for AC_CONFIG_FILES
1306 are specified using shell variables.
1308 - clean, distribution, or rebuild rules are normally disabled for
1309 inputs and outputs of AC_CONFIG_FILES, AC_CONFIG_HEADERS, and
1310 AC_CONFIG_LINK specified using shell variables. However, if these
1311 variables are used as ${VAR}, and AC_SUBSTed, then Automake will
1312 be able to output rules anyway.
1313 (See the Automake documentation for AC_CONFIG_FILES.)
1315 - $(EXEEXT) is automatically appended to filenames of TESTS
1316 that have been declared as programs in the same Makefile.
1317 This is mostly useful when some check_PROGRAMS are listed in TESTS.
1319 - `-Wportability' has finally been turned on by default for `gnu' and
1320 `gnits' strictness. This means, automake will complain about %-rules
1321 or $(GNU Make functions) unless you switch to `foreign' strictness or
1322 use `-Wno-portability'.
1324 - Automake now uses AC_PROG_MKDIR_P (new in Autoconf 2.60), and uses
1325 $(MKDIR_P) instead of $(mkdir_p) to create directories. The
1326 $(mkdir_p) variable is still defined (to the same value as
1327 $(MKDIR_P)) but should be considered obsolete. If you are using
1328 $(mkdir_p) in some of your rules, please plan to update them to
1329 $(MKDIR_P) at some point.
1331 - AM_C_PROTOTYPES and ansi2knr are now documented as being obsolete.
1332 They still work in this release, but may be withdrawn in a future one.
1334 - Inline compilation rules for gcc3-style dependency tracking are
1337 - Automake installs a "Hello World!" example package in $(docdir).
1338 This example is used throughout the new "Autotools Introduction"
1339 chapter of the manual.
1341 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1345 * Makefile.in bloat reduction:
1347 - Inference rules are used to compile sources in subdirectories when
1348 the `subdir-objects' option is used and no per-target flags are
1349 used. This should reduce the size of some projects a lot, because
1350 Automake used to output an explicit rule for each such object in
1353 - Automake no longer outputs three rules (.o, .obj, .lo) for each
1354 object that must be built with explicit rules. It just outputs
1355 the rules required to build the kind of object considered: either
1356 the two .o and .obj rules for usual objects, or the .lo rule for
1359 * Change to Libtool support:
1361 - Libtool tags are used with libtool versions that support them.
1362 (I.e., with Libtool 1.5 or greater.)
1364 - Automake is now able to handle setups where a libtool library is
1365 conditionally installed in different directories, as in
1368 lib_LTLIBRARIES = liba.la
1370 pkglib_LTLIBRARIES = liba.la
1372 liba_la_SOURCES = ...
1374 * Changes to aclocal:
1376 - aclocal now ensures that AC_DEFUNs and AU_DEFUNs it discovers are
1377 really evaluated, before it decides to include them in aclocal.m4.
1378 This solves nasty problems with conditional redefinitions of
1379 Autoconf macros in /usr/share/aclocal/*.m4 files causing extraneous
1380 *.m4 files to be included in any project using these macros.
1381 (Calls to AC_PROG_EGREP causing libtool.m4 to be included is the
1382 most famous instance of this bug.)
1384 - Do not complain about missing conditionally AC_REQUIREd macros
1385 that are not actually used. In 1.8.x aclocal would correctly
1386 determine which of these macros were really needed (and include
1387 only these in the package); unfortunately it would also require
1388 all of them to be present in order to run. This created
1389 situations were aclocal would not work on a tarball distributing
1390 all the macros it uses. For instance running aclocal on a project
1391 containing only the subset of the Gettext macros in use by the
1392 project did not work, because gettext conditionally requires other
1395 * Portability improvements:
1397 - Tar format can be chosen with the new options tar-v7, tar-ustar, and
1398 tar-pax. The new option filename-length-max=99 helps diagnosing
1399 filenames that are too long for tar-v7. (PR/414)
1401 - Variables aumented with `+=' are now automatically flattened (i.e.,
1402 trailing backslashes removed) and then wrapped around 80 colummns
1403 (adding trailing backslashes). In previous versions, a long series
1409 would result in a single-line definition of VAR that could possibly
1410 exceed the maximum line length of some make implementations.
1412 Non-augmented variables are still output as they are defined in
1417 - Support Fortran 90/95 with the new "fc" and "ppfc" languages.
1418 Works the same as the old Fortran 77 implementation; just replace
1419 F77 with FC everywhere (exception: FFLAGS becomes FCFLAGS).
1420 Requires a version of autoconf which provides AC_PROG_FC (>=2.59).
1422 - Support for conditional _LISP.
1424 - Support for conditional -hook and -local rules (PR/428).
1426 - Diagnose AC_CONFIG_AUX_DIR calls following AM_INIT_AUTOMAKE. (PR/49)
1428 - Automake will not write any Makefile.ins after the first error it
1429 encounters. The previous Makefile.ins (if any) will be left in
1430 place. (Warnings will not prevent output, but remember they can
1431 be turned into errors with -Werror.)
1433 - The restriction that SUBDIRS must contain direct children is gone.
1436 - The manual tells more about SUBDIRS vs. DIST_SUBDIRS.
1437 It also gives an example of nested packages using AC_CONFIG_SUBDIRS.
1439 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1441 Bugs fixed in 1.8.5:
1443 * Long-standing bugs:
1445 - Define DIST_SUBDIRS even when the `no-dist' or `cygnus' options are used
1446 so that `make distclean' and `make maintainer-clean' can work.
1448 - Define AR and ARFLAGS even when only EXTRA_LIBRARIES are defined.
1450 - Fix many rules to please FreeBSD make, which runs commands with `sh -e'.
1452 - Polish diagnostic when no input file is found.
1454 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1456 Bugs fixed in 1.8.4:
1458 * Long-standing bugs:
1460 - Fix AM_PATH_PYTHON to correctly display $PYTHON when it has been
1461 overridden by the user.
1463 - Honor PATH_SEPARATOR in various places of the Automake package, for
1466 - Adjust dependency tracking mode detection to ICC 8.0's new output.
1469 - Fix install-sh so it can install the `mv' binary... using `mv'.
1471 - Fix tru64 dependency tracking for libtool objects.
1473 - Work around Exuberant Ctags when creating a TAGS files in a directory
1474 without files to scan but with subdirectories to include.
1476 * Bugs introduced by 1.8:
1478 - Fix an "internal error" when @LIBOBJS@ is used in a variable that is
1479 not defined in the same conditions as the _LDADD that uses it.
1481 - Do not warn when JAVAROOT is overridden, this is legitimate.
1483 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1485 Bugs fixed in 1.8.3:
1487 * Long-standing bugs:
1489 - Quote filenames in installation rules, in case $DESTDIR, $prefix,
1490 or any of the other *dir variables contain a space.
1492 Please note that Automake does not and cannot support spaces in
1493 filenames that are involved during the build. This change affects
1494 only installation paths, so that `make install' does not bomb out
1495 in packages configured with
1496 ./configure --prefix '/c/Program Files'
1498 - Fix the depfiles output so it works with GNU sed (<4.1) even when
1499 POSIXLY_CORRECT is set.
1501 - Do not AC_SUBST(LIBOBJS) in AM_WITH_REGEX. This macro was unusable
1502 since Autoconf 2.54, which defines LIBOBJS itself.
1504 - Fix a potential (but unlikely) race condition in parallel elisp
1505 builds. (Introduced in 1.7.3.)
1507 - Do not assume that users override _DEPENDENCIES in all conditions
1508 where Automake will try to define them.
1510 - Do not use `mkdir -p' in mkinstalldirs, unless this is GNU mkdir.
1511 Solaris 8's `mkdir -p' is not thread-safe and can break parallel
1514 This fix also affects the $(mkdir_p) variable defined since
1515 Automake 1.8. It will be set to `mkdir -p' only if mkdir is GNU
1516 mkdir, and to `mkinstalldirs' or `install-sh -d' otherwise.
1518 - Secure temporary directory creation in `make distcheck'. (PR/413)
1520 - Do not generate two build rules for `parser.h' when the
1521 parser appears in two different conditionals.
1523 - Work around a Solaris 8 /bin/sh bug in the test for dependency
1524 checking. Usually ./configure will not pick this shell; so this
1525 fix only helps cases where the shell is forced to /bin/sh.
1527 * Bugs introduced by 1.8:
1529 - In some situations (hand-written `m4_include's), aclocal would
1530 call the `File::Spec->rel2abs' method, which was only introduced
1531 in Perl 5.6. This new version reestablish support Perl 5.005.
1533 It is likely that the next major Automake releases will require at
1534 least Perl 5.6. Consider upgrading your development environment
1535 if you are still using the five-year-old Perl 5.005.
1537 - Automake would sometimes fail to define rules for targets listed
1538 in variables defined in multiple conditions. For instance on
1544 it would define only the `a.$(OBJEXT): a.c' rule and omit the
1545 `b.$(OBJEXT): b.c' rule.
1547 * New sections in manual:
1549 - Third-Party Makefiles: how to interface third party Makefiles.
1550 - Upgrading: upgrading packages to newer Automake versions.
1551 - Multiple Outputs: handling tools that produce many outputs.
1553 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1557 * A (well known) portability bug slipped in the changes made to
1558 install-sh in Automake 1.8.1. The broken install-sh would refuse to
1559 install anything on Tru64.
1561 * Fix install rules for conditionally built python files. (This never
1564 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1568 * Bugs introduced by 1.8:
1570 - Fix Config.pm import error with old Perl versions (at least
1571 5.005_03). One symptom is that aclocal could not find its macro
1574 - Automake 1.8 used `mkdir -m 0755 -p --' to ensure that directories
1575 created by `make install' are always world readable, even if the
1576 installer happens to have an overly restrictive umask (e.g. 077).
1577 This was a mistake and has been reverted. There are at least two
1578 reasons why we must not use `-m 0755':
1579 - it causes special bits like SGID to be ignored,
1580 - it may be too restrictive (some setups expect 775 directories).
1582 - Fix aclocal to honor definitions located in files which have been
1583 m4_included manually. aclocal 1.8 had been updated to check
1584 m4_included files for new requirements, but forgot that these
1585 m4_included files can also provide new definitions.
1587 Note that if you have such a setup, we recommend you get rid of
1588 it. In the past, there was a reason to m4_include files manually:
1589 aclocal used to duplicate entire M4 files into aclocal.m4, even
1590 files that were distributed. Some packages were therefore
1591 m4_including the distributed file directly, and playing some
1592 tricks to ensure aclocal would not copy that file to aclocal.m4,
1593 in order to limit the amount of duplication. Since aclocal 1.8.x
1594 will precisely output m4_includes for local M4 files, we recommend
1595 that you clean up your setup, removing all manual m4_includes and
1596 letting aclocal output them.
1598 - Output detailed menus in the Info version if the Automake manual,
1599 so that Emacs can locate the indexes.
1601 - configure.ac and configure were listed twice in DIST_COMMON (an
1602 internal variable where Automake lists configury files to
1603 distribute). This was harmless, but unaesthetic.
1605 - Use `chmod a-w' instead of `chmod -w' as the latter honors umask.
1606 This was an issue only in the Automake package itself, not in
1609 - Automake assumed that all AC_CONFIG_LINKS arguments had the form
1610 DEST:SRC. This was wrong, as some packages do
1611 AC_CONFIG_LINKS($computedlinks). This version no longer abort in
1614 - Contrary to mkinstalldirs, $(mkdir_p) was expecting exactly one
1615 argument. This caused two kinds of failures:
1616 - Rules installing data in a conditionally defined directory
1617 failed when that directory was undefined. In this case no
1618 argument was supplied.
1619 - `make installdirs' failed, because several directories were
1620 passed to $(mkdir_p). This was an issue only on platform
1621 were $(mkdir_p) is implemented with `install-sh -d'.
1622 $(mkdir_p) as been changed to accept 0 or more arguments, as
1625 * Long-standing bugs:
1627 - Fix an unexpected diagnostic occurring when users attempt
1628 to override some internal variables that Automake appends to.
1630 - aclocal now scans configure.ac for macro definitions (PR/319).
1632 - Fix a portability issue with OSF1/Tru64 Make. If a directory
1633 distributes files which are outside itself (this usually occurs
1634 when using AC_CONFIG_AUX_DIR([../dir]) to use auxiliary files
1635 from a parent package), then `make distcheck' fails due to an
1636 optimization performed by OSF1/Tru64 Make in its VPATH handling.
1637 (tests/subpkg2.test failure)
1639 - Fix another portability issue with Sun and OSF1/Tru64 Make.
1640 In a VPATH-build configuration, `make install' would install
1641 nobase_ files to wrong locations.
1643 - Fix a Perl `uninitialized value' diagnostic occurring when
1644 automake complains that a Texinfo file does not have a
1645 @setfilename statement.
1647 - Erase config.status.lineno during `make distclean'. This file
1648 can be created by config.status. Automake already knew about
1649 configure.lineno, but forgot config.status.lineno.
1651 - Distribute all files, even those which are built and installed
1652 conditionally. This change affects files listed in conditionally
1653 defined *_HEADERS and *_PYTHON variable (unless they are nodist_*)
1654 as well as those listed in conditionally defined dist_*_DATA,
1655 dist_*_JAVA, dist_*_LISP, and dist_*_SCRIPTS variables.
1657 - Fix AM_PATH_LISPDIR to avoid \? in sed regular expressions; it
1658 doesn't conform to POSIX.
1660 - Normalize help strings for configure variables and options added
1665 - Check for python2.4 in AM_PATH_PYTHON.
1667 * Spurious failures in test suite:
1669 - tests/libtool5.test, tests/ltcond.test, tests/ltcond2.test,
1670 tests/ltconv.test: fix failures with CVS Libtool.
1671 - tests/aclocal6.test: fix failure if autom4te.cache is disabled.
1672 - tests/txinfo24.test, tests/txinfo25.test, tests/txinfo28.test:
1673 fix failures with old Texinfo versions.
1675 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1681 - The NEWS file is more verbose.
1685 - Autoconf 2.58 or greater is required.
1689 - Default source file names in the absence of a _SOURCES declaration
1690 are made by removing any target extension before appending `.c', so
1691 to make the libtool module `foo.la' from `foo.c', you only need to
1694 lib_LTLIBRARIES = foo.la
1695 foo_la_LDFLAGS = -module
1697 For backward compatibility, foo_la.c will be used instead of
1698 foo.c if this file exists or is the explicit target of a rule.
1699 However -Wobsolete will warn about this deprecated naming.
1701 - AR's `cru' flags are now set in a global ARFLAGS variable instead
1702 of being hard-coded in each $(AR) invocation, so they can be
1703 substituted from configure.ac. This has been requested by people
1704 dealing with non-POSIX ar implementations.
1706 - New warning option: -Woverride. This will warn about any user
1707 target or variable definitions which override Automake
1710 - Texinfo rules back up and restore info files when makeinfo fails.
1712 - Texinfo rules now support the `html' target.
1713 Running this requires Texinfo 4.0 or greater.
1715 `html' is a new recursive target, so if your package mixes
1716 hand-crafted `Makefile.in's with Automake-generated
1717 `Makefile.in's, you should adjust the former to support (or
1718 ignore) this target so that `make html' recurses successfully. If
1719 you had a custom `html' rule in your `Makefile.am', it's better to
1720 rename it as `html-local', otherwise your rule will override
1721 Automake's new rule (you can check that by running `automake
1722 -Woverride') and that will stop the recursion to subdirectories.
1724 Last but not least, this `html' rule is declared PHONY, even when
1725 overridden. Fortunately, it appears that few packages use a
1726 non-PHONY `html' rule.
1728 - Any file which is m4_included from configure.ac will appear as a
1729 configure and Makefile.in dependency, and will be automatically
1732 - The rules for rebuilding Makefiles and Makefile.ins will now
1733 rebuild all Makefiles and all Makefile.ins at once when one of
1734 configure's dependencies has changed. This is considerably faster
1735 than previous implementations, where config.status and automake
1736 were run separately in each directory (this still happens when you
1737 change a Makefile.am locally, without touching configure.ac or
1738 friends). Doing this also solves a longstanding issue: these
1739 rebuild rules failed to work when adding new directories to the
1740 tree, forcing you to run automake manually.
1742 - For similar reasons, the rules to rebuild configure,
1743 config.status, and aclocal.m4 are now defined in all directories.
1744 Note that if you were using the CONFIG_STATUS_DEPENDENCIES and
1745 CONFIGURE_DEPENDENCIES (formerly undocumented) variables, you
1746 should better define them in all directories. This is easily done
1747 using an AC_SUBST (make sure you prefix these dependencies with
1748 $(top_srcdir) since this variable will appear at different
1749 levels of the build tree).
1751 - aclocal will now use `m4_include' instead of copying local m4
1752 files into aclocal.m4. (Local m4 files are those you ship with
1753 your project, other files will be copied as usual.)
1755 Because m4_included files are automatically distributed, it means
1756 for most projects there is no point in EXTRA_DISTing the list of
1757 m4 files which are used. (You can probably get rid of
1758 m4/Makefile.am if you had one.)
1760 - aclocal will avoid touching aclocal.m4 when possible, so that
1761 Autom4te's cache isn't needlessly invalidated. This behavior can
1762 be switched off with the new `--force' option.
1764 - aclocal now uses Autoconf's --trace to detect macros which are
1765 actually used and will no longer include unused macros simply
1766 because they where mentioned. This was often the case for macros
1767 called conditionally.
1769 - New options no-dist and no-dist-gzip.
1771 - compile, depcomp, elisp-comp, install-sh, mdate-sh, mkinstalldirs,
1772 py-compile, and ylwrap, now all understand --version and --help.
1774 - Automake will now recognize AC_CONFIG_LINKS so far as removing created
1775 links as part of the distclean target and including source files in
1778 - AM_PATH_PYTHON now supports ACTION-IF-FOUND and ACTION-IF-NOT-FOUND
1779 argument. The latter can be used to override the default behavior
1780 (which is to abort).
1782 - Automake will exit with $? = 63 on version mismatch. (So does
1783 Autoconf 2.58) missing knows this, and in this case it will
1784 emulate the tools as if they were absent. Because older versions
1785 of Automake and Autoconf did not use this exit code, this change
1786 will only be useful in projects generated with future versions of
1789 - When using AC_CONFIG_FILES with multiple input files, Automake
1790 generates the first ".in" input file for which a ".am" exists.
1791 (Former versions would try to use only the first input file.)
1793 - lisp_DATA is now allowed. If you are using the empty ELCFILES
1794 idiom to disable byte-compilation of lisp_LISP files, it is
1795 recommended that you switch to using lisp_DATA. Note that
1796 this is not strictly equivalent: lisp_DATA will install elisp
1797 files even if emacs is not installed, while *_LISP do not
1798 install anything unless emacs is found.
1800 - Makefiles will prefer `mkdir -p' over mkinstalldirs if it is
1801 available. This selection is achieved through the Makefile
1802 variable $(mkdir_p) that is set by AM_INIT_AUTOMAKE to either
1803 `mkdir -m 0755 -p --', `$(mkinstalldirs) -m 0755', or
1804 `$(install_sh) -m 0755 -d'.
1808 - Because `mkdir -p' is available on most platforms, and we can use
1809 `install-sh -d' when it is not, the use of the mkinstalldirs
1810 script is being phased out. `automake --add-missing' no longer
1811 installs it, and if you remove mkinstalldirs from your package,
1812 automake will define $(mkinstalldirs) as an alias for $(mkdir_p).
1814 Gettext 0.12.1 still requires mkinstalldirs. Fortunately
1815 gettextize and autopoint will install it when needed. Automake
1816 will continue to define the $(mkinstalldirs) and to distribute
1817 mkinstalldirs when this script is in the source tree.
1819 - AM_PROG_CC_STDC is now empty. The content of this macro was
1820 merged in AC_PROG_CC. If your code uses $am_cv_prog_cc_stdc, you
1821 should adjust it to use $ac_cv_prog_cc_stdc instead. (This
1822 renaming should be safe, even if you have to support several,
1823 versions of Automake, because AC_PROG_CC defines this variable
1824 since Autoconf 2.54.)
1826 - Some users where using the undocumented ACLOCAL_M4_SOURCES
1827 variable to override the aclocal.m4 dependencies computed
1828 (inaccurately) by older versions of Automake. Because Automake
1829 now tracks configure's m4 dependencies accurately (see m4_include
1830 above), the use of ACLOCAL_M4_SOURCES should be considered
1831 obsolete and will be flagged as such when running `automake
1836 - Defining programs conditionally using Automake conditionals no
1837 longer leads to a combinatorial explosion. The following
1838 construct used to be troublesome when used with dozens of
1853 Likewise for _SOURCES, _LDADD, and _LIBADD variables.
1855 - Due to implementation constraints, previous versions of Automake
1856 proscribed multiple conditional definitions of some variables
1866 All _PROGRAMS, _LDADD, and _LIBADD variables were affected.
1867 This restriction has been lifted, and these variables now
1868 support multiple conditional definitions as do other variables.
1870 - Cleanup the definitions of $(distdir) and $(top_distdir).
1871 $(top_distdir) now points to the root of the distribution
1872 directory created during `make dist', as it did in Automake 1.4,
1873 not to the root of the build tree as it did in intervening
1874 versions. Furthermore these two variables are now only defined in
1875 the top level Makefile, and passed to sub-directories when running
1878 - The --no-force option now correctly checks the Makefile.in's
1879 dependencies before deciding not to update it.
1881 - Do not assume that make files are called Makefile in cleaning rules.
1883 - Update .info files in the source tree, not in the build tree. This
1884 is what the GNU Coding Standard recommend. Only Automake 1.7.x
1885 used to update these files in the build tree (previous versions did
1886 it in the source tree too), and it caused several problems, varying
1887 from mere annoyance to portability issues.
1889 - COPYING, COPYING.LIB, and COPYING.LESSER are no longer overwritten
1890 when --add-missing and --force-missing are used. For backward
1891 compatibility --add-missing will continue to install COPYING (in
1892 `gnu' strictness) when none of these three files exist, but this
1893 use is deprecated: you should better choose a license yourself and
1894 install it once for all in your source tree (and in your code
1897 - Fix ylwrap so that it does not overwrite header files that haven't
1898 changed, as the inline rule already does.
1900 - User-defined rules override automake-defined rules for the same
1901 targets, even when rules do not have commands. This is not new
1902 (and was documented), however some of the automake-generated
1903 rules have escaped this principle in former Automake versions.
1904 Rules for the following targets are affected by this fix:
1906 clean, clean-am, dist-all, distclean, distclean-am, dvi, dvi-am,
1907 info, info-am, install-data-am, install-exec-am, install-info,
1908 install-info-am, install-man, installcheck-am, maintainer-clean,
1909 maintainer-clean-am, mostlyclean, mostlyclean-am, pdf, pdf-am,
1910 ps, ps-am, uninstall-am, uninstall-info, uninstall-man
1912 Practically it means that an attempt to supplement the dependencies
1913 of some target, as in
1915 clean: my-clean-rule
1917 will now *silently override* the automake definition of the
1918 rule for this target. Running `automake -Woverride' will diagnose
1919 all such overriding definitions.
1921 It should be noted that almost all of these targets support a *-local
1922 variant that is meant to supplement the automake-defined rule
1923 (See node `Extending' in the manual). The above rule should
1926 clean-local: my-clean-rule
1928 These *-local targets have been documented since at least
1929 Automake 1.2, so you should not fear the change if you have
1930 to support multiple automake versions.
1934 - The Automake manual is now distributed under the terms of the GNU FDL.
1936 - Targets dist-gzip, dist-bzip2, dist-tarZ, dist-zip are always defined.
1938 - core dumps are no longer removed by the cleaning rules. There are
1939 at least three reasons for this:
1940 1. These files should not be created by any build step,
1941 so their removal do not fit any of the cleaning rules.
1942 Actually, they may be precious to the developer.
1943 2. If such file is created during a build, then it's clearly a
1944 bug Automake should not hide. Not removing the file will
1945 cause `make distcheck' to complain about its presence.
1946 3. Operating systems have different naming conventions for
1947 core dump files. A core file on one system might be a
1948 completely legitimate data file on another system.
1950 - RUNTESTFLAGS, CTAGSFLAGS, ETAGSFLAGS, JAVACFLAGS are no longer
1951 defined by Automake. This means that any definition in the
1952 environment will be used, unless overridden in the Makefile.am or
1953 on the command line. The old behavior, where these variables were
1954 defined empty in each Makefile, can be obtained by AC_SUBSTing or
1955 AC_ARG_VARing each variable from configure.ac.
1957 - CONFIGURE_DEPENDENCIES and CONFIG_STATUS_DEPENDENCIES are now
1958 documented. (The is not a new feature, these variables have
1959 been there since at least Automake 1.4.)
1961 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1963 Bugs fixed in 1.7.9:
1964 * Fix install-strip to work with nobase_ binaries.
1965 * Fix renaming of #line directives in ylwrap.
1966 * Rebuild with Autoconf 2.59. (1.7.8 was not installable with pdksh.)
1968 Bugs fixed in 1.7.8:
1969 * Remove spurious blank lines in cleaning rules introduced in 1.7.7.
1970 * Fix detection of Debian's install-info, broken since version 1.5.
1971 (Debian bug #213524).
1972 * Honor -module if it appears in AM_LDFLAGS (i.e., relax name checking)
1973 This was only done for libfoo_LDFLAGS and LDFLAGS in previous versions.
1975 Bugs fixed in 1.7.7:
1976 * The implementation of automake's --no-force option is unreliable,
1977 so this option is ignored in this version. A real fix will appear in
1978 Automake 1.8. (Debian Bug #206299)
1979 * AM_PATH_PYTHON: really check the whole list of interpreters if no
1980 argument is given. (PR/399)
1981 * Do not warn about leading `_' in variable names, even with -Wportability.
1982 * Support user redefinitions of TEXINFO_TEX.
1983 * depcomp: support AIX Compiler version 6.
1984 * Fix missing rebuilds during `make dist' with BSD make.
1985 (Could produce tarballs containing out-of-date files.)
1986 * Resurrect multilib support.
1987 * Noteworthy manual updates:
1988 - Extending aclocal: how to write m4 macros that won't trigger warnings
1990 - A Shared Library: Rewrite and split into subsections.
1992 Bugs fixed in 1.7.6:
1993 * Fix depcomp's icc mode for ICC 7.1.
1994 * Diagnose calls to AC_CONFIG_FILES and friends with not enough arguments.
1995 * Fix maintainer-clean's removal of autom4te.cache in VPATH builds.
1996 * Fix AM_PATH_LISPDIR to work with POSIXLY_CORRECT=1.
1997 * Fix the location reported in some diagnostics related to AUTOMAKE_OPTIONS.
1998 * Remove Latin-1 characters from elisp-comp.
1999 * Update the manual's @dircategory to match the Free Software Directory.
2001 Bugs fixed in 1.7.5:
2002 * Update install-sh's license to remove an advertising clause.
2003 (Debian bug #191717)
2004 * Fix a bug introduced in 1.7.4, related to BUILT_SOURCE handling,
2005 that caused invalid Makefile.ins to be generated.
2006 * Make sure AM_MAKE_INCLUDE doesn't fail when a `doit' file exists.
2007 * New FAQ entry: renamed objects.
2009 Bugs fixed in 1.7.4:
2010 * Tweak the TAGS rule to support Exuberant Ctags (in addition to
2011 the Emacs implementation)
2012 * Fix output of aclocal.m4 dependencies in subdirectories.
2013 * Use `mv -f' instead of `mv' in fastdep rules.
2014 * Upgrade mdate-sh to work on OS/2.
2015 * Don't byte-compile elisp files when ELCFILES is set empty.
2016 (this documented feature was broken by 1.7.3)
2017 * Diagnose trailing backslashes on last line of Makefile.am.
2018 * Diagnose whitespace following trailing backslashes.
2019 * Multiple tests are now correctly supported in DEJATOOL. (PR/388)
2020 * Fix rebuilt rules for AC_CONFIG_FILES([Makefile:Makefile.in:Makefile.bot])
2022 * `make install' will build `BUILT_SOURCES' first.
2023 * Minor documentation fixes.
2025 Bugs fixed in 1.7.3:
2026 * Fix stamp files numbering (when using multiple AC_CONFIG_HEADERS).
2027 * Query distutils for `pythondir' and `pythonexecdir', instead of
2028 using an hardcoded path. This should allow builds on 64-bit
2029 distributions that usually use lib64/ instead of lib/.
2030 * AM_PATH_PYTHON will also search for python2.3.
2031 * elisp files are now built all at once instead of one by one. Besides
2032 incurring a speed-up, this is required to support interdependent elisp files.
2033 * Support for DJGPP:
2034 - `make distcheck' will now work in `_inst/' and `_build' instead
2035 of `=inst/' and `=build/'
2036 - use `_dirstamp' when the file-system doesn't support `.dirstamp'
2037 - install/uninstall `*.i[0-9][0-9]'-style info files
2038 - more changes that affect only the Automake package (not its output)
2039 * Fix some incompatibilities with upcoming perl-5.10.
2040 * Properly quote AC_PACKAGE_TARNAME and AC_PACKAGE_VERSION when defining
2041 PACKAGE and VERSION.
2043 - dashmstdout and dashXmstdout modes: don't use `-o /dev/null', this
2044 is troublesome with gcc and Solaris compilers. (PR/385)
2045 - makedepend mode: work with Libtool. (PR/385 too)
2047 * better support for unusual gettext setups, such as multiple po/ directories
2049 - Flag missing po/ and intl/ directories as warnings, not errors.
2050 - Disable these warnings if po/ does not exist.
2051 * Noteworthy manual updates:
2053 - Document how AC_CONFIG_AUX_DIR interacts with missing files.
2055 - Document `AM_YFLAGS = -d'. (PR/382)
2057 Bugs fixed in 1.7.2:
2058 * Fix installation and uninstallation of Info files built in subdirectories.
2059 * Do not run `./configure --with-included-gettext' during `make distcheck'
2060 if AM_GNU_GETTEXT([external]) is used.
2061 * Correctly uninstall renamed man pages.
2062 * Do not strip escaped newline in variables defined in one condition
2063 and augmented in another condition.
2064 * Fix ansi2knr rules for LIBOBJS sources.
2065 * Clean all known Texinfo index files, not only those which appear to
2066 be used, because we cannot know which indexes are used in included files.
2067 (PR/375, Debian Bug #168671)
2068 * Honor only the first @setfilename seen in a Texinfo file.
2069 * Treat "required file X not found" diagnostics as errors (exit status 1).
2070 * Don't complain that a required file is not found when it is a Makefile
2072 * Don't use single suffix inference rules when building `.info'-less
2073 Info files, for the sake of Solaris make.
2074 * The `check' target now depends on `$(BUILT_SOURCES)'. (PR/359)
2075 * Recognize multiple inference rules such as `.a.b .c.d:'. (PR/371)
2076 * Warn about multiple inference rules when -Wportability is used. (PR/372)
2077 * Fix building of deansified files from subdirectories. (PR/370)
2078 * Add missing `fi' in the .c->.obj rules.
2079 * Improve install-sh to work even when names contain spaces or certain
2080 (but not all) shell metachars.
2081 * Fix the following spurious failures in the test suite:
2082 depcomp2.test, gnits2.test, gnits3.test, python3.test, texinfo13.test
2083 * Noteworthy manual updates:
2084 - Augment the section about BUILT_SOURCES.
2085 - Mention that AM_PROG_CC_STDC is a relic that is better avoided today.
2087 Bugs fixed in 1.7.1:
2088 * Honor `ansi2knr' for files built in subdirectories, or using per-targets
2090 * Aclocal should now recognize macro names containing parentheses, e.g.
2091 AC_DEFUN([AC_LANG_PREPROC(Fortran 90)], [...]).
2092 * Erase *.sum and *.log files created by DejaGnu, during `make distclean'.
2094 * Install Python files even if they were built. (PR/369)
2095 * Have stamp-vti dependent upon configure instead of configure.ac, as the
2096 version might not be defined in the latter. (PR/358)
2097 * Reorder arguments passed to a couple of commands, so things works
2098 when POSIXLY_CORRECT=1.
2099 * Fix a regex that can cause Perl to segfault on large input.
2101 * Fix distribution of packages that have some sources defined conditionally,
2102 as in the `Conditional compilation using Automake conditionals' example
2104 * Fix spurious test suite failures on IRIX.
2105 * Don't report a required variable as undefined if it has been
2106 defined conditionally for the "right" conditions.
2107 * Fix cleaning of the /tmp subdirectory used by `make distcheck', in case
2108 `make distcheck' fails.
2109 * Fix distribution of included Makefile fragment, so we don't create
2110 spurious directories in the distribution. (PR/366)
2111 * Don't complain that a target lacks `.$(EXEEXT)' when it has it.
2114 * Autoconf 2.54 is required.
2115 * `aclocal' and `automake' will no longer warn about obsolete
2116 configure macros. This is done by `autoconf -Wobsolete'.
2117 * AM_CONFIG_HEADER, AM_SYS_POSIX_TERMIOS and
2118 AM_HEADER_TIOCGWINSZ_NEEDS_SYS_IOCTL are obsolete (although still
2119 supported). You should use AC_CONFIG_HEADERS, AC_SYS_POSIX_TERMIOS,
2120 and AC_HEADER_TIOCGWINSZ instead. `autoupdate' can upgrade
2121 `configure.ac' for you.
2122 * Support for per-program and per-library `_CPPFLAGS'.
2123 * New `ctags' target (builds CTAGS files).
2124 * Support for -Wmumble and -Wno-mumble, where mumble is a warning category
2125 (see `automake --help' or the manual for a list of them).
2126 * Honor the WARNINGS environment variable.
2127 * Omit the call to depcomp when using gcc3: call the compiler directly.
2128 * A new option, std-options, tests that programs support --help and --version
2129 when `make installcheck' is run. This is enabled by --gnits.
2130 * Texinfo rules now support the `ps' and `pdf' targets.
2131 * Info files are now created in the build directory, not the source directory.
2132 * info_TEXINFOS supports files in subdirectories (this requires Texinfo 4.1
2134 * `make distcheck' will enforce DESTDIR support by attempting
2136 * `+=' can be used in conditionals, even if the augmented variable
2137 was defined for another condition.
2138 * Makefile fragments (inserted with `include') are always distributed.
2139 * Use Autoconf's --trace interface to inspect configure.ac and get
2140 a more accurate view of it.
2141 * Add support for extending aclocal's default macro search path
2142 using a `dirlist' file within the aclocal directory.
2143 * automake --output-dir is deprecated.
2144 * The part of the distcheck target that checks whether uninstall actually
2145 removes all installed files has been moved in a separate target,
2146 distuninstallcheck, so it can be overridden easily.
2150 * Support for AM_INIT_GETTEXT([external])
2151 * Bug fixes, including:
2152 - Fix Automake's own `make install' so it works even if `ln' doesn't.
2153 - nobase_ programs and scripts honor --program-transform correctly.
2154 - Erase configure.lineno during `make distclean'.
2155 - Erase YACC and LEX outputs during `make maintainer-clean'.
2158 * Many bug fixes, including:
2159 - Requiring the current version works.
2160 - Fix "$@" portability issues (for Zsh).
2161 - Fix output of dummy dependency files in presence of post-processed
2163 - Don't compute dependencies in background to avoid races with libtool.
2164 - Fix handling of _OBJECTS variables for targets sharing source variables.
2165 - Check dependency mode for Java when AM_PROG_GCJ is used.
2168 * automake --output-dir is deprecated
2169 * Many bug fixes, including:
2170 - Don't choke on AM_LDFLAGS definitions.
2171 - Clean libtool objects from subdirectories.
2172 - Allow configure variables with reserved suffix and unknown prefix
2173 (e.g. AC_SUBST(mumble_LDFLAGS) when 'mumble' is not a target).
2174 - Fix the definition of AUTOMAKE and ACLOCAL in configure.
2177 * Autoconf 2.52 is required.
2178 * automake no longer run libtoolize.
2179 This is the job of autoreconf (from GNU Autoconf).
2180 * `dist' generates all the archive flavors, as did `dist-all'.
2181 * `dist-gzip' generates the Gzip tar file only.
2182 * Combining Automake Makefile conditionals no longer lead to a combinatorial
2183 explosion. Makefile.in's keep a reasonable size.
2184 * AM_FUNC_ERROR_AT_LINE, AM_FUNC_STRTOD, AM_FUNC_OBSTACK, AM_PTRDIFF_T
2185 are no longer shipped, since Autoconf 2.52 provides them (both as AM_
2187 * `#line' of Lex and Yacc files are properly set.
2188 * EXTRA_DIST can contain generated directories.
2189 * Support for dot-less extensions in suffix rules.
2190 * The part of the distcheck target that checks whether distclean actually
2191 cleans all built files has been moved in a separate target, distcleancheck,
2192 so it can be overridden easily.
2193 * `make distcheck' will pass additional options defined in
2194 $(DISTCHECK_CONFIGURE_FLAGS) to configure.
2195 * Fixed CDPATH portability problems, in particular for MacOS X.
2196 * Fixed handling of nobase_ targets.
2197 * Fixed support of implicit rules leading to .lo objects.
2198 * Fixed late inclusion of --add-missing files (e.g. depcomp) in DIST_COMMON
2199 * Added uninstall-hook target
2200 * `AC_INIT AM_INIT_AUTOMAKE(tarname,version)' is an obsolete construct.
2201 You can now use `AC_INIT(pkgname,version) AM_INIT_AUTOMAKE' instead.
2202 (Note that "pkgname" is not "tarname", see the manual for details.)
2203 It is also possible to pass a list of global Automake options as
2204 first argument to this new form of AM_INIT_AUTOMAKE.
2205 * Compiler-based assembler is now called `CCAS'; people expected `AS'
2206 to be a real assembler.
2207 * AM_INIT_AUTOMAKE will set STRIP itself when it needs it. Adding
2208 AC_CHECK_TOOL([STRIP], [strip]) manually is no longer required.
2209 * aclocal and automake are also installed with the version number
2210 appended, and some of the install directory names have changed.
2211 This lets you have multiple versions installed simultaneously.
2212 * Support for parsers and lexers in subdirectories.
2215 * Support for `configure.ac'.
2216 * Support for `else COND', `endif COND' and negated conditions `!COND'.
2217 * `make dist-all' is much faster.
2218 * Allows '@' AC_SUBSTs in macro names.
2219 * Faster AM_INIT_AUTOMAKE (requires update of `missing' script)
2220 * User-side dependency tracking. Developers no longer need GNU make
2222 * Uses DIST_SUBDIRS in some situations when SUBDIRS is conditional
2223 * Most files are correctly handled if they appear in subdirs
2224 For instance, a _DATA file can appear in a subdir
2225 * GNU tar is no longer required for `make dist'
2226 * Added support for `dist_' and `nodist_' prefixes
2227 * Added support for `nobase_' prefix
2228 * Compiled Java support
2229 * Support for per-executable and per-library compilation flags
2233 * Added support for the Fortran 77 programming language.
2234 * Re-indexed the Automake Texinfo manual.
2235 * Added `AM_FOOFLAGS' variable for each compiler invocation;
2236 e.g. AM_CFLAGS can be used in Makefile.am to set C compiler flags
2237 * Support for latest autoconf, including support for objext
2238 * Can now put `.' in SUBDIRS to control build order
2239 * `include' command and `+=' support for macro assignment
2240 * Dependency tracking no long susceptible to deleted header file problem
2241 * Maintainer mode now a conditional. @MAINT@ is now an anachronism.
2246 * Better Cygwin32 support
2247 * Support for suffix rules with _SOURCES variables
2248 * New options `readme-alpha' and `check-news'; Gnits mode sets these
2249 * @LEXLIB@ no longer required when lex source seen
2250 Lex support in `missing', and new lex macro. Update your missing script.
2251 * Built-in support for assembly
2252 * aclocal gives error if `AM_' macro not found
2253 * Passed YFLAGS, not YACCFLAGS, to yacc
2254 * AM_PROG_CC_STDC does not have to come before AC_PROG_CPP
2255 * Dependencies computed as a side effect of compilation
2256 * Preliminary support for Java
2257 * DESTDIR support at "make install" time
2258 * Improved ansi2knr support; you must use the latest ansi2knr.c (included)
2262 * Better DejaGnu support
2263 * Added no-installinfo option
2264 * Added Emacs Lisp support
2265 * Added --no-force option
2266 * Included `aclocal' program
2267 * Automake will now generate rules to regenerate aclocal.m4, if appropriate
2268 * Now uses `AM_' macro names everywhere
2269 * ansi2knr option can have directory prefix (eg `../lib/ansi2knr')
2270 ansi2knr now works correctly on K&R sources
2271 * Better C++, yacc, lex support
2272 * Will compute _DEPENDENCIES variables automatically if not supplied
2273 * Will interpolate $(...) and ${...} when examining contents of a variable
2274 * .deps files now in build directory, not source directory; dependency
2275 handling generally rewritten
2276 * DATA, MANS and BUILT_SOURCES no longer included in distribution
2277 * can now put config.h into a subdir
2278 * Added dist-all target
2279 * Support for install-info program (see texinfo 3.9)
2280 * Support for "yacc -d"
2281 * configure substitutions are automatically discovered and included
2282 in generated Makefile.in
2283 * Special --cygnus mode
2284 * OMIT_DEPENDENCIES can now hold list of dependencies to be omitted
2285 when making distribution. Some dependencies are auto-ignored.
2286 * Changed how libraries are specified in _LIBRARIES variable
2287 * Full libtool support, from Gord Matzigkeit
2288 * No longer have to explicitly touch stamp-h when using AC_CONFIG_HEADER;
2289 AM_CONFIG_HEADER handles it automatically
2290 * Texinfo output files no longer need .info extension
2291 * Added `missing' support
2293 * Conditionals in Makefile.am, from Ian Taylor
2297 * distcheck target runs install and installcheck targets
2298 * Added preliminary support for DejaGnu.
2303 * More libtool fixes from Gord Matzigkeit; libtool support is still
2305 * Added support for jm_MAINTAINER_MODE
2307 * New "distcheck" target
2311 * mkinstalldirs and mdate-sh now appear in directory specified by
2313 * Removed DIST_SUBDIRS, DIST_OTHER
2314 * AC_ARG_PROGRAM only required when an actual program exists
2315 * dist-hook target now run before distribution packaged up; idea from
2316 Dieter Baron. Other hooks exist, too.
2317 * Preliminary (unfinished) support for libtool
2318 * Added short option names.
2319 * Better "dist" support when gluing together multiple packages
2323 * Documentation updates (many from François Pinard)
2324 * strictness `normal' now renamed to `foreign'
2325 * Renamed --install-missing to --add-missing
2326 * Now handles AC_CONFIG_AUX_DIR
2327 * Now handles TESTS macro
2328 * DIST_OTHER renamed to EXTRA_DIST
2329 * DIST_SUBDIRS is deprecated
2330 * @ALLOCA@ and @LIBOBJS@ now work in _LDADD variables
2331 * Better error messages in many cases
2332 * Program names are canonicalized
2333 * Added "check" prefix; from Gord Matzigkeit
2337 * configure.in scanner knows about AC_PATH_XTRA, AC_OUTPUT ":" syntax
2338 * Beginnings of a test suite
2339 * Automatically adds -I options for $(srcdir), ".", and path to config.h
2340 * Doesn't print anything when running
2341 * Beginnings of MAINT_CHARSET support
2342 * Can specify version in AUTOMAKE_OPTIONS
2343 * Most errors recognizable by Emacs' M-x next-error
2344 * Added --verbose option
2345 * All "primary" variables now obsolete; use EXTRA_PRIMARY to supply
2346 configure-generated names
2347 * Required macros now distributed in aclocal.m4
2349 * --strictness=gnu is default
2353 * More sophisticated configure.in scanning; now understands ALLOCA and
2354 LIBOBJS directly, handles AC_CONFIG_HEADER more precisely, etc.
2355 * TEXINFOS and MANS now obsolete; use info_TEXINFOS and man_MANS instead.
2356 * CONFIG_HEADER variable now obsolete
2357 * Can handle multiple Texinfo sources
2358 * Allow hierarchies deeper than 2. From Gord Matzigkeit.
2359 * HEADERS variable no longer needed; now can put .h files directly into
2360 foo_SOURCES variable.
2361 * Automake automatically rebuilds files listed in AC_OUTPUT. The
2362 corresponding ".in" files are included in the distribution.
2365 * Added --gnu and --gnits options
2366 * More standards checking
2368 * Cleaned up 'dist' targets
2369 * Added AUTOMAKE_OPTIONS variable and several options
2370 * Now scans configure.in to get some information (preliminary)
2373 * Works with Perl 4 again
2376 * Added --install-missing option.
2377 * Pretty-prints generated macros and rules
2378 * Comments in Makefile.am are placed more intelligently in Makefile.in
2379 * Generates .PHONY target
2380 * Rule or macro in Makefile.am now overrides contents of Automake file
2381 * Substantial cleanups from François Pinard
2385 * Works with Perl 4 again.
2388 * New uniform naming scheme.
2389 * --strictness option
2391 * '.c' files corresponding to '.y' or '.l' files are automatically
2393 * Many bug fixes and cleanups
2396 * Allow objects to be conditionally included in libraries via lib_LIBADD.
2399 * Bug fixes in 'clean' code.
2400 * Now generates 'installdirs' target.
2401 * man page installation reworked.
2402 * 'make dist' no longer re-creates all Makefile.in's.
2405 * Reimplemented in Perl
2406 * Added --amdir option (for debugging)
2407 * Texinfo support cleaned up.
2408 * Automatic de-ANSI-fication cleaned up.
2409 * Cleaned up 'clean' targets.
2412 * Automatic dependency tracking
2413 * More documentation
2414 * New variables DATA and PACKAGEDATA
2415 * SCRIPTS installed using $(INSTALL_SCRIPT)
2416 * No longer uses double-colon rules
2418 * Changes in advance of internationalization
2422 Copyright (C) 1995-2012 Free Software Foundation, Inc.
2424 This program is free software; you can redistribute it and/or modify
2425 it under the terms of the GNU General Public License as published by
2426 the Free Software Foundation; either version 2, or (at your option)
2429 This program is distributed in the hope that it will be useful,
2430 but WITHOUT ANY WARRANTY; without even the implied warranty of
2431 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
2432 GNU General Public License for more details.
2434 You should have received a copy of the GNU General Public License
2435 along with this program. If not, see <http://www.gnu.org/licenses/>.