From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Siddhesh Poyarekar <siddhesh@sourceware.org>, libc-alpha@sourceware.org
Cc: "Andreas K . Huettel" <dilfridge@gentoo.org>,
Carlos O'Donell <carlos@redhat.com>
Subject: Re: [PATCH v3] configure: Use autoconf 2.71
Date: Mon, 17 Jul 2023 10:46:11 -0400 [thread overview]
Message-ID: <b4f81f07-3ac3-1d36-2874-0de4c6c4ed14@gotplt.org> (raw)
In-Reply-To: <20230717142150.185969-1-siddhesh@sourceware.org>
On 2023-07-17 10:21, Siddhesh Poyarekar via Libc-alpha wrote:
> Bump autoconf requirement to 2.71 to allow regenerating configure on
> more recent distributions. autoconf 2.71 has been in Fedora since F36
> and is the current version in Debian stable (bookworm). It appears to
> be current in Gentoo as well.
>
> All sysdeps configure and preconfigure scripts have also been
> regenerated; all changes are trivial transformations that do not affect
> functionality.
>
> Signed-off-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
> Reviewed-by: Carlos O'Donell <carlos@redhat.com>
> ---
> Change from v2:
>
> Resolved conflicts in ./configure and sysdeps/loongarch/configure. I'll
> push this once `make check` finishes.
I've pushed this now. As discussed in the patch review call today, let
me try and turn the remaining patches around as soon as I can. If I can
do it soon enough we could add them to 2.38, or else skip over and add
to 2.39.
Thanks,
Sid
next prev parent reply other threads:[~2023-07-17 14:52 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 18:41 [PATCH 0/4] Update default build configuration Siddhesh Poyarekar
2023-06-29 18:41 ` [PATCH 1/4] configure: Use autoconf 2.71 Siddhesh Poyarekar
2023-06-29 19:48 ` Joseph Myers
2023-06-29 19:56 ` Siddhesh Poyarekar
2023-06-29 20:03 ` Siddhesh Poyarekar
2023-06-29 20:07 ` Joseph Myers
2023-06-29 22:16 ` Zack Weinberg
2023-06-29 18:41 ` [PATCH 2/4] configure: Default --enable-stack-protector to strong Siddhesh Poyarekar
2023-06-29 18:41 ` [PATCH 3/4] Disable lazy binding by default Siddhesh Poyarekar
2023-06-29 21:54 ` Michael Hudson-Doyle
2023-06-29 22:16 ` Siddhesh Poyarekar
2023-06-29 18:41 ` [PATCH 4/4] configure: Disable building libcrypt " Siddhesh Poyarekar
2023-06-29 18:45 ` Dmitry V. Levin
2023-06-29 19:02 ` Siddhesh Poyarekar
2023-07-14 6:21 ` Sam James
2023-07-17 15:24 ` Siddhesh Poyarekar
2023-07-17 17:26 ` Sam James
2023-06-30 1:42 ` [PATCH v2 0/4] Update default build configuration Siddhesh Poyarekar
2023-06-30 1:42 ` [PATCH v2 1/4] configure: Use autoconf 2.71 Siddhesh Poyarekar
2023-07-14 21:00 ` Carlos O'Donell
2023-07-17 14:21 ` [PATCH v3] " Siddhesh Poyarekar
2023-07-17 14:46 ` Siddhesh Poyarekar [this message]
2023-06-30 1:42 ` [PATCH v2 2/4] configure: Default --enable-stack-protector to strong Siddhesh Poyarekar
2023-07-13 9:51 ` Florian Weimer
2023-07-17 14:55 ` Siddhesh Poyarekar
2023-07-17 15:45 ` Florian Weimer
2023-07-17 15:52 ` Siddhesh Poyarekar
2023-08-03 10:06 ` Florian Weimer
2023-06-30 1:42 ` [PATCH v2 3/4] configure: Disable lazy binding by default Siddhesh Poyarekar
2023-07-13 9:38 ` Florian Weimer
2023-07-17 14:57 ` Siddhesh Poyarekar
2023-07-17 15:30 ` Florian Weimer
2023-07-17 15:55 ` Siddhesh Poyarekar
2023-07-18 16:25 ` Andreas K. Huettel
2023-06-30 1:42 ` [PATCH v2 4/4] configure: Disable building libcrypt " Siddhesh Poyarekar
2023-07-13 9:40 ` Florian Weimer
2023-07-14 4:16 ` Mark Harris
2023-07-17 15:13 ` Siddhesh Poyarekar
2023-07-17 16:44 ` [PATCH v3] " Siddhesh Poyarekar
2023-07-17 17:18 ` Andreas Schwab
2023-07-17 18:17 ` Siddhesh Poyarekar
2023-07-20 18:05 ` Joseph Myers
2023-07-20 18:39 ` Andreas K. Huettel
2023-07-07 10:31 ` [ping][PATCH v2 0/4] Update default build configuration Siddhesh Poyarekar
2023-07-12 21:51 ` [ping2][PATCH " Siddhesh Poyarekar
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=b4f81f07-3ac3-1d36-2874-0de4c6c4ed14@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=carlos@redhat.com \
--cc=dilfridge@gentoo.org \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).