From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] autoconf-archive: Update to version 2024.10.16
Date: Mon, 18 Nov 2024 20:04:32 +0000 [thread overview]
Message-ID: <284A4384-06EE-481F-9C59-2BFD4A4DF2FE@ipfire.org> (raw)
In-Reply-To: <20241112195821.2591127-2-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 11190 bytes --]
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 12 Nov 2024, at 19:58, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> - Update from version 2023.02.20 to 2024.10.16
> - Update of rootfile
> - Changelog
> 2024.10.16
> fix serial numbers
> Typo: ziping → zipinf
> (cherry picked from commit 4396d6e1f6213452d77fca3e02e7f7439204bcb0)
> ax_lua.m4: add LuaJIT support
> AX_LIB_READLINE: add check for minimum version
> m4_define with braces around concat source, m4_if without extra arg
> Fix typos found by codespell
> ax_code_coverage: remove /tmp/* from remove patterns failing with lcov 2.0
> The lcov >= 2.0 refactored error handling and by default it fails
> when an unused remove pattern is provided:
> LCOV --remove /tmp/* */tests/*.c
> lcov: ERROR: 'exclude' pattern '/tmp/*' is unused.
> (use "lcov --ignore-errors unused ..." to bypass this error)
> Based on the macro history is is not clear why the /tmp/* would
> be needed by default. Usual autotools projects don't use /tmp/.
> If needed users can still add this pattern to
> CODE_COVERAGE_IGNORE_PATTERN.
> AX_CXX_COMPILE_STDCXX: Add C++23 support
> AX_CXX_COMPILE_STDCXX: Add (C) statements for myself
> AX_CXX_COMPILE_STDCXX: Check _MSVC_LANG
> This fixes a bug which meant AX_CXX_COMPILE_STDCXX([20]) would only
> actually test for C++17 support.
> fixup! ax_check_compile_flag: add -Werror when checking for compiler flags
> ax_check_compile_flag: add -Werror when checking for compiler flags
> Seemingly that at some point clang started accepting _any_ flags,
> whereas previously it would error out.
> These days, you can give it -Whamsandwich and it will succeed, while
> at the same time throwing an annoying warning.
> Add -Werror so that everything gets flagged and set accordingly.
> AX_BOOST_BASE: Don't set BOOST_*FLAGS if Boost is not found
> Previously BOOST_CPPFLAGS was set to a nonsensical -I/include/boost-0
> value if Boost headers were not found at all and BOOST_LDFLAGS was
> similarly set to a wrong (although less obviously so) value in this
> case because they kept the last values tested by the macro.
> Just don't set these variables at all if detecting Boost failed.
> fix serial numbers
> Use AS_VAR_IF in ax_gcc_builtin.m4
> The AS_VAR_IF check can be a simpler alternative to testing for variable
> value inside AS_IF.
> ax_switch_flags.m4: validate macro arguments at autoconf compile time
> This is a nicer experience for detecting outright misuse of macros than
> successfully creating a configure script and then having it fail.
> ax_check_glx.m4: validate macro arguments at autoconf compile time
> This is a nicer experience for detecting outright misuse of macros than
> successfully creating a configure script and then having it fail.
> ax_check_gl.m4: validate macro arguments at autoconf compile time
> This is a nicer experience for detecting outright misuse of macros than
> successfully creating a configure script and then having it fail.
> ax_is_release.m4: validate macro arguments at autoconf compile time
> This is a nicer experience for detecting outright misuse of macros than
> successfully creating a configure script and then having it fail.
> remove duplicated setting of CPPFLAGS/LDFLAGS
> ax_python_devel: fix typo preventing correct variable evaluation
> The test should check the variable, not the fixed string.
> Most probably a simple typo, so fix it.
> AX_CHECK_{PREPROC,COMPILE}_FLAG: improve logging message
> 2023.09.26
> ax_lua.m4: add Lua 5.4 support
> ax_lua.m4: Fix case of no Lua version match since 'xnil' != ''
> 2023.09.04
> AX_FUNC_WHICH_GETHOSTBYADDR_R: use canonical formatting
> AX_FUNC_WHICH_GETHOSTENT_R: use canonical formatting
> Re-generate macros using the canonical formatting.
> Merge pull request #280 from theAeon/master
> ax_blas: detect flexiblas
> 2023.09.03
> Merge pull request #282 from bogdro/gethostent_r
> Create ax_func_which_gethostent_r.m4
> Merge pull request #281 from bogdro/gethostbyaddr_r
> Create ax_func_which_gethostbyaddr_r.m4
> Merge pull request #283 from cminyard/master
> ax_python_devel: Add an option to make it optional
> Merge pull request #284 from SoapGentoo/Wstrict-prototypes
> Make macros `-Wstrict-prototypes` compatible
> 2023.08.18
> ax_prototype: Disable "unused variable" warning to prevent accidental failures
> 2023.08.13
> Make macros `-Wstrict-prototypes` compatible
> * With Clang having switched to modern C conventions already and GCC
> following suit soon, we want to have macros that work in the presence
> of `-Wstrict-prototypes` in all C language modes, not just C23.
> 2023.07.25
> ax_python_devel: Add an option to make it optional
> ax_python_devel will fail the autoconf run if it doesn't detect that a
> python development environment is available. That's not always what
> the user wants, they may want to go on without the functionality.
> This change adds a way to pass in an option to specify if you want it to
> fail or go on if the functionality is not found. The default is to
> fail, as before.
> 2023.06.28
> Create ax_func_which_gethostent_r.m4
> Create ax_func_which_gethostbyaddr_r.m4
> 2023.06.07
> ax_blas: detect flexiblas
> 2023.06.06
> Merge remote-tracking branch 'github/master'.
> Merge pull request #278 from rurban/fortify2
> ax_add_fortify_source.m4: fix 2nd probe
> ax_c_float_words_bigendian: use canon formatting
> 2023.05.19
> AX_C_FLOAT_WORDS_BIGENDIAN: Fix bug "AX_C_FLOAT_WORDS_BIGENDIAN fails whenever interprocedural optimization is enabled."
> Previous versions of this macro would not work when interprocedural
> optimization (via link-time optimization) was enabled. This would happen
> when, say, the GCC/clang "-flto" flag, or the ICC "-ipo" flag was used, for
> example. The problem was that under these conditions, the compiler did not
> allocate for and write the special float value in the data segment of the
> test object file. Thus, the special value (in platform-dependent binary form)
> could not be found, and the macro would fail.
> The solution to the above problem was to:
> 1) Compile and link a whole test program rather than just compile an
> object file.
> 2) Add code that requires the compiler to write the special value to
> the data segment of the program executable.
> For further details, refer to the documentation in the macro source file. Note
> that this change already increments the serial number of the file.
> This change resolves the following issues:
> CPython issue #89640
> https://github.com/python/cpython/issues/89640
> Gentoo bug #700012
> https://bugs.gentoo.org/700012
> Cairo issue #459
> https://gitlab.freedesktop.org/cairo/cairo/-/issues/459
> Poky (Yocto Project) #12699
> https://lists.yoctoproject.org/g/poky/topic/89131836
> 2023.05.07
> ax_add_fortify_source.m4: fix 2nd probe
> it didnt error anymore, just warned.
> thus without -O it still enabled the 2nd variant
> 2023.05.01
> bump serial numbers after recent changes
> 2023.04.19
> ax_ext_have_lib.m4: fix typo
> ax_python_config_var.m4: fix typo
> ax_path_bdb.m4: fix typo
> ax_pkg_mico.m4: fix typo
> ax_cvs.m4: fix typo
> ax_cc_tentdef.m4: fix typo
> ax_ms_cpprest.m4: fix typo
> ax_check_java_plugin.m4: fix typo
> ax_cc_attrcommon.m4: Fix typo
> ax_boost_base.m4: fix comment typo
> 2023.04.13
> Re-format macros into canonical format after recent changes.
> Merge pull request #263 from k4rtik/icu
> ax_check_icu: bump serial and update after icu-config deprecation
> Merge pull request #275 from cstes/ax_cc_tentdef
> ax_cc_tentdef: test for C tentative definitions
> Merge pull request #276 from theAeon/master
> AX_BLAS: Fix vecLib detection on modern MacOS
> 2023.04.12
> Fix vecLib detection on modern MacOS
> For whatever reason Apple's hardened runtime scoping disallows third-party
> linking to -framework vecLib. Linking -framework Accelerate solves this issue.
> 2023.04.10
> ax_cc_tentdef: test for C tentative definitions
> 2023.03.08
> ax_lib_netcdf4: NF_CONFIG instead of NC_CONFIG for Fortran flags.
> NF_CONFIG is better and safer than NC_CONFIG, for NETCDF4_FFLAGS and
> NETCDF4_FLIBS configuration.
>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> config/rootfiles/common/autoconf-archive | 4 ++++
> lfs/autoconf-archive | 6 +++---
> 2 files changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/config/rootfiles/common/autoconf-archive b/config/rootfiles/common/autoconf-archive
> index f096797ec..c57bb5468 100644
> --- a/config/rootfiles/common/autoconf-archive
> +++ b/config/rootfiles/common/autoconf-archive
> @@ -65,8 +65,10 @@
> #usr/share/aclocal/ax_cache_size.m4
> #usr/share/aclocal/ax_caolan_check_package.m4
> #usr/share/aclocal/ax_caolan_search_package.m4
> +#usr/share/aclocal/ax_cc_attrcommon.m4
> #usr/share/aclocal/ax_cc_for_build.m4
> #usr/share/aclocal/ax_cc_maxopt.m4
> +#usr/share/aclocal/ax_cc_tentdef.m4
> #usr/share/aclocal/ax_cf_ebcdic.m4
> #usr/share/aclocal/ax_cflags_aix_option.m4
> #usr/share/aclocal/ax_cflags_force_c89.m4
> @@ -336,7 +338,9 @@
> #usr/share/aclocal/ax_func_mkdir.m4
> #usr/share/aclocal/ax_func_posix_memalign.m4
> #usr/share/aclocal/ax_func_snprintf.m4
> +#usr/share/aclocal/ax_func_which_gethostbyaddr_r.m4
> #usr/share/aclocal/ax_func_which_gethostbyname_r.m4
> +#usr/share/aclocal/ax_func_which_gethostent_r.m4
> #usr/share/aclocal/ax_func_which_getservbyname_r.m4
> #usr/share/aclocal/ax_gcc_archflag.m4
> #usr/share/aclocal/ax_gcc_builtin.m4
> diff --git a/lfs/autoconf-archive b/lfs/autoconf-archive
> index ed7c77fbc..09bc8cf1d 100644
> --- a/lfs/autoconf-archive
> +++ b/lfs/autoconf-archive
> @@ -1,7 +1,7 @@
> ###############################################################################
> # #
> # IPFire.org - A linux based firewall #
> -# Copyright (C) 2007-2018 IPFire Team <info(a)ipfire.org> #
> +# Copyright (C) 2007-2024 IPFire Team <info(a)ipfire.org> #
> # #
> # This program is free software: you can redistribute it and/or modify #
> # it under the terms of the GNU General Public License as published by #
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 2023.02.20
> +VER = 2024.10.16
>
> THISAPP = autoconf-archive-$(VER)
> DL_FILE = $(THISAPP).tar.xz
> @@ -39,7 +39,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_BLAKE2 = a72469e61a6ef702cbf4e30712c7dbe36369da7dad6e2312eb7026af41a989a47ded0a27975349486b69155f9e8199f89720dc57f98440b2766294a0f8755ee6
> +$(DL_FILE)_BLAKE2 = 64554b7258c527f2e6bb115bec08e358bd4f10b940cdbe58c073fb3bdeccab78897250766e600b7e5fd79a76d633135d1caf2c7e81893bd68cab704073cac2c5
>
> install : $(TARGET)
>
> --
> 2.47.0
>
next prev parent reply other threads:[~2024-11-18 20:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 19:58 [PATCH] abseil-cpp: Update to version 20240722.0 Adolf Belka
2024-11-12 19:58 ` [PATCH] autoconf-archive: Update to version 2024.10.16 Adolf Belka
2024-11-18 20:04 ` Michael Tremer [this message]
2024-11-12 19:58 ` [PATCH] btrfs-progs: Update to version 6.11 Adolf Belka
2024-11-18 20:04 ` Michael Tremer
2024-11-12 19:58 ` [PATCH] protobuf: Update to version 28.3 Adolf Belka
2024-11-18 20:04 ` Michael Tremer
2024-11-12 19:58 ` [PATCH] wget: Update to version 1.25.0 Adolf Belka
2024-11-18 20:04 ` Michael Tremer
2024-11-18 20:04 ` [PATCH] abseil-cpp: Update to version 20240722.0 Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=284A4384-06EE-481F-9C59-2BFD4A4DF2FE@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox