This is to announce automake-1.19.94, a alpha release.
It is the second pre-release for the upcoming Automake 1.20. Please consider doing us a favour and testing it on different platforms.
This release brings important bug-fixes that resolve some long-standing limitations and adds minor new features to automake. There have been 95 commits by 3 people in the 8 weeks since 1.19. See the NEWS below for a brief summary. Thanks to everyone who has contributed! The following people contributed changes to this release: Kamila Szewczyk (90) Karl Berry (4) Paul Eggert (1) Kamila [on behalf of the automake maintainers] ================================================================== See below for the detailed list of changes since the previous version, as summarized by the NEWS file. Download here: https://alpha.gnu.org/gnu/automake/automake-1.19.94.tar.gz https://alpha.gnu.org/gnu/automake/automake-1.19.94.tar.xz Please report bugs and problems to <[email protected]> (instead of replying to this mail), and send general comments and feedback to <[email protected]>, and patches to <[email protected]>. Thanks to everyone who has reported problems, contributed patches, and helped test Automake! -*-*-*- If you install this test release in its own prefix (recommended) and you use libtool, you'll need to arrange for the libtool m4 files to be found by aclocal. For info on this, see:https://gnu.org/s/automake/manual/automake.html#Libtool-library-used-but-LIBTOOL-is-undefined
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
New in 1.20 (????-??-??):
* Licensing
- Automake is now licensed under the GNU General Public License version 3
or later (GPLv3+), matching Autoconf and following the Free Software
Foundation's recommendation to use GPLv3 or later:
https://www.gnu.org/software/autoconf/
https://www.gnu.org/licenses/license-recommendations.html
https://www.gnu.org/licenses/rms-why-gplv3.html
Existing exceptions for distributed support files remain in place.
This does not change the licensing of generated Makefile.in files
or require packages using Automake to adopt the GPL.
* New features added
- New configure option --enable-jobserver lets compilers and linkers
inherit GNU make's pipe jobserver, for example for GCC's
-flto=jobserver. Dry-run, question, and touch modes still do not
run these commands. (bug#45756)
- New option delete-on-error. It emits the .DELETE_ON_ERROR special
target in the generated Makefile.in, instructing GNU make to delete
the target when its recipe fails after having modified it. A failed
rule like `foo.h: gen.sh; ./gen.sh > $@' then no longer leaves a
truncated result that later runs of make treat as up to date. Other
make programs do not support this, so the option will have no effect.
- New target print-distfiles lists the files that "make dist" would
distribute.
* Source tree organization
- Historical ChangeLogs, development plans, and NEWS-future are now
under attic/. The experimental contrib/tap-driver.pl is retained
in attic/testing/; the maintained TAP driver is lib/tap-driver.sh.
The manual's link checker moved from contrib/ to maintainer/.
* Changes to Automake-generated Makefiles
- distcheck no longer runs "make dvi" by default, so TeX is not needed
to check a distribution containing Texinfo manuals. Set
AM_DISTCHECK_DVI_TARGET in Makefile.am to, e.g., dvi, pdf or html,
to check that the documentation can be built. (bug#79053)
* Bugs fixed
- Repeated target declarations in overlapping Automake conditionals no
longer produce spurious redefinition warnings when adding
prerequisites.
(bug#13940)
- Dependencies on another target's objects in LIBADD or LDADD are now
tracked regardless of the order in which targets are processed.
(bug#60508)
- distcheck now detects symbolic links left in the installation tree
after uninstall, including dangling links.
- lex and yacc output files distributed from a VPATH build no longer
carry
"#line" directives pointing to their sources through the build-time
srcdir, e.g. "../src/parse.y"; the distributed copies now refer to
the sources next to them. (bug#39666)
- dist-zstd now honors numeric ZSTD_CLEVEL values, such as 3, instead
of treating them as input filenames. This fixes failed or incorrect
distribution archives when ZSTD_CLEVEL is set.
- lex and yacc rules now create output directories before generating
sources, fixing out-of-tree builds with subdir-objects and
--disable-dependency-tracking. (bug#27188, Debian bug#807050)
- configure now refuses a source directory path containing '<', '>',
'(' or ')'. These could be interpreted as shell redirections or
syntax in compiler commands, potentially overwriting files in the
build directory.
- configure now refuses a source directory path ($srcdir) containing
';' or '|', reporting "unsafe srcdir value", as it already did for
characters such as '$' and '&'. Such a path used to fail later
with misleading errors, from config.status's dependency-tracking
setup or from make ("No rule to make target"). These characters
remain accepted when $srcdir is '.'.
- Non-recursive Vala builds now pass distcheck when generated Vala
sources trigger recompilation in the build directory. Generated C
files are moved into their subdirectories together, and build-tree
stamp files are removed by distclean. (bug#76527)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Here is the GNU automake home page:
https://gnu.org/s/automake/
Here are the compressed sources:
https://alpha.gnu.org/gnu/automake/automake-1.19.94.tar.gz (2.5MB)
https://alpha.gnu.org/gnu/automake/automake-1.19.94.tar.xz (1.7MB)
Here are the GPG detached signatures:
https://alpha.gnu.org/gnu/automake/automake-1.19.94.tar.gz.sig
https://alpha.gnu.org/gnu/automake/automake-1.19.94.tar.xz.sig
Use a mirror for higher download bandwidth:
https://www.gnu.org/order/ftp.html
Here are the SHA256 and SHA3-256 checksums:
File: automake-1.19.94.tar.gz
SHA256 sum:
b550d1eab9a5881949aff503ef50056c5c2f04f527c5f00ca2fb7d52acfe9f92
SHA3-256 sum:
d89c81e5b9e75fcef15a91d138b6f95209e6ff10eb9ef6b5b2142220bc6b7d19
File: automake-1.19.94.tar.xzSHA256 sum: db6b4a816c086eb51b537c87ad1990b1a640de11df02a87c0df656d72dae255c SHA3-256 sum: 863782e6b1d32052e2556c18a154022d38a984a6f2c8200ebeb7250ff38eda4b
Verify the SHA256 checksum with either sha256sum, sha256, or
'shasum -a 256'.
Verify the SHA3-256 checksum with 'cksum -a sha3 -l 256'
from coreutils-9.8.
Use a .sig file to verify that the corresponding file (without the
.sig suffix) is intact. First, be sure to download both the .sig file
and the corresponding tarball. Then, run a command like this:
gpg --verify automake-1.19.94.tar.gz.sig automake-1.19.94.tar.gz
The signature should match the fingerprint of the following key:
pub rsa4096 2022-07-31 [C]
6C22 2EA6 B2BD 216A A406 516A C868 F0B6 DE38 409D
uid Kamila Szewczyk <[email protected]>
uid Kamila Szewczyk <[email protected]>
uid Kamila Szewczyk <[email protected]>
uid Kamila Szewczyk <[email protected]>
If that command fails because you don't have the required public key,
or that public key has expired, try the following commands to retrieve
or refresh it, and then rerun the 'gpg --verify' command.
gpg --recv-keys 6C222EA6B2BD216AA406516AC868F0B6DE38409D
As a last resort to find the key, you can try the official GNU
keyring:
wget -q https://ftp.gnu.org/gnu/gnu-keyring.gpg
gpg --keyring gnu-keyring.gpg --verify automake-1.19.94.tar.gz.sig
automake-1.19.94.tar.gz
This release is based on the automake git repository, available as git clone https://https.git.savannah.gnu.org/git/automake.git with commit 69b6c65e706ad089f076ebaf8b84fca4170c6cce tagged as v1.19.94. For a summary of changes and contributors, see:https://gitweb.git.savannah.gnu.org/gitweb/?p=automake.git;a=shortlog;h=v1.19.94
or run this command from a git-cloned automake directory: git shortlog v1.19..v1.19.94 -- With Valediction, Kamila Szewczyk (https://iczelia.net)
OpenPGP_0xC868F0B6DE38409D.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
