public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/gdb] gdb-17.2-rebase-f44: Fix more broken configure files
Date: Sun, 28 Jun 2026 00:00:01 GMT [thread overview]
Message-ID: <178260480165.1.9287489878907333616.rpms-gdb-51337c28d9eb@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/gdb
Branch : gdb-17.2-rebase-f44
Commit : 51337c28d9eb91a7a2599d3515e9de734a3c02ee
Author : Jeff Law <law@redhat.com>
Date : 2020-07-21T00:58:44-06:00
Stats : +34/-2 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/gdb/c/51337c28d9eb91a7a2599d3515e9de734a3c02ee?branch=gdb-17.2-rebase-f44
Log:
Fix more broken configure files
---
diff --git a/gdb-config.patch b/gdb-config.patch
index 982037b..b26d668 100644
--- a/gdb-config.patch
+++ b/gdb-config.patch
@@ -11,8 +11,8 @@ diff -Nrup a/gnulib/import/m4/alloca.m4 b/gnulib/import/m4/alloca.m4
{
int dir, dummy = 0;
diff -Nrup a/libiberty/aclocal.m4 b/libiberty/aclocal.m4
---- a/libiberty/aclocal.m4 2019-11-18 18:49:21.000000000 -0700
-+++ b/libiberty/aclocal.m4 2020-01-11 01:08:23.142342127 -0700
+--- a/libiberty/aclocal.m4 2019-01-19 09:01:34.000000000 -0700
++++ b/libiberty/aclocal.m4 2020-01-09 22:00:27.183312982 -0700
@@ -147,7 +147,7 @@ if test $ac_cv_os_cray = yes; then
fi
@@ -22,3 +22,35 @@ diff -Nrup a/libiberty/aclocal.m4 b/libiberty/aclocal.m4
{
static char *addr = 0;
auto char dummy;
+diff --git a/config/intdiv0.m4 b/config/intdiv0.m4
+index 55dddcf1..ba906efc 100644
+--- a/config/intdiv0.m4
++++ b/config/intdiv0.m4
+@@ -31,10 +31,10 @@ sigfpe_handler (sig) int sig;
+ exit (sig != SIGFPE);
+ }
+
+-int x = 1;
+-int y = 0;
+-int z;
+-int nan;
++volatile int x = 1;
++volatile int y = 0;
++volatile int z;
++volatile int nan;
+
+ int main ()
+ {
+diff --git a/libiberty/configure.ac b/libiberty/configure.ac
+index f1ce7601..fc20d228 100644
+--- a/libiberty/configure.ac
++++ b/libiberty/configure.ac
+@@ -661,7 +661,7 @@ if test -z "${setobjs}"; then
+ for v in $vars; do
+ AC_MSG_CHECKING([for $v])
+ AC_CACHE_VAL(libiberty_cv_var_$v,
+- [AC_LINK_IFELSE([AC_LANG_PROGRAM([[int *p;]],[[extern int $v []; p = $v;]])],
++ [AC_LINK_IFELSE([AC_LANG_PROGRAM([[__attribute__ ((used)) int *p;]],[[extern int $v []; p = $v;]])],
+ [eval "libiberty_cv_var_$v=yes"],
+ [eval "libiberty_cv_var_$v=no"])])
+ if eval "test \"`echo '$libiberty_cv_var_'$v`\" = yes"; then
reply other threads:[~2026-06-28 0:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=178260480165.1.9287489878907333616.rpms-gdb-51337c28d9eb@fedoraproject.org \
--to=law@redhat.com \
--cc=git-commits@fedoraproject.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