[AUH] autoconf-archive: upgrading to 2026.11.11 SUCCEEDED

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe(s) *autoconf-archive* to *2026.11.11* has Succeeded.

Next steps:
    - apply the patch: git am 0001-autoconf-archive-upgrade-2024.10.16-2026.11.11.patch
    - check the changes to upstream patches and summarize them in the commit message,
    - compile an image that contains the package
    - perform some basic sanity tests
    - amend the patch and sign it off: git commit -s --reset-author --amend
    - send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update failures.
Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper

-- >8 --
From c304b0376e79c6feff950b277148d951a277883a Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@yoctoproject.org>
Date: Thu, 12 Nov 2026 05:15:07 +0000
Subject: [PATCH] autoconf-archive: upgrade 2024.10.16 -> 2026.11.11

# Copyright (c) 2026 Autoconf Archive Maintainers <autoconf-archive-
maintainers@gnu.org>

Merge pull request #318 from autoconf-archive/revert-288-luajit
Revert "Add LuaJIT support to AX_PROG_LUA macro"

Merge pull request #327 from rrthomas/code_coverage-doc
AX_CODE_COVERAGE: fix documentation

AX_PTHREAD: Fix pthread detection on Solaris 11.4
AX_PTHREAD fails to detect pthread support on Solaris 11.4.  This was
originally noticed with the copy of ax_pthread.m4 in the GCC source tree:

build: Fix ax_pthread.m4 on Solaris 11.4
https://gcc.gnu.org/pipermail/gcc-patches/2026-May/716850.html

It turns out the problem is that AX_PTHREAD expects _REENTRANT to be
defined on Solaris.  However, as described in

https://gcc.gnu.org/gcc-16/porting_to.html#solaris
and
Goodbye (And Good Riddance) to -mt -and -D_REENTRANT
https://www.linker-aliens.org/blogs/ali/entry/mtreentrant/

referenced from there, Solaris 11.4 removed references to _REENTRANT from
the Solaris system headers.  Given that, GCC 16 no longers defines it with
-pthread.

This started when libpthread was folded into libc in Solaris 11.

However, AX_PTHREAD expects _REENTRANT to be defined in multithreaded
programs on Solaris, which is no longer true.  To detect the situation,
this patch checks for XPG7 support which was introduced together with those
changes in Solaris 11.4.

However, the _REENTRANT check is dubious at best.  If a feature isn't
detected, this may be because the corresponding feature test macros isn't
defined.  However, the reverse is not true: a feature way well be available
be default without any feature test macro.

The fix was tested in the GCC tree as described above, and manually on
Solaris 11.3 where _REENTRANT is still referenced and needed.

Closes #341.

ax_lib_hdf5.m4:  fix "The macro 'AC_HAVE_LIBRARY' is obsolete."
- from
  https://www.gnu.org/software/autoconf/manual/autoconf-2.69/html_node/Obsolete-
  Macros.html replaced with AC_CHECK_LIB

Closes #342.

Merge pull request #323 from jas4711/avoid-timestamps
Don't embed build timestamp for AX_AM_MACROS*.

Merge pull request #325 from uckelman-sf/fix_ax_pkg_check_modules_whitespace
AX_PKG_CHECK_MODULES: Remove extra whitespace from PUBLIC-MODULES and PRIVATE-
MODULES arguments

Merge pull request #326 from Tropicao/patch-1
ax_python.m4: add new python version

Merge pull request #333 from DanielEScherzer/patch-1
ax_prog_bison_version.m4: fix incorrect description

Merge pull request #335 from bdrung/boost_python
ax_boost_python.m4: try versioned boost_python first

Merge pull request #336 from BrianAker/ax_check_compile_flag
AX_CHECK_COMPILE_FLAG incorrectly accepts warning flags with GNU compilers

AX_GCC_VAR_ATTRIBUTE: add a case for nonstring
Without one the attribute falls to the generic fallback, which declares
an int:

    int foo __attribute__((nonstring));

nonstring only applies to arrays and pointers of character type, so the
compiler ignores it there and warns:

    warning: 'nonstring' attribute ignored on objects of type 'int'
    [-Wattributes]

The macro reads any warning as the attribute being unsupported, so the
check answers no on every compiler, including the ones that support it.

Test it on a char array instead, which is what the attribute is for.
Checked against gcc 15, gcc 16 and clang 22.

ax_cxx_compile_stdcxx.m4: fix -Wunused issue with C++-17 feature test
Some projects may pass `-Wunused -Werror` in as CXX/CXXFLAGS, resulting
in a build failure when running the C++-17 feature tests that confirm that
`constexpr` lambdas are supported.

Use `static_assert` to test the value set in the test, muting the -Wunused
issue found by the compiler.

AX_CHECK_COMPILE_FLAG incorrectly accept unsupported warning flags with GNU
compilers
AX_CHECK_COMPILE_FLAG could incorrectly accept unsupported warning flags with
GNU compilers because it appended -Werror after the candidate flag being tested.
With GCC/G++, diagnostics for wrong-language or otherwise unsupported warning
options can be order-sensitive, so a warning emitted for the tested flag may not
be promoted to an error when -Werror appears later on the command line. As a
result, the probe could succeed even though the flag should have been rejected.

This change initializes add_gnu_werror explicitly and places -Werror before the
candidate flag in the probe command, so GNU compilers fail these checks
reliably. It fixes false positives during configure-time flag detection,
especially for warning options that are valid in C but not C++.

To highlight how the behavior correct here are two one liners:
printf 'int main(){return 0;}\n' | g++-15 -Wmissing-prototypes -Werror -x c++ -
printf 'int main(){return 0;}\n' | g++-15 -Werror -Wmissing-prototypes -x c++ -

ax_boost_python.m4: try versioned boost_python first
Multiple boot_python libraries might be installed on the system. As of
March 2026 Ubuntu resolute has libraries for Python 3.13 and 3.14:

```
$ ls -1 /usr/lib/x86_64-linux-gnu/libboost_python*.so*
/usr/lib/x

[Changelog truncated as it exceeds 5000 characters;
the full changelog can be found in an attachment to the AUH email]
---
 ...daa3da0eb1a256fda631867e19345d5f6e3a.patch | 33 ----------------
 ...226a2fe3980388abffd6de25ed6b9591cce3.patch | 39 -------------------
 ...8d9e3ead52f998535b86c763065c5b45cc59.patch | 38 ------------------
 ...0.16.bb => autoconf-archive_2026.11.11.bb} |  5 +--
 4 files changed, 1 insertion(+), 114 deletions(-)
 delete mode 100644 meta/recipes-devtools/autoconf-archive/autoconf-archive/3a23daa3da0eb1a256fda631867e19345d5f6e3a.patch
 delete mode 100644 meta/recipes-devtools/autoconf-archive/autoconf-archive/427e226a2fe3980388abffd6de25ed6b9591cce3.patch
 delete mode 100644 meta/recipes-devtools/autoconf-archive/autoconf-archive/e25f8d9e3ead52f998535b86c763065c5b45cc59.patch
 rename meta/recipes-devtools/autoconf-archive/{autoconf-archive_2024.10.16.bb => autoconf-archive_2026.11.11.bb} (64%)