Out today is GNU Automake 1.20 with the new --enable-jobserver option and opting for GPLv3+ licensing...

Out today is GNU Automake 1.20 with the new --enable-jobserver option and opting for GPLv3+ licensing.

Out today is GNU Automake 1.20 with the new --enable-jobserver option and opting for GPLv3+ licensing.

Blog com notícias sobre, Linux, Android, Segurança , etc

Out today is GNU Automake 1.20 with the new --enable-jobserver option and opting for GPLv3+ licensing...

software leftovers

software leftovers

Out today is GNU Automake 1.20 with the new --enable-jobserver option and opting for GPLv3+ licensing...

Arriving just two months after its predecessor, the release adds jobserver support, safer build behavior, and nine bug fixes. The post GNU Automake 1.20 Moves to GPLv3 and Tunes Up the Build System…

Out today is GNU Automake 1.20 with the new --enable-jobserver option and opting for GPLv3+ licensing...

We are pleased to announce GNU Automake 1.20, a stable minor release. Among new features is `--enable-jobserver' for compiler and linker access to GNU make's jobserver, the delete-on-error option, and a print-distfiles target. distcheck no longer requires TeX by default. This release also fixes some long-standing bugs and limitations concerning dependency tracking, lex/yacc output in VPATH builds, Vala builds, distribution compression, and uninstall checks. Furthermore, GNU automake has upgraded from the GNU GPLv2 (or later) license to the GNU GPL v3 (or later) license. I have substantial plans for the GNU Build System (`autotools') as a whole. I intend to continue resolving old issues and limitations, and adding new features in GNU Automake, slowly dragging it into the future. My ultimate goal is to establish it, once again, as the build system of choice for new software projects while continuing to simplify maintenance and portability for existing users. Hopefully, upcoming releases will get us closer and closer to this goal. -*-*-*- There have been 104 commits by 3 contributors in the 58 days since 1.19. Thanks to everyone who contributed to this release! Kamila Szewczyk (99) Karl Berry (4) Paul Eggert (1) Kamila Szewczyk (szewczyk@math.uni-sb.de) ================================================================== See below for the detailed list of changes since the previous version, as summarized by the NEWS file. Here is the GNU Automake home page: https://www.gnu.o ... oftware/automake/ Here are the compressed sources: https://ftp.gnu.o ... omake-1.20.tar.gz (2549281 bytes) https://ftp.gnu.o ... omake-1.20.tar.xz (1694140 bytes) Here are the GPG detached signatures: https://ftp.gnu.o ... e-1.20.tar.gz.sig https://ftp.gnu.o ... e-1.20.tar.xz.sig Use a mirror for higher download bandwidth: https://www.gnu.o ... rg/order/ftp.html Here are the SHA256 and SHA3-256 checksums: File: automake-1.20.tar.gz SHA256 sum: df7696d9f7cc7e98b9ff46bbbf5fa72c0bbdf629b4ca05ecdc9150ee4561c072 SHA3-256 sum: 7dc50edcb7eb4f11478fc3de8214a19cfe2d7b27929e8be1e26524a47204ece5 File: automake-1.20.tar.xz SHA256 sum: 6f7ae4c90b4e89b5f7f50a9c3bf205a10f18b60c2659d3d6f044351bd8a28d5d SHA3-256 sum: 6175fa7daf497eb3206655f27b51e0d5523b45bc268ce27fcaf81628337c0d76 Verify SHA256 with sha256sum or 'shasum -a 256'. Verify SHA3-256 with 'openssl dgst -sha3-256 FILE'. 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.20.tar.gz.sig automake-1.20.tar.gz The signature should match the fingerprint of the following key: pub rsa4096 2022-07-31 [C] [expires: 2036-05-11] 6C22 2EA6 B2BD 216A A406 516A C868 F0B6 DE38 409D uid [ultimate] Kamila Szewczyk <k@iczelia.net> uid [ultimate] Kamila Szewczyk <szewczyk@cs.uni-saarland.de> uid [ultimate] Kamila Szewczyk <iczelia@gnu.org> uid [ultimate] Kamila Szewczyk <szewczyk@math.uni-sb.de> sub rsa4096 2022-07-31 [E] sub ed25519 2026-06-29 [S] If that command fails because you don't have the required public key, or that public key has expired, try the following command 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.o ... u/gnu-keyring.gpg gpg --keyring ./gnu-keyring.gpg --verify automake-1.20.tar.gz.sig automake-1.20.tar.gz Please report bugs and problems to <bug-automake@gnu.org> (instead of replying to this mail), and send general comments and feedback to <automake@gnu.org>, and patches to <automake-patches@gnu.org>. Thanks to everyone who has reported problems, contributed patches, and helped test Automake! Changes from NEWS: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ New in 1.20 (2026-11-07): * 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.o ... oftware/autoconf/ https://www.gnu.o ... ommendations.html https://www.gnu.o ... ms-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_) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This release is based on the Automake Git repository, available as: git clone https://https.git ... /git/automake.git Commit 5613ae2dbb151f73070bb576f21136e5ef5c75c1 is tagged as v1.20. For a summary of changes and contributors, see: https://gitweb.gi ... =shortlog;h=v1.20 Or run this command from a Git checkout of Automake: git shortlog v1.19..v1.20 -- With Valediction, Kamila Szewczyk (https:// ... elia.net)

Arriving just two months after its predecessor, the release adds jobserver support, safer build behavior, and nine bug fixes.

Arriving just two months after its predecessor, the release adds jobserver support, safer build behavior, and nine bug fixes.

For decades, the GNU Build System has stood as the bedrock of free software development, a sprawling ecosystem that powers much of the internet.

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 ... ke-1.19.94.tar.gz https://alpha.gnu ... ke-1.19.94.tar.xz Please report bugs and problems to <bug-automake@gnu.org> (instead of replying to this mail), and send general comments and feedback to <automake@gnu.org>, and patches to <automake-patches@gnu.org>. 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 ... TOOL-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.o ... oftware/autoconf/ https://www.gnu.o ... ommendations.html https://www.gnu.o ... ms-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. ... /s/automake/ Here are the compressed sources: https://alpha.gnu ... ke-1.19.94.tar.gz (2.5MB) https://alpha.gnu ... ke-1.19.94.tar.xz (1.7MB) Here are the GPG detached signatures: https://alpha.gnu ... .19.94.tar.gz.sig https://alpha.gnu ... .19.94.tar.xz.sig Use a mirror for higher download bandwidth: https://www.gnu.o ... rg/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.xz SHA256 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 <k@iczelia.net> uid Kamila Szewczyk <szewczyk@cs.uni-saarland.de> uid Kamila Szewczyk <iczelia@gnu.org> uid Kamila Szewczyk <szewczyk@math.uni-sb.de> 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.o ... u/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 ... /git/automake.git with commit 69b6c65e706ad089f076ebaf8b84fca4170c6cce tagged as v1.19.94. For a summary of changes and contributors, see: https://gitweb.gi ... ortlog;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:// ... elia.net)

This is to announce automake-1.19.92, a alpha release. It is the first (and hopefully final) 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 80 commits by 3 people in the 49 days 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 (75) Karl Berry (4) Paul Eggert (1) Kamila Szewczyk (szewczyk@math.uni-sb.de) [on behalf of the automake maintainers] ================================================================== Download here: https://alpha.gnu ... ke-1.19.92.tar.gz https://alpha.gnu ... ke-1.19.92.tar.xz Please report bugs and problems to <bug-automake@gnu.org> (instead of replying to this mail), and send general comments and feedback to <automake@gnu.org>, and patches to <automake-patches@gnu.org>. 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 ... TOOL-is-undefined For planned incompatibilities in a possible future Automake 2.0 release, please see NEWS-future and start following the advice there now. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ New in 1.19.2 (2026-10-28): * 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. * 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. ... /s/automake/ Here are the compressed sources: https://alpha.gnu ... ke-1.19.92.tar.gz (2.5MB) https://alpha.gnu ... ke-1.19.92.tar.xz (1.7MB) Here are the GPG detached signatures: https://alpha.gnu ... .19.92.tar.gz.sig https://alpha.gnu ... .19.92.tar.xz.sig Use a mirror for higher download bandwidth: https://www.gnu.o ... rg/order/ftp.html Here are the SHA256 and SHA3-256 checksums: File: automake-1.19.92.tar.gz SHA256 sum: 8f766f5f78d98f81ce30446cab79caf2d9b514f32821e2c466c846a22f971b68 SHA3-256 sum: 4445cde757b16c43ec389461d2bab9f99562586ab07a4a0cf506e3450e1eb576 File: automake-1.19.92.tar.xz SHA256 sum: 3e338607daf027546f2040439578176feab6ee8efab83dc9a9a9680884ff1fb5 SHA3-256 sum: 84348e4b626558f1aacecde044400131fbdcbbde74fe447a338427b580d4174d 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.92.tar.gz.sig automake-1.19.92.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 <k@iczelia.net> uid Kamila Szewczyk <szewczyk@cs.uni-saarland.de> uid Kamila Szewczyk <iczelia@gnu.org> uid Kamila Szewczyk <szewczyk@math.uni-sb.de> 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.o ... u/gnu-keyring.gpg gpg --keyring gnu-keyring.gpg --verify automake-1.19.92.tar.gz.sig automake-1.19.92.tar.gz This release is based on the automake git repository, available as git clone https://https.git ... /git/automake.git with commit f6104d007b721055edec9c689fdc9c397623600a tagged as v1.19.92. For a summary of changes and contributors, see: https://gitweb.gi ... ortlog;h=v1.19.92 or run this command from a git-cloned automake directory: git shortlog v1.19..v1.19.92 -- With Valediction, Kamila Szewczyk (https:// ... elia.net)

Volkswagen has launched its new ID.Tiguan electric SUV as part of its strategy to compete with Chinese automakers in the European market. The vehicle is positioned as a key tool in the German automake… · Photo : gudi&cris · CC BY-ND · Flickr