public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Fabian Groffen" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-debug/gdb/
Date: Sun, 21 Jul 2024 13:04:00 +0000 (UTC)	[thread overview]
Message-ID: <1721567037.8c67eb5c50030b45953766cf2f20a3d6aa8501dd.grobian@gentoo> (raw)

commit:     8c67eb5c50030b45953766cf2f20a3d6aa8501dd
Author:     Fabian Groffen <grobian <AT> gentoo <DOT> org>
AuthorDate: Sun Jul 21 13:00:49 2024 +0000
Commit:     Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Sun Jul 21 13:03:57 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8c67eb5c

dev-build/gdb-15.1: drop Solaris build-hack

We'll disable the culprint (Python) instead.

Signed-off-by: Fabian Groffen <grobian <AT> gentoo.org>

 dev-debug/gdb/gdb-15.1.ebuild | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/dev-debug/gdb/gdb-15.1.ebuild b/dev-debug/gdb/gdb-15.1.ebuild
index 541bf7f8915a..89469e978771 100644
--- a/dev-debug/gdb/gdb-15.1.ebuild
+++ b/dev-debug/gdb/gdb-15.1.ebuild
@@ -131,14 +131,6 @@ src_prepare() {
 	# Avoid using ancient termcap from host on Prefix systems
 	sed -i -e 's/termcap tinfow/tinfow/g' \
 		gdb/configure{.ac,} || die
-	if [[ ${CHOST} == *-solaris* ]] ; then
-		# code relies on C++11, so make sure we get that selected
-		# due to Python 3.11 pymacro.h doing stuff to work around
-		# versioning mess based on the C version, while we're compiling
-		# C++ here, so we need to make it clear we're doing C++11/C11
-		# because Solaris system headers act on these
-		sed -i -e 's/-x c++/-std=c++11/' gdb/Makefile.in || die
-	fi
 }
 
 gdb_branding() {


             reply	other threads:[~2024-07-21 13:04 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-21 13:04 Fabian Groffen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-08 11:57 [gentoo-commits] repo/gentoo:master commit in: dev-debug/gdb/ Sam James
2024-11-08 10:59 Sam James
2024-11-08  6:31 Sam James
2024-11-08  3:54 Sam James
2024-10-27 18:19 Andreas K. Hüttel
2024-10-18 17:32 Arthur Zamarin
2024-10-15 12:47 Arthur Zamarin
2024-10-14  0:50 Sam James
2024-10-14  0:50 Sam James
2024-10-14  0:16 Sam James
2024-10-14  0:16 Sam James
2024-10-13 23:50 Sam James
2024-10-03  9:35 Sam James
2024-09-29 21:05 Sam James
2024-09-29 21:05 Sam James
2024-07-17  5:56 Sam James
2024-07-17  5:56 Sam James
2024-07-17  5:56 Sam James
2024-07-17  5:17 Sam James
2024-07-17  5:16 Sam James
2024-07-17  4:59 Sam James
2024-07-17  4:56 Sam James
2024-07-08  3:32 Sam James
2024-06-02  0:14 Sam James
2024-05-11 15:19 Sam James
2024-04-25 23:10 Sam James
2024-04-25 23:10 Sam James
2024-04-25 22:18 Sam James
2024-04-25 22:18 Sam James
2024-04-25 22:18 Sam James
2024-04-25 22:18 Sam James
2024-04-25 22:18 Sam James
2024-03-04 10:24 Sam James
2024-03-03  7:02 Sam James
2024-02-25  9:38 Fabian Groffen
2024-02-20  7:45 Sam James
2024-02-20  7:45 Sam James
2024-02-20  7:45 Sam James
2024-02-20  7:22 Sam James
2024-02-20  7:22 Sam James
2024-02-20  5:56 Sam James
2024-02-20  5:56 Sam James
2024-02-20  5:56 Sam James

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=1721567037.8c67eb5c50030b45953766cf2f20a3d6aa8501dd.grobian@gentoo \
    --to=grobian@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