Navigation:
Browse pkgsrc
(this page) 2012-08-15 22:25:05 by Thomas Klausner | Files touched by this commit (2) |  |
Log message:
Update to 1.12.3:
New in 1.12.3:
* WARNING: Future backward-incompatibilities!
- Future versions of Automake will likely drop support for the
long-deprecated 'configure.in' name for the Autoconf input file.
You are advised to use the recommended name 'configure.ac' instead.
- The long-obsolete (since automake 1.10) AM_PROG_MKDIR m4 macro will
be removed in Automake 1.13. The $(mkdir_p) make variable and the
@mkdir_p@ substitution will still remain available (as aliases of
$(MKDIR_P)) for the moment, for better backward compatibility.
- Autoconf 2.65 or later will be required by the next major Automake
version (1.13). Until now, Automake has required Autoconf version
2.62 or later.
- Starting from the next major Automake version (1.13), the rules
to build pdf, ps and dvi output from Texinfo input will use the
'--build-dir' option by default. Since such an option was only
introduced in Texinfo 4.9, this means that Makefiles generated by
future Automake versions will require at least that version of
Texinfo.
- Starting from the next major Automake version (1.13), the parallel
testsuite harness (previously only enabled by the 'parallel-tests'
option) will become the default one; the older serial testsuite
harness will still be available through the use of the 'serial-tests'
option.
- The following long-obsolete m4 macros will be removed in the
next major Automake version (1.13):
AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002
fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC
fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC
AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002
ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR
jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT
gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL
fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part
of the now-removed automatic de-ANSI-fication
support of Automake)
- All the "old alias" macros in 'm4/obsolete.m4' will be removed in
the next major Automake version (1.13).
- Support for the two- and three-arguments invocation forms of the
AM_INIT_AUTOMAKE macro is deprecated, and will be removed in the
next major Automake version (1.13).
- The '--acdir' option of aclocal is deprecated, and will probably
be removed in the next major Automake release (1.13). You should
use the options '--automake-acdir' and '--system-acdir' instead
(which have been introduced in Automake 1.11.2).
- The exact order in which the directories in the aclocal macro
search path are looked up is probably going to be changed in the
next Automake release (1.13).
- The 'missing' script will not try anymore to update the timestamp
of out-of-date files that require a maintainer-specific tool to be
remade, in case the user lacks such a tool (or has a too-old version
of it). In fact, starting from Automake 1.13, all it'll do will be
giving more useful warnings than a bare "command not found" from a
make recipe would.
* Miscellaneous changes:
- The '.m4' files provided by Automake does not define serial numbers
anymore. This should cause no difference in the behaviour of aclocal
though.
- Some testsuite weaknesses and spurious failures have been fixed.
- There is initial support for automatic dependency tracking with the
Portland Group C/C++ compilers, thanks to the new new depmode 'pgcc'.
Bugs fixed in 1.12.3:
* Long-standing bugs:
- Instead of renaming only self-references of files (typically for
#lines), ylwrap now also renames references to the other generated
files. This fixes support for GLR and C++ parsers from Bison (PR
automake/491 and automake bug#7648): 'parser.c' now properly
#includes 'parser.h' instead of 'y.tab.h'.
- Generated files unknown to ylwrap are now preserved. This fixes
C++ support for Bison (automake bug#7648): location.hh and the
like are no longer discarded.
|
| 2012-07-09 20:03:49 by Benny Siegert | Files touched by this commit (2) |
Log message: SECURITY: Update automake to 1.12.2. Fixes CVE-2012-3386: automake security fix for 'make distcheck' |
| 2012-06-03 23:18:30 by Thomas Klausner | Files touched by this commit (2) |
Log message:
Update to 1.12.1:
New in 1.12.1:
* WARNING: Future backward-incompatibilities!
- Starting from either the next minor version (1.12.2) or the next major
version (1.13), Automake will start warning if 'configure.in' is used
instead of 'configure.ac' as the Autoconf input. Future versions of
Automake will drop support for 'configure.in' altogether.
- Autoconf 2.65 or later will be required by the next major Automake
version (1.13). Until now, Automake has required Autoconf version
2.62 or later.
- Starting from the next major Automake version (1.13), the rules to
build pdf, ps and dvi output from Texinfo input will use the '--tidy'
option by default. Since such an option was introduced in Texinfo
4.9, this means that Makefiles generated by future Automake versions
will require at least that version of Texinfo.
- Starting from the next major Automake version (1.13), the parallel
testsuite harness (previously only enabled by the 'parallel-tests'
option) will become the default one; the older serial testsuite
harness will still be available through the use of the 'serial-tests'
option.
- The following long-obsolete m4 macros will be removed in the
next major Automake version (1.13):
AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002
fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC
fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC
AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002
ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR
jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT
gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL
fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part
of the now-removed automatic de-ANSI-fication
support of Automake)
- All the "old alias" macros in 'm4/obsolete.m4' will be removed in
the next major Automake version (1.13).
- Support for the two- and three-arguments invocation forms of the
AM_INIT_AUTOMAKE macro will be deprecated in the next minor version
of Automake (1.12.1) and removed in the next major version (1.13).
- The '--acdir' option of aclocal is deprecated, and will probably
be removed in the next major Automake release (1.13). You should
use the options '--automake-acdir' and '--system-acdir' instead
(which have been introduced in Automake 1.11.2).
- The exact order in which the directories in the aclocal macro
search path are looked up is probably going to be changed in the
next Automake release (1.13).
* New supported languages:
- Support for Objective C++ has been added; it should work similarly to
the support for Objective C.
* Deprecated obsolescent features:
- Use of the long-deprecated two- and three-arguments invocation forms
of the AM_INIT_AUTOMAKE macro now elicits a warning in the 'obsolete'
category. Starting from the next major Automake release (1.13), such
usages won't be allowed anymore.
- Support for the "Cygnus-style" trees (enabled by the 'cygnus' \
option) is
now deprecated (its use triggers a warning in the 'obsolete' category).
It will be removed in the next major Automake release (1.13).
- The long-obsolete (since 1.10) automake-provided $(mkdir_p) make
variable, @mkdir_p@ configure-time substitution and AM_PROG_MKDIR
m4 macro are deprecated, eliciting a warning in the 'obsolete'
category. They will be removed in the next major version (1.13).
* Miscellaneous changes:
- The Automake test cases now require a proper POSIX-conforming shell.
Older non-POSIX Bourne shells (like Solaris 10 /bin/sh) won't be
accepted anymore. In most cases, the user shouldn't have to specify
such POSIX shell explicitly, since it will be looked up at configure
time. Still, when this lookup fails, or when the user wants to
override its conclusion, the variable 'AM_TEST_RUNNER_SHELL' can be
used (pointing to the shell that will be used to run the Automake
test cases).
Bugs fixed in 1.12.1:
* Bugs introduced by 1.12:
- Several weaknesses in Automake's own build system and test suite
have been fixed.
* Bugs introduced by 1.11.3:
- When given non-option arguments, aclocal rejects them, instead of
silently ignoring them.
* Long-standing bugs:
- When the 'color-tests' option is in use, forcing of colored testsuite
output through "AM_COLOR_TESTS=always" works even if the terminal is
a non-ANSI one, i.e., if the TERM environment variable has a value of
"dumb".
- Several inefficiencies and poor performances in the implementation
of the parallel-tests 'check' and 'recheck' targets have been fixed.
- The post-processing of output "#line" directives done the ylwrap
script is more faithful w.r.t. files in a subdirectory; for example,
if the processed file is "src/grammar.y", ylwrap will correctly
produce directives like:
#line 7 "src/grammar.y"
rather than like
#line 7 "grammar.y"
as it did before.
* Bugs with new Perl versions:
- Aclocal works correctly with perl 5.16.0 (automake bug#11543).
|
| 2012-05-01 00:11:19 by David A. Holland | Files touched by this commit (1) |
Log message: Add note pointing to emulators/b-em/hacks.mk for next time. |
| 2012-04-26 22:41:17 by Thomas Klausner | Files touched by this commit (4) |
Log message:
Update to 1.12:
* WARNING: Future backward-incompatibilities!
- Starting from the next major Automake version (1.13), the rules to
build pdf, ps and dvi output from Texinfo input will use the '--tidy'
option by default. Since such an option was introduced in Texinfo
4.9, this means that Makefiles generated by future Automake versions
will require at least that version of Texinfo.
- Starting from the next major Automake version (1.13), the parallel
testsuite harness (previously only enabled by the 'parallel-tests'
option) will become the default one; the older serial testsuite
harness will still be available through the use of the 'serial-tests'
option.
- The following long-obsolete m4 macros will be removed in the
next major Automake version (1.13):
AM_PROG_CC_STDC: superseded by AC_PROG_CC since October 2002
fp_PROG_CC_STDC: broken alias for AM_PROG_CC_STDC
fp_WITH_DMALLOC: old alias for AM_WITH_DMALLOC
AM_CONFIG_HEADER: superseded by AC_CONFIG_HEADERS since July 2002
ud_PATH_LISPDIR: old alias for AM_PATH_LISPDIR
jm_MAINTAINER_MODE: old alias for AM_MAINTAINER_MODE
ud_GNU_GETTEXT: old alias for AM_GNU_GETTEXT
gm_PROG_LIBTOOL: old alias for AC_PROG_LIBTOOL
fp_C_PROTOTYPES: old alias for AM_C_PROTOTYPES (which was part
of the now-removed automatic de-ANSI-fication
support of Automake)
- All the "old alias" macros in 'm4/obsolete.m4' will be removed in
the next major Automake version (1.13).
- Support for the "Cygnus-style" trees (enabled by the 'cygnus' option)
will be deprecated in the next minor version of Automake (1.12.1) and
removed in the next major version (1.13).
- Support for the two- and three-arguments invocation forms of the
AM_INIT_AUTOMAKE macro will be deprecated in the next minor version
of Automake (1.12.1) and removed in the next major version (1.13).
- The long-obsolete (since 1.10) automake-provided $(mkdir_p) make
variable, @mkdir_p@ substitution and AM_PROG_MKDIR m4 macro will
all be deprecated in the next minor version of Automake (1.12.1)
and removed in the next major version (1.13).
- The '--acdir' option of aclocal is deprecated, and will probably
be removed in the next major Automake release (1.13). You should
use the options '--automake-acdir' and '--system-acdir' instead
(which have been introduced in Automake 1.11.2).
- The exact order in which the directories in the aclocal macro
search path are looked up is probably going to be changed in the
next Automake release (1.13).
* Obsolete features removed:
- The never documented nor truly used script 'acinstall' has been
removed.
- Support for automatic de-ANSI-fication has been removed.
- The support for the "obscure" multilib feature has been removed
from Automake core (but remains available in the 'contrib/'
directory of the Automake distribution).
- Support for ".log -> .html" conversion and the check-html and
recheck-html targets has been removed from Automake core (but
remains available in the 'contrib/' directory of the Automake
distribution).
- The deprecated 'lzma' compression format for distribution archives
has been removed, in favor of 'xz' and 'lzip'.
- The obsolete AM_WITH_REGEX macro has been removed.
- The long-deprecated options '--output-dir', '--Werror' and
'--Wno-error' have been removed.
- The chapter on the history of Automake has been moved out of the
reference manual, into a new dedicated Texinfo file.
* New targets:
- New 'cscope' target to build a cscope database for the source tree.
* Changes to Automake-generated testsuite harnesses:
- The new automake option 'serial-tests' has been introduced. It can
be used to explicitly instruct automake to use the older serial
testsuite harness. This is still the default at the moment, but it
might change in future versions.
- The 'recheck' target (provided by the parallel testsuite harness) now
depends on the 'all' target. This allows for a better user-experience
in test-driven development. See automake bug#11252.
- Test scripts that exit with status 99 to signal an "hard error" (e.g.,
and unexpected or internal error, or a failure to set up the test case
scenario) have their outcome reported as an 'ERROR' now. Previous
versions of automake reported such an outcome as a 'FAIL' (the only
difference with normal failures being that hard errors were counted
as failures even when the test originating them was listed in
XFAIL_TESTS).
- The testsuite summary displayed by the parallel-test harness has a
completely new format, that always list the numbers of passed, failed,
xfailed, xpassed, skipped and errored tests, even when these numbers
are zero (but using smart coloring when the color-tests option is in
effect).
- The default testsuite driver offered by the 'parallel-tests' option is
now implemented (partly at least) with the help of automake-provided
auxiliary scripts (e.g., 'test-driver'), instead of relying entirely
on code in the generated Makefile.in.
This has two noteworthy implications. The first one is that projects
using the 'parallel-tests' option should now either run automake with
the '--add-missing' option, or manually copy the 'test-driver' script
into their tree. The second, and more important, implication is that
now, when the 'parallel-tests' option is in use, TESTS_ENVIRONMENT can
not be used anymore to define a test runner, and the command specified
in LOG_COMPILER (and <ext>_LOG_COMPILER) must be a *real* executable
program or script. For example, this is still a valid usage (albeit
a little contorted):
TESTS_ENVIRONMENT = \
if test -n '$(STRICT_TESTS)'; then \
maybe_errexit='-e'; \
else \
maybe_errexit=''; \
fi;
LOG_COMPILER = $(SHELL) $$maybe_errexit
while this is not anymore:
TESTS_ENVIRONMENT = \
$(SHELL) `test -n '$(STRICT_TESTS_CHECKING)' && echo ' -e'`
neither is this:
TESTS_ENVIRONMENT = \
run_with_perl_or_shell () \
{ \
if grep -q '^#!.*perl' $$1; then
$(PERL) $$1; \
else \
$(SHELL) $$1; \
fi; \
}
LOG_COMPILER = run_with_perl_or_shell
- The package authors can now use customary testsuite drivers within
the framework provided by the 'parallel-tests' testsuite harness.
Consistently with the existing syntax, this can be done by defining
special makefile variables 'LOG_DRIVER' and '<ext>_LOG_DRIVER'.
- A new developer-reserved variable 'AM_TESTS_FD_REDIRECT' can be used
to redirect/define file descriptors used by the test scripts.
- The parallel-tests harness generates now, in addition the '.log' files
holding the output produced by the test scripts, a new set of '.trs'
files, holding "metadata" derived by the execution of the test scripts;
among such metadata are the outcomes of the test cases run by a script.
- Initial and still experimental support for the TAP test protocol is
now provided.
* Changes to Yacc and Lex support:
- C source and header files derived from non-distributed Yacc and/or
Lex sources are now removed by a simple "make clean" (while they were
previously removed only by "make maintainer-clean").
- Slightly backward-incompatible change, relevant only for use of Yacc
with C++: the extensions of the header files produced by the Yacc
rules are now modelled after the extension of the corresponding
sources. For example, yacc files named "foo.y++" and \
"bar.yy" will
produce header files named "foo.h++" and "bar.hh" \
respectively, where
they would have previously produced header files named simply "foo.h"
and "bar.h". This change offers better compatibility with 'bison -o'.
* Miscellaneous changes:
- The AM_PROG_VALAC macro now causes configure to exit with status 77,
rather than 1, if the vala compiler found is too old.
- The build system of Automake itself now avoids the use of make
recursion as much as possible.
- Automake now prefers to quote 'like this' or "like this", rather
than `like this', in diagnostic message and generated Makefiles,
to accommodate the new GNU Coding Standards recommendations.
- Automake has a new option '--print-libdir' that prints the path of the
directory containing the Automake-provided scripts and data files.
- The 'dist' and 'dist-all' targets now can run compressors in parallel.
- The rules to create pdf, dvi and ps output from Texinfo files now
works better with modern 'texi2dvi' script, by explicitly passing
it the '--clean' option to ensure stray auxiliary files are not
left to clutter the build directory.
- Automake can now generate silenced rules for texinfo outputs.
- Some auxiliary files that are automatically distributed by Automake
(e.g., 'install-sh', or the 'depcomp' script for packages compiling
C sources) might now be listed in the DIST_COMMON variable in many
Makefile.in files, rather than in the top-level one.
- Messages of types warning or error from 'automake' and 'aclocal'
are now prefixed with the respective type, and presence of -Werror
is noted.
- Automake's early configure-time sanity check now tries to avoid
sleeping for a second, which slowed down cached configure runs
noticeably. In that case, it will check back at the end of the
configure script to ensure that at least one second has passed, to
avoid time stamp issues with makefile rules rerunning autotools
programs.
- The warnings in the category 'extra-portability' are now enabled by
'-Wall'. In previous versions, one has to use '-Wextra-portability'
to enable them.
Bugs fixed in 1.12:
- Various minor bugfixes for recent or long-standing bugs.
* Bugs introduced by 1.11:
- The AM_COND_IF macro also works if the shell expression for the
conditional is no longer valid for the condition.
- The automake-provided parallel testsuite harness does not fail anymore
with BSD make used in parallel mode when there are test scripts in a
subdirectory, like in:
TESTS = sub/foo.test sub/bar.test
* Long-standing bugs:
- Automake's own build system finally have a real "installcheck" target.
- Vala-related cleanup rules are now more complete, and work better in
a VPATH setup.
- Files listed with the AC_REQUIRE_AUX_FILE macro in configure.ac are
now automatically distributed also if the directory of the auxiliary
files coincides with the top-level directory.
- Automake now detects the presence of the '-d' flag in the various
'*YFLAGS' variables even when their definitions involve indirections
through other variables, such as in:
foo_opts = -d
AM_YFLAGS = $(foo_opts)
- Automake now complains if a '*YFLAGS' variable has any conditional
content, not only a conditional definition.
- Explicit enabling and/or disabling of Automake warning categories
through the '-W...' options now always takes precedence over the
implicit warning level implied by Automake strictness (foreign, gnu
or gnits), regardless of the order in which such strictness and
warning flags appear. For example, a setting like:
AUTOMAKE_OPTIONS = -Wall --foreign
will cause the warnings in category 'portability' to be enabled, even
if those warnings are by default disabled in 'foreign' strictness.
|
| 2012-04-15 17:37:46 by Thomas Klausner | Files touched by this commit (3) | |
Log message:
Update to 1.11.5:
Bugs fixed in 1.11.5:
* Bugs introduced by 1.11.3:
- Vala files with '.vapi' extension are now recognized and handled
correctly again. See automake bug#11222.
- Vala support work again for projects that contain some program
built from '.vala' (and possibly '.c') sources and some other
program built from '.c' sources *only*. See automake bug#11229.
New in 1.11.4:
* WARNING: Future backward-incompatibilities!
- The support for the "obscure" multilib feature has been deprecated,
and will be moved out of the automake core in the next major Automake
release (1.12).
- The support for ".log -> .html" conversion and the check-html and
recheck-html targets will be removed in the next major Automake
release (1.12).
- The obsolescent AM_WITH_REGEX macro has been deprecated (since the
GNU rx library has been decommissioned), and will be removed in the
next major Automake release (1.12).
- The `lzma' compression format for distribution archives has been
deprecated in favor of `xz' and `lzip', and will be removed in the
next major Automake release (1.12).
- The `--acdir' option of aclocal is deprecated, and will probably be
removed in the next major Automake release (1.12).
- The exact order in which the directories in the aclocal macro
search path are looked up is probably going to be changed in the
next Automake release (1.12).
- The Automake support for automatic de-ANSI-fication will be removed
in the next major Automake release (1.12).
- Starting from the next Automake release (1.12), warnings in the
`extra-portability' category will be enabled by `-Wall' (right now,
one has to use `-Wextra-portability' explicitly).
* Miscellaneous changes:
- The 'ar-lib' script now ignores the "s" (symbol index) and \
"S" (no
symbol index) modifiers as well as the "s" action, as the symbol index
is created unconditionally by Microsoft lib. Also, the "q" (quick)
action is now a synonym for "r" (replace). Also, the script has been
ignoring the "v" (verbose) modifier already since Automake 1.11.3.
- When the 'compile' script is used to wrap MSVC, it now accepts an
optional space between the -I, -L and -l options and their respective
arguments, for better POSIX compliance.
- There is an initial, experimental support for automatic dependency
tracking with tcc (the Tiny C Compiler). Its associated depmode is
currently recognized as "icc" (but this and other details are likely
to change in future versions).
- Automatic dependency tracking now works also with the IBM XL C/C++
compilers, thanks to the new new depmode 'xlc'.
Bugs fixed in 1.11.4:
* Bugs introduced by 1.11.2:
- A definition of 'noinst_PYTHON' before 'python_PYTHON' (or similar)
don't cause spurious failures upon "make install" anymore.
- The user can now instruct the 'uninstall-info' rule not to update
the '${infodir}/dir' file by exporting the environment variable
'AM_UPDATE_INFO_DIR' to the value "no". This is done for consistency
with how the 'install-info' rule operates since automake 1.11.2.
* Long-standing bugs:
- It is now possible for a foo_SOURCES variable to hold Vala sources
together with C header files, as well as with sources and headers for
other supported languages (e.g., C++). Previously, only mixing C and
Vala sources was supported.
- If "aclocal --install" is used, and the first directory specified with
'-I' is non-existent, aclocal will now create it before trying to copy
files in it.
- An empty declaration of a "foo_PRIMARY" don't cause anymore the
generated install rules to create an empty $(foodir) directory;
for example, if Makefile.am contains something like:
pkglibexec_SCRIPTS =
if FALSE
pkglibexec_SCRIPTS += bar.sh
endif
the $(pkglibexec) directory will not be created upon "make install".
|
| 2012-03-11 08:27:08 by Steven Drake | Files touched by this commit (3) |
Log message: Insure that am__py_compile gets add to output. Bump PKGREVISION. |
| 2012-03-10 09:00:52 by Steven Drake | Files touched by this commit (2) |
Log message: Add share/aclocal to the PLIST. aclocal dies if this directory doesn't exist. Bump PKGREVISION. |
| 2012-03-03 14:01:36 by Thomas Klausner | Files touched by this commit (1) | |
Log message: Remove unused patch after 1.11.3 update. |
| 2012-03-03 13:58:13 by Thomas Klausner | Files touched by this commit (3) | |
Log message:
Update to 1.11.3:
New in 1.11.3:
* WARNING: Future backward-incompatibilities!
- The support for the "obscure" multilib feature has been deprecated,
and will be moved out of the automake core in the next major Automake
release (1.12).
- The support for ".log -> .html" conversion and the check-html and
recheck-html targets will be removed in the next major Automake
release (1.12).
- The obsolescent AM_WITH_REGEX macro has been deprecated (since the
GNU rx library has been decommissioned), and will be removed in the
next major Automake release (1.12).
- The `lzma' compression format for distribution archives has been
deprecated in favor of `xz' and `lzip', and will be removed in the
next major Automake release (1.12).
- The `--acdir' option of aclocal is deprecated, and will probably be
removed in the next major Automake release (1.12).
- The exact order in which the directories in the aclocal macro
search path are looked up is probably going to be changed in the
next Automake release (1.12).
- The Automake support for automatic de-ANSI-fication will be removed
in the next major Automake release (1.12).
- Starting from the next Automake release (1.12), warnings in the
`extra-portability' category will be enabled by `-Wall' (right now,
one has to use `-Wextra-portability' explicitly).
* Miscellaneous changes:
- Automake's own build system is more silent by default, making use of
the 'silent-rules' option.
- The master copy of the `gnupload' script is now maintained in gnulib,
not in automake.
- The `missing' script doesn't try to wrap calls to `tar' anymore.
- "make dist" doesn't wrap `tar' invocations with the `missing' script
anymore. Similarly, the obsolescent variable `$(AMTAR)' (which you
shouldn't be using BTW ;-) does not invoke the missing script anymore
to wrap tar, but simply invokes the `tar' program itself.
- "make dist" can now create lzip-compressed tarballs.
- In the Automake info documentation, the Top node and the nodes about
the invocation of the automake and aclocal programs have been renamed;
now, calling "info automake" will open the Top node, while calling
"info automake-invocation" and "info aclocal-invocation" \
will access
the nodes about the invocation of respectively automake and aclocal.
- Automake is now distributed as a gzip-compressed and an xz-compressed
tarball. Previously, bzip2 was used instead of xz.
- The last relics of Python 1.5 support have been removed from the
AM_PATH_PYTHON macro.
- For programs and libraries, automake now detects EXTRA_foo_DEPENDENCIES
and adds them to the normal list of dependencies, but without
overwriting the foo_DEPENDENCIES variable, which is normally computed
by automake.
Bugs fixed in 1.11.3:
* Bugs introduced by 1.11.2:
- Automake now correctly recognizes the prefix/primary combination
`pkglibexec_SCRIPTS' as valid.
- The parallel-tests harness doesn't trip anymore on sed implementations
with stricter limits on the length of input lines (problem seen at
least on Solaris 8).
* Long-standing bugs:
- The "deleted header file problem" for *.am files is avoided by stub
rules. This allows `make' to trigger a rerun of `automake' also if
some previously needed `.am' file has been removed.
- The `silent-rules' option now generates working makefiles even
for the uncommon `make' implementations that do not support the
nested-variables extension to POSIX 2008. For such `make'
implementations, whether a build is silent is determined at
configure time, and cannot be overridden at make time with
`make V=0' or `make V=1'.
- Vala support now works better in VPATH setups.
New in 1.11.2:
* Changes to aclocal:
- The `--acdir' option is deprecated. Now you should use the new options
`--automake-acdir' and `--system-acdir' instead.
- The `ACLOCAL_PATH' environment variable is now interpreted as a
colon-separated list of additional directories to search after the
automake internal acdir (by default ${prefix}/share/aclocal-APIVERSION)
and before the system acdir (by default ${prefix}/share/aclocal).
* Miscellaneous changes:
- The Automake support for automatic de-ANSI-fication has been
deprecated. It will probably be removed in the next major Automake
release (1.12).
- The `lzma' compression scheme and associated automake option `dist-lzma'
is obsoleted by `xz' and `dist-xz' due to upstream changes.
- You may adjust the compression options used in dist-xz and dist-bzip2.
The default is now merely -e for xz, but still -9 for bzip; you may
specify a different level via the XZ_OPT and BZIP2 envvars respectively.
E.g., "make dist-xz XZ_OPT=-7" or "make dist-bzip2 BZIP2=-5"
- The `compile' script now converts some options for MSVC for a better
user experience. Similarly, the new `ar-lib' script wraps Microsoft lib.
- The py-compile script now accepts empty arguments passed to the options
`--destdir' and `--basedir', and complains about unrecognized options.
Moreover, a non-option argument or a special `--' argument terminates
the list of options.
- A developer that needs to pass specific flags to configure at "make
distcheck" time can now, and indeed is advised to, do so by defining
the developer-reserved makefile variable AM_DISTCHECK_CONFIGURE_FLAGS,
instead of the old DISTCHECK_CONFIGURE_FLAGS.
The DISTCHECK_CONFIGURE_FLAGS variable should now be reserved for the
user; still, the old Makefile.am files that used to define it will
still continue to work as before.
- New macro AM_PROG_AR that looks for an archiver and wraps it in the new
'ar-lib' auxiliary script if the selected archiver is Microsoft lib.
This new macro is required for LIBRARIES and LTLIBRARIES when automake
is run with -Wextra-portability and -Werror.
- When using DejaGnu-based testsuites, the user can extend the `site.exp'
file generated by automake-provided rules by defining the special make
variable `$(EXTRA_DEJAGNU_SITE_CONFIG)'.
- The `install-info' rule can now be instructed not to create/update
the `${infodir}/dir' file, by exporting the new environment variable
`AM_UPDATE_INFO_DIR' to the value "no".
Bugs fixed in 1.11.2:
* Bugs introduced by 1.11:
- The parallel-tests driver no longer produces erroneous results with
Tru64/OSF 5.1 sh upon unreadable log files.
- The `parallel-tests' test driver does not report spurious successes
when used with concurrent FreeBSD make (e.g., "make check -j3").
- When the parallel-tests driver is in use, automake now explicitly
rejects invalid entries and conditional contents in TEST_EXTENSIONS,
instead of issuing confusing and apparently unrelated error messages
(e.g., "non-POSIX variable name", "bad characters in variable \
name",
or "redefinition of TEST_EXTENSIONS), or even, in some situations,
silently producing broken `Makefile.in' files.
- The `silent-rules' option now truly silences all compile rules, even
when dependency tracking is disabled. Also, when `silent-rules' is
not used, `make' output no longer contains spurious backslash-only
lines, thus once again matching what Automake did before 1.11.
- The AM_COND_IF macro also works if the shell expression for the
conditional is no longer valid for the condition.
* Long-standing bugs:
- The order of Yacc and Lex flags is fixed to be consistent with other
languages: $(AM_YFLAGS) comes before $(YFLAGS), and $(AM_LFLAGS) before
$(LFLAGS), so that the user variables override the developer variables.
- "make distcheck" now correctly complains also when "make \
uninstall"
leaves one and only one file installed in $(prefix).
- A "make uninstall" issued before a "make install", or \
after a mere
"make install-data" or a mere "make install-exec" does \
not spuriously
fail anymore.
- Automake now warns about more primary/directory invalid combinations,
such as "doc_LIBRARIES" or "pkglib_PROGRAMS".
- Rules generated by Automake now try harder to not change any files when
`make -n' is invoked. Fixes include compilation of Emacs Lisp, Vala, or
Yacc source files and the rule to update config.h.
- Several scripts and the parallel-tests testsuite driver now exit with
the right exit status upon receiving a signal.
- A per-Makefile.am setting of -Werror does not erroneously carry over
to the handling of other Makefile.am files.
- The code for automatic dependency tracking works around a Solaris
make bug triggered by sources containing repeated slashes when the
`subdir-objects' option was used.
- The makedepend and hp depmodes now work better with VPATH builds.
- Java sources specified with check_JAVA are no longer compiled for
"make all", but only for "make check".
- An usage like "java_JAVA = foo.java" will now cause Automake to warn
and error out if `javadir' is undefined, instead of silently producing
a broken Makefile.in.
- aclocal and automake now honour the configure-time definitions of
AUTOCONF and AUTOM4TE when they spawn autoconf or autom4te processes.
- The `install-info' recipe no longer tries to guess whether the
`install-info' program is from Debian or from GNU, and adaptively
change its behaviour; this has proven to be frail and easy to
regress.
|
New packages: