public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/gdb] gdb-17.2-rebase-f44: add x86_64-redhat-linux-gnu to --enable-targets list for full GDB
Date: Sun, 28 Jun 2026 00:01:54 GMT	[thread overview]
Message-ID: <178260491492.1.1750232657972504797.rpms-gdb-e52c9dae7003@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/gdb
            Branch : gdb-17.2-rebase-f44
            Commit : e52c9dae7003b6a607c43347fa18dd92ba6e73f6
            Author : Andrew Burgess <aburgess@redhat.com>
            Date   : 2024-11-13T09:29:07+00:00
            Stats  : +7/-2 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/gdb/c/e52c9dae7003b6a607c43347fa18dd92ba6e73f6?branch=gdb-17.2-rebase-f44

            Log:
            add x86_64-redhat-linux-gnu to --enable-targets list for full GDB

Add x86_64-redhat-linux-gnu to --enable-targets list for full GDB in
gdb.spec. This ensures we can remote debug x86-64 targets from
non-x86-64 hosts.  This fixes rhbz 2308522.

There was an earlier commit which added x86_64-redhat-linux-gnu to the
--enable-targets list for the gdb.minimal build (commit 692cc832db8d),
but that commit missed extending the full GDB build flags.

---
diff --git a/gdb.spec b/gdb.spec
index 2803e1b..83c7f57 100644
--- a/gdb.spec
+++ b/gdb.spec
@@ -45,7 +45,7 @@ Version: 15.2
 
 # The release always contains a leading reserved number, start it at 1.
 # `upstream' is not a part of `name' to stay fully rpm dependencies compatible for the testing.
-Release: 2%{?dist}
+Release: 3%{?dist}
 
 License: GPL-3.0-or-later AND BSD-3-Clause AND FSFAP AND LGPL-2.1-or-later AND GPL-2.0-or-later AND LGPL-2.0-or-later AND LicenseRef-Fedora-Public-Domain AND GFDL-1.3-or-later AND LGPL-2.0-or-later WITH GCC-exception-2.0 AND GPL-3.0-or-later WITH GCC-exception-3.1 AND GPL-2.0-or-later WITH GNU-compiler-exception
 # Do not provide URL for snapshots as the file lasts there only for 2 days.
@@ -548,7 +548,7 @@ $(: ppc64 host build crashes on ppc variant of libexpat.so )    \
 %endif
         --with-auto-load-dir='$debugdir:$datadir/auto-load%{?scl::%{_root_datadir}/gdb/auto-load}'      \
         --with-auto-load-safe-path='$debugdir:$datadir/auto-load%{?scl::%{_root_datadir}/gdb/auto-load}'        \
-        --enable-targets=s390-linux-gnu,powerpc-linux-gnu,arm-linux-gnu,aarch64-linux-gnu,riscv64-linux-gnu     \
+        --enable-targets=s390-linux-gnu,powerpc-linux-gnu,arm-linux-gnu,aarch64-linux-gnu,riscv64-linux-gnu,x86_64-redhat-linux-gnu     \
         %{_target_platform}
 
 if [ -z "%{!?_with_profile:no}" ]
@@ -928,6 +928,11 @@ fi
 # endif scl
 
 %changelog
+* Wed Nov 13 2024 Andrew Burgess <aburgess@redhat.com>
+- Add x86_64-redhat-linux-gnu to --enable-targets for full GDB build
+  in gdb.spec, this ensures we can remote debug x86-64 targets from
+  non-x86-64 hosts.  This fixes rhbz 2308522.
+
 * Tue Nov 12 2024 Andrew Burgess <aburgess@redhat.com>
 - Remove gdb-6.6-testsuite-timeouts.patch.  I updated the upstream
   tests in commit 06b8b0ad976 so this patch is no longer useful.

                 reply	other threads:[~2026-06-28  0:01 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=178260491492.1.1750232657972504797.rpms-gdb-e52c9dae7003@fedoraproject.org \
    --to=aburgess@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