From: "Conrad Kostecki" <conikost@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-shells/bash/files/
Date: Sat, 04 Jan 2025 22:47:52 +0000 (UTC) [thread overview]
Message-ID: <1736030825.cd135337b386ce8a9276a0cd47de8e2a9c5f6871.conikost@gentoo> (raw)
commit: cd135337b386ce8a9276a0cd47de8e2a9c5f6871
Author: Michael Mair-Keimberger <mmk <AT> levelnine <DOT> at>
AuthorDate: Fri Jan 3 15:28:31 2025 +0000
Commit: Conrad Kostecki <conikost <AT> gentoo <DOT> org>
CommitDate: Sat Jan 4 22:47:05 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cd135337
app-shells/bash: remove unused patch
Signed-off-by: Michael Mair-Keimberger <mmk <AT> levelnine.at>
Signed-off-by: Conrad Kostecki <conikost <AT> gentoo.org>
.../files/bash-5.2_p21-configure-strtold.patch | 32 ----------------------
1 file changed, 32 deletions(-)
diff --git a/app-shells/bash/files/bash-5.2_p21-configure-strtold.patch b/app-shells/bash/files/bash-5.2_p21-configure-strtold.patch
deleted file mode 100644
index 51e9a19daebb..000000000000
--- a/app-shells/bash/files/bash-5.2_p21-configure-strtold.patch
+++ /dev/null
@@ -1,32 +0,0 @@
-https://src.fedoraproject.org/rpms/bash/blob/bd5ac20b134f2936c54245fc83a8e70207d3e07e/f/bash-configure-c99-2.patch
-
-Another C compatibility issue: char ** and char * are distinct types,
-and strtold expects the former for its second argument.
-
-Submitted upstream:
-
- <https://lists.gnu.org/archive/html/bug-bash/2023-11/msg00104.html>
-
---- configure.ac
-+++ configure.ac
-@@ -885,7 +885,7 @@ AC_CHECK_DECLS([strtold], [
- [AC_COMPILE_IFELSE(
- [AC_LANG_PROGRAM(
- [[#include <stdlib.h>]],
-- [[long double r; char *foo, bar; r = strtold(foo, &bar);]]
-+ [[long double r; char *foo, *bar; r = strtold(foo, &bar);]]
- )],
- [bash_cv_strtold_broken=no],[bash_cv_strtold_broken=yes])
- ]
-
---- configure
-+++ configure
-@@ -15676,7 +15676,7 @@ else $as_nop
- int
- main (void)
- {
--long double r; char *foo, bar; r = strtold(foo, &bar);
-+long double r; char *foo, *bar; r = strtold(foo, &bar);
-
- ;
- return 0;
next reply other threads:[~2025-01-04 22:47 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 22:47 Conrad Kostecki [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-07 12:48 [gentoo-commits] repo/gentoo:master commit in: app-shells/bash/files/ Sam James
2024-12-07 12:48 Sam James
2024-12-06 23:12 Conrad Kostecki
2023-12-31 2:38 Conrad Kostecki
2023-04-26 21:08 Mike Gilbert
2023-04-25 21:30 Sam James
2023-03-04 19:29 Sven Wegener
2022-11-16 18:36 Conrad Kostecki
2022-09-11 23:13 Mike Gilbert
2021-07-10 21:16 Conrad Kostecki
2021-05-29 18:51 Lars Wendler
2020-12-01 13:16 Lars Wendler
2020-06-13 16:24 Mike Gilbert
2019-09-15 7:53 Mike Frysinger
2018-06-26 15:05 Mike Gilbert
2018-01-04 23:48 Sven Wegener
2017-10-20 7:45 Patrice Clement
2017-06-10 12:02 Jason Donenfeld
2017-06-10 3:07 Jason Donenfeld
2017-06-10 3:06 Jason Donenfeld
2016-07-16 9:54 Patrice Clement
2016-06-23 6:03 Mike Frysinger
2016-06-23 5:31 Mike Frysinger
2016-02-03 18:52 Mike Frysinger
2016-02-03 18:52 Mike Frysinger
2016-02-03 18:52 Mike Frysinger
2016-02-03 18:52 Mike Frysinger
2016-02-03 18:52 Mike Frysinger
2016-02-03 18:52 Mike Frysinger
2016-01-26 7:23 Mike Frysinger
2016-01-26 7:23 Mike Frysinger
2016-01-26 7:23 Mike Frysinger
2015-12-02 18:59 Mike Frysinger
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=1736030825.cd135337b386ce8a9276a0cd47de8e2a9c5f6871.conikost@gentoo \
--to=conikost@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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