From: "Luke T. Shumaker" <lukeshu@lukeshu.com>
To: binutils@sourceware.org, gdb-patches@sourceware.org
Cc: "Ralf Wildenhues" <Ralf.Wildenhues@gmx.de>,
"Alfred M. Szmidt" <ams@gnu.org>,
"Tom Tromey" <tromey@adacore.com>,
"Maciej W. Rozycki" <macro@orcam.me.uk>,
Jan Beulich <jbeulich@suse.com>,
Joseph Myers <josmyers@redhat.com>,
"Luke T. Shumaker" <lukeshu@lukeshu.com>
Subject: [PATCH v2 4/5] readline: Re-generate configure
Date: Sun, 9 Jun 2024 21:08:32 -0600 [thread overview]
Message-ID: <20240610030833.472301-5-lukeshu@lukeshu.com> (raw)
In-Reply-To: <20240606201145.1747021-1-lukeshu@lukeshu.com>
`readline/readline/configure` has been out-of-date with configure.ac
(just a whitespace change) since 2cac47f5bab (autoupdate: replace
obsolete macros AC_AIX, AC_MINIX, and AC_GNU_SOURCE, Matthieu Longo,
2024-05-28). Re-generate it.
---
v2:
- This patch was not present in v1, as configure was not yet out of
date.
---
readline/readline/configure | 1 -
1 file changed, 1 deletion(-)
diff --git a/readline/readline/configure b/readline/readline/configure
index 6ea4545e26f..5a1c6363d5f 100755
--- a/readline/readline/configure
+++ b/readline/readline/configure
@@ -3923,7 +3923,6 @@ $as_echo "$ac_cv_safe_to_define___extensions__" >&6; }
-
# If we're using gcc and the user hasn't specified CFLAGS, add -O2 to CFLAGS
if test -n "$want_auto_cflags" ; then
AUTO_CFLAGS="-g ${GCC+-O2}"
--
2.45.1
next prev parent reply other threads:[~2024-06-10 3:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 20:11 [PATCH 0/4] Add a ./bootstrap script to automate bundling and generating files Luke T. Shumaker
2024-06-06 20:11 ` [PATCH 1/4] readline: Fix examples/rlfe/configure.ac Luke T. Shumaker
2024-06-08 18:25 ` Maciej W. Rozycki
2024-06-08 18:28 ` Maciej W. Rozycki
2024-06-10 3:01 ` Luke T. Shumaker
2024-06-10 16:51 ` Simon Marchi
2024-06-06 20:11 ` [PATCH 2/4] Update COPYING files from gnu.org Luke T. Shumaker
2024-06-06 20:11 ` [PATCH 3/4] zlib: Remove files that should certainly not be checked in Luke T. Shumaker
2024-06-07 6:24 ` Jan Beulich
2024-06-07 7:53 ` Luke T. Shumaker
2024-06-10 3:04 ` Luke T. Shumaker
2024-06-08 0:35 ` Luke T. Shumaker
2024-06-06 20:11 ` [PATCH 4/4] Add a ./bootstrap script to automate bundling and generating files Luke T. Shumaker
2024-06-06 20:53 ` Luke T. Shumaker
2024-06-06 20:57 ` Joseph Myers
2024-06-07 8:23 ` Luke T. Shumaker
2024-06-10 19:27 ` Joseph Myers
2024-06-12 7:02 ` Luke T. Shumaker
2024-06-12 12:58 ` Tom Tromey
2024-06-06 20:55 ` [PATCH 0/4] " Luke T. Shumaker
2024-06-10 3:08 ` [PATCH v2 0/5] " Luke T. Shumaker
2024-06-10 3:08 ` [PATCH v2 1/5] readline: Fix examples/rlfe/configure.in Luke T. Shumaker
2024-06-10 22:49 ` Hans-Peter Nilsson
2024-06-10 3:08 ` [PATCH v2 2/5] Update COPYING files from gnu.org Luke T. Shumaker
2024-06-10 3:08 ` [PATCH v2 3/5] zlib: Remove files that should certainly not be checked in Luke T. Shumaker
2024-06-10 3:08 ` Luke T. Shumaker [this message]
2024-06-10 3:08 ` [PATCH v2 5/5] Add a ./bootstrap script to automate bundling and generating files Luke T. Shumaker
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=20240610030833.472301-5-lukeshu@lukeshu.com \
--to=lukeshu@lukeshu.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=ams@gnu.org \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=jbeulich@suse.com \
--cc=josmyers@redhat.com \
--cc=macro@orcam.me.uk \
--cc=tromey@adacore.com \
/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).