From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Lucas Stach <l.stach@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] host-autotools-autoconf: version bump 2.71 -> 2.72
Date: Fri, 23 Jan 2026 16:02:07 +0100 [thread overview]
Message-ID: <20260123150207.1571471-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260113162347.2679126-1-l.stach@pengutronix.de>
Thanks, applied as 05335d8bf6c6879f880a521814bb5ab1c013e576.
Michael
[sent from post-receive hook]
On Fri, 23 Jan 2026 16:02:07 +0100, Lucas Stach <l.stach@pengutronix.de> wrote:
> Citing the release announcement:
> 2.72 consists largely of bug fixes. The most significant changes are
> support for the upcoming 2024 edition of the C standard (aka C23)
> and a mechanism for enabling 64-bit time_t on 32-bit platforms
> (--enable-year2038).
>
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> Message-Id: <20260113162347.2679126-1-l.stach@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/host-autotools-autoconf.make b/rules/host-autotools-autoconf.make
> index 99c268967af6..a68ba9af384b 100644
> --- a/rules/host-autotools-autoconf.make
> +++ b/rules/host-autotools-autoconf.make
> @@ -14,8 +14,8 @@ LAZY_PACKAGES-$(PTXCONF_HOST_AUTOTOOLS_AUTOCONF) += host-autotools-autoconf
> #
> # Paths and names
> #
> -HOST_AUTOTOOLS_AUTOCONF_VERSION := 2.71
> -HOST_AUTOTOOLS_AUTOCONF_MD5 := 12cfa1687ffa2606337efe1a64416106
> +HOST_AUTOTOOLS_AUTOCONF_VERSION := 2.72
> +HOST_AUTOTOOLS_AUTOCONF_MD5 := 1be79f7106ab6767f18391c5e22be701
> HOST_AUTOTOOLS_AUTOCONF := autoconf-$(HOST_AUTOTOOLS_AUTOCONF_VERSION)
> HOST_AUTOTOOLS_AUTOCONF_SUFFIX := tar.xz
> HOST_AUTOTOOLS_AUTOCONF_URL := $(call ptx/mirror, GNU, autoconf/$(HOST_AUTOTOOLS_AUTOCONF).$(HOST_AUTOTOOLS_AUTOCONF_SUFFIX))
prev parent reply other threads:[~2026-01-23 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 16:23 [ptxdist] [PATCH] " Lucas Stach
2026-01-23 15:02 ` Michael Olbrich [this message]
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=20260123150207.1571471-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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