public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/gdb] gdb-17.2-rebase-f44: [rhel6 dts] Use devtoolset gcc for GDB being now in C++11.
Date: Sat, 27 Jun 2026 23:58:16 GMT	[thread overview]
Message-ID: <178260469662.1.15439186876608360180.rpms-gdb-4d0140dca173@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/gdb
Branch : gdb-17.2-rebase-f44
Commit : 4d0140dca173e64e298b7c593dbdb0ee3a92a0b6
Author : Jan Kratochvil <jan.kratochvil@redhat.com>
Date   : 2017-06-12T21:57:44+02:00
Stats  : +24/-1 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/gdb/c/4d0140dca173e64e298b7c593dbdb0ee3a92a0b6?branch=gdb-17.2-rebase-f44

Log:
[rhel6 dts] Use devtoolset gcc for GDB being now in C++11.

---
diff --git a/gdb.spec b/gdb.spec
index 366739b..9450b42 100644
--- a/gdb.spec
+++ b/gdb.spec
@@ -26,7 +26,7 @@ Version: 8.0
 
 # 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: 16%{?dist}
+Release: 17%{?dist}
 
 License: GPLv3+ and GPLv3+ with exceptions and GPLv2+ and GPLv2+ with exceptions and GPL+ and LGPLv2+ and LGPLv3+ and BSD and Public Domain and GFDL
 Group: Development/Debuggers
@@ -126,6 +126,11 @@ BuildRequires: %{librpmname}
 Recommends: %{librpmname}
 %endif
 
+%if 0%{?el6:1}
+# GDB C++11 requires devtoolset gcc.
+BuildRequires: %{?scl_prefix}gcc-c++
+%endif
+
 # GDB patches have the format `gdb-<version>-bz<red-hat-bz-#>-<desc>.patch'.
 # They should be created using patch level 1: diff -up ./gdb (or gdb-6.3/gdb).
 
@@ -1091,6 +1096,11 @@ rm -rf %{buildroot}
 
 test -e %{_root_libdir}/librpm.so.%{librpmver}
 
+%if 0%{?el6:1}
+# GDB C++11 requires devtoolset gcc.
+%{?scl:PATH=%{_bindir}${PATH:+:${PATH}}}
+%endif
+
 # Identify the build directory with the version of gdb as well as the
 # architecture, to allow for mutliple versions to be installed and
 # built.
@@ -1376,6 +1386,11 @@ echo ====================TESTING END=====================
 cd %{gdb_build}
 rm -rf $RPM_BUILD_ROOT
 
+%if 0%{?el6:1}
+# GDB C++11 requires devtoolset gcc.
+%{?scl:PATH=%{_bindir}${PATH:+:${PATH}}}
+%endif
+
 make %{?_smp_mflags} install DESTDIR=$RPM_BUILD_ROOT
 
 %if 0%{!?scl:1}
@@ -1524,7 +1539,12 @@ rm -rf $RPM_BUILD_ROOT
 
 %files
 %defattr(-,root,root)
+# File must begin with "/": {GFDL,COPYING3,COPYING,COPYING.LIB,COPYING3.LIB}
+%if 0%{!?el6:1}
 %license COPYING3 COPYING COPYING.LIB COPYING3.LIB
+%else
+%doc     COPYING3 COPYING COPYING.LIB COPYING3.LIB
+%endif
 %doc README NEWS
 %{_bindir}/gdb
 %{_bindir}/gcore
@@ -1615,6 +1635,9 @@ then
 fi
 
 %changelog
+* Mon Jun 12 2017 Jan Kratochvil <jan.kratochvil@redhat.com> - 8.0-17.fc26
+- [rhel6 dts] Use devtoolset gcc for GDB being now in C++11.
+
 * Sat Jun 10 2017 Jan Kratochvil <jan.kratochvil@redhat.com> - 8.0-16.fc26
 - [dts] Upgrade libstdc++-v3-python to 7.1.1-20170526.
 

                 reply	other threads:[~2026-06-27 23:58 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=178260469662.1.15439186876608360180.rpms-gdb-4d0140dca173@fedoraproject.org \
    --to=jan.kratochvil@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