staging/stintel/tools/automake, branch master

tools: build autoconf, automake, libtool, dosfstools and make-ext4fs in parallel

2026-09-22T18:29:59Z

libtool 22.5 s -> 20.0 s dosfstools 6.0 s -> 4.8 s make-ext4fs 2.1 s -> 1.2 s automake 3.9 s -> 3.4 s autoconf 3.1 s -> 2.6 s Each one builds five times out of five with the job server, and each build installs files that are identical to those of a serial build. Signed-off-by: John Crispin

tools: automake: do not error on missing conditional

2026-07-30T17:34:40Z

Now that cond.m4 is not being overwritten and is actively used, make it less aggressive on encountering an undefined conditional not set by a macro which is itself conditionally called, where the condition is set to intentionally not trigger the macro. This prevents the need to further patch a configure.ac file to edit the improper usage of or remove a disabled macro which triggers the error "conditional ___ is not defined..." in the cases where autoreconf is still necessary for another reason, or, if this is the only build issue, autoreconf can now be used to avoid this. Instead of erroring, align the behavior of AM_CONDITIONAL closer to the gnulib variant gl_CONDITIONAL which ignores and disables the conditional in this case. Signed-off-by: Michael Pratt Link: https://github.com/openwrt/openwrt/pull/24362 Signed-off-by: Robert Marko

tools: automake: fix MAINTAINERCLEANFILES warnings

2025-07-29T19:31:11Z

It seems that, for whatever reason in this case, the function "vardef ($var, $cond)" does not work while "$var->def ($cond)" does work for conditionals. Also, do not define it conditionally when defined unconditionally. Even though the reordering patch would make that functionally sound, it still throws a warning which can cause a build to fail when warnings are treated as errors. Instead, just add BUILT_SOURCES to every existing case rather than only when BUILT_SOURCES is defined. Fixes: 6d2bfe50d3 ("tools/automake: control all cleaning with clean variables") Signed-off-by: Michael Pratt Link: https://github.com/openwrt/openwrt/pull/19593 Signed-off-by: Robert Marko

tools: automake: update to 1.18.1

2025-07-26T15:09:19Z

automake update to 1.18 broke buildbots as we dont have makeinfo host tool present, after investigation this was an automake regression that was fixed in 1.18.1[1]. So, since 1.18.1 contains small number of fixes, update to it instead of just backporting the single commit. [1] https://cgit.git.savannah.gnu.org/cgit/automake.git/commit/?id=9b92240af4a8f7a3050c13adec367cf48e9ce063 Fixes: d7d02059407b ("tools/automake: update to 1.18") Signed-off-by: Robert Marko

tools/automake: update to 1.18

2025-07-26T12:38:09Z

Update to the latest stable release with the new API versions for binaries. The temporary patching of shebangs is no longer necessary since the whitespace check has been changed to a warning. Part of a patch was upstreamed and therefore removed. Manually adjusted patch: - 000-relocatable.patch - 101-do-not-require-files.patch All other patches are automatically refreshed. Link: https://lists.gnu.org/archive/html/autotools-announce/2025-05/msg00001.html Signed-off-by: Michael Pratt Link: https://github.com/openwrt/openwrt/pull/16522 Signed-off-by: Robert Marko

tools/automake: do not delete libtool in clean targets

2025-07-26T12:38:08Z

For the building of some packages, it is helpful to completely clean the packaged release copy of the source, however this usually deletes libtool if used, otherwise causing the need to run the bootstrap script twice. Not deleting libtool allows compilation to continue directly after cleaning pre-generated files in the package distribution. Signed-off-by: Michael Pratt Link: https://github.com/openwrt/openwrt/pull/16522 Signed-off-by: Robert Marko

tools/automake: control all cleaning with clean variables

2025-07-26T12:38:08Z

Automake previously makes rules for the target maintainer-clean to remove both the contents of MAINTAINERCLEANFILES and BUILT_SOURCES. In order to have finer control over what is removed, let there only be a rule for deleting MAINTAINERCLEANFILES, and set MAINTAINERCLEANFILES to a default value of BUILT_SOURCES if only conditional or missing, and append BUILT_SOURCES if user-defined. In order to maintain conditional values for MAINTAINERCLEANFILES while keeping a default value, change the behavior of automake to output unconditional definitions before conditions. Signed-off-by: Michael Pratt Link: https://github.com/openwrt/openwrt/pull/16522 Signed-off-by: Robert Marko

tools/automake: do not delete Makefile in clean targets

2025-07-26T12:38:08Z

For the building of some packages, it is sometimes helpful to completely clean the packaged release copy of the source, however this usually both requires and deletes the Makefile, causing the need to run the configure stage twice. Not deleting the Makefile allows compilation to continue directly after cleaning pre-generated files in the package distribution. Signed-off-by: Michael Pratt Link: https://github.com/openwrt/openwrt/pull/16522 Signed-off-by: Robert Marko

tools/automake: update to 1.17

2025-07-26T12:38:07Z

Update to the latest stable release. This is the automake API that newer packages such as libtool 2.5.4 is bootstrapped with, and is required for bootstrapping it again. Manually Adjusted: - 000-relocatable.patch All other patches are automatically refreshed. Link: https://lists.gnu.org/archive/html/autotools-announce/2024-07/msg00000.html Signed-off-by: Michael Pratt Link: https://github.com/openwrt/openwrt/pull/16522 Signed-off-by: Robert Marko

tools/automake: hardcode portable location for Perl

2025-07-26T12:38:07Z

The latest automake version 1.17 includes a restriction against whitespace for the configure variable $PERL, which is set to "/usr/bin/env perl" for portability reasons with products like the SDK. Instead of waiting until the next version of automake is released for this error to be converted to a warning, set the shebang of automake and aclocal manually with a patch. In past git history, these lines have been patched before, but only to remove the "-w" flag in favor of setting global warnings in the script itself so that env does not strip the option. The other purposes of Perl during building can use the static staging directory path without any limitations. Also, the configure variable "am_cv_prog_PERL_ithreads" for the detection of Perl threads support has been removed since 2013 in favor of dynamic runtime detection. Remove our manual setting of this variable value as it has no effect. Ref: 1ef07eee4 ("automake: forcibly disable perl ithreads support") Ref: 182626687 ("ithreads: use runtime (not configure time) detection of perl threads") # automake.git Ref: f6c581cc3 ("automake: portability fixes") Ref: 87f3365d9 ("Revert "tools/automake: bump to 1.17"") Signed-off-by: Michael Pratt Link: https://github.com/openwrt/openwrt/pull/16522 Signed-off-by: Robert Marko