public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/valgrind/
Date: Sun, 22 Jan 2023 23:08:22 +0000 (UTC)	[thread overview]
Message-ID: <1674428833.b9589621d3748e5bb7486ee14d32f87ec7bcc503.sam@gentoo> (raw)

commit:     b9589621d3748e5bb7486ee14d32f87ec7bcc503
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Jan 22 23:07:02 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Jan 22 23:07:13 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b9589621

dev-util/valgrind: don't strip some components

Per README_PACKAGERS, this breaks Valgrind at least a bit, and sometimes entirely.

Signed-off-by: Sam James <sam <AT> gentoo.org>

 .../{valgrind-9999.ebuild => valgrind-3.20.0-r1.ebuild}        | 10 +++++++---
 dev-util/valgrind/valgrind-9999.ebuild                         |  9 ++++++---
 2 files changed, 13 insertions(+), 6 deletions(-)

diff --git a/dev-util/valgrind/valgrind-9999.ebuild b/dev-util/valgrind/valgrind-3.20.0-r1.ebuild
similarity index 92%
copy from dev-util/valgrind/valgrind-9999.ebuild
copy to dev-util/valgrind/valgrind-3.20.0-r1.ebuild
index aed73f6be21b..beb459c7a08c 100644
--- a/dev-util/valgrind/valgrind-9999.ebuild
+++ b/dev-util/valgrind/valgrind-3.20.0-r1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2022 Gentoo Authors
+# Copyright 1999-2023 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=8
@@ -26,6 +26,7 @@ PATCHES=(
 	# Respect CFLAGS, LDFLAGS
 	"${FILESDIR}"/${PN}-3.7.0-respect-flags.patch
 	"${FILESDIR}"/${PN}-3.15.0-Build-ldst_multiple-test-with-fno-pie.patch
+	"${FILESDIR}"/${P}-tests-clang16.patch
 )
 
 src_prepare() {
@@ -108,6 +109,9 @@ src_install() {
 
 	pax-mark m "${ED}"/usr/$(get_libdir)/valgrind/*-*-linux
 
+	# See README_PACKAGERS
+	dostrip -x /usr/libexec/valgrind/vgpreload* /usr/$(get_libdir)/valgrind/*
+
 	if [[ ${CHOST} == *-darwin* ]] ; then
 		# fix install_names on shared libraries, can't turn them into bundles,
 		# as dyld won't load them any more then, bug #306467
@@ -119,9 +123,9 @@ src_install() {
 }
 
 pkg_postinst() {
-	elog "Valgrind will not work if glibc does not have debug symbols."
+	elog "Valgrind will not work if libc (e.g. glibc) does not have debug symbols."
 	elog "To fix this you can add splitdebug to FEATURES in make.conf"
-	elog "and remerge glibc.  See:"
+	elog "and remerge glibc. See:"
 	elog "https://bugs.gentoo.org/show_bug.cgi?id=214065"
 	elog "https://bugs.gentoo.org/show_bug.cgi?id=274771"
 	elog "https://bugs.gentoo.org/show_bug.cgi?id=388703"

diff --git a/dev-util/valgrind/valgrind-9999.ebuild b/dev-util/valgrind/valgrind-9999.ebuild
index aed73f6be21b..13560a006c12 100644
--- a/dev-util/valgrind/valgrind-9999.ebuild
+++ b/dev-util/valgrind/valgrind-9999.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2022 Gentoo Authors
+# Copyright 1999-2023 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=8
@@ -108,6 +108,9 @@ src_install() {
 
 	pax-mark m "${ED}"/usr/$(get_libdir)/valgrind/*-*-linux
 
+	# See README_PACKAGERS
+	dostrip -x /usr/libexec/valgrind/vgpreload* /usr/$(get_libdir)/valgrind/*
+
 	if [[ ${CHOST} == *-darwin* ]] ; then
 		# fix install_names on shared libraries, can't turn them into bundles,
 		# as dyld won't load them any more then, bug #306467
@@ -119,9 +122,9 @@ src_install() {
 }
 
 pkg_postinst() {
-	elog "Valgrind will not work if glibc does not have debug symbols."
+	elog "Valgrind will not work if libc (e.g. glibc) does not have debug symbols."
 	elog "To fix this you can add splitdebug to FEATURES in make.conf"
-	elog "and remerge glibc.  See:"
+	elog "and remerge glibc. See:"
 	elog "https://bugs.gentoo.org/show_bug.cgi?id=214065"
 	elog "https://bugs.gentoo.org/show_bug.cgi?id=274771"
 	elog "https://bugs.gentoo.org/show_bug.cgi?id=388703"


             reply	other threads:[~2023-01-22 23:08 UTC|newest]

Thread overview: 100+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22 23:08 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-08 13:49 [gentoo-commits] repo/gentoo:master commit in: dev-util/valgrind/ Sam James
2023-10-31 18:53 Sam James
2023-10-26 16:48 Sam James
2023-10-26 16:48 Sam James
2023-10-23  7:48 Sam James
2023-08-28  6:40 Sam James
2023-06-09 16:42 Arthur Zamarin
2023-06-09 14:38 Sam James
2023-06-09 14:23 Arthur Zamarin
2023-05-20  4:20 Sam James
2023-04-29  4:54 Sam James
2023-04-29  1:39 Sam James
2023-04-29  0:40 Sam James
2023-01-27 12:20 Arthur Zamarin
2023-01-27 12:20 Arthur Zamarin
2023-01-27  9:25 Jakov Smolić
2023-01-27  8:21 Sam James
2023-01-27  8:21 Sam James
2023-01-27  8:21 Sam James
2023-01-25  2:32 Sam James
2023-01-24  5:53 Sam James
2023-01-23  1:12 Sam James
2023-01-23  1:11 Sam James
2023-01-22 23:12 Sam James
2023-01-22 23:12 Sam James
2023-01-22 23:12 Sam James
2023-01-22 23:08 Sam James
2022-12-29  1:40 Sam James
2022-12-29  1:35 Sam James
2022-12-29  1:35 Sam James
2022-12-29  1:35 Sam James
2022-10-28 10:39 Sam James
2022-09-16 19:27 Arthur Zamarin
2022-09-15 19:58 Arthur Zamarin
2022-09-14  7:48 Agostino Sarubbo
2022-09-14  7:48 Agostino Sarubbo
2022-09-14  7:47 Agostino Sarubbo
2022-07-31  6:30 Sam James
2022-07-27 13:47 Anthony G. Basile
2022-05-05 11:43 Jakov Smolić
2022-05-03  3:19 Sam James
2022-02-11 20:29 Arthur Zamarin
2022-02-11  7:25 Agostino Sarubbo
2022-02-10  9:43 Sam James
2022-02-10  9:10 Jakov Smolić
2022-02-10  9:10 Jakov Smolić
2021-10-25 11:56 Sam James
2021-10-25 11:56 Sam James
2021-10-17  5:49 Sam James
2021-06-07 13:16 Agostino Sarubbo
2021-06-04  8:14 Sam James
2021-06-03 16:26 Sam James
2021-06-02 16:44 Sam James
2021-06-01  6:36 Agostino Sarubbo
2021-03-22 13:10 Anthony G. Basile
2021-01-07  8:20 Fabian Groffen
2021-01-06 22:55 Fabian Groffen
2020-10-29 12:37 David Seifert
2020-10-29 12:37 David Seifert
2020-10-12  6:57 Agostino Sarubbo
2020-09-18  7:54 Agostino Sarubbo
2020-09-06  0:27 Sam James
2020-09-05 23:46 Thomas Deutschmann
2020-07-29 16:22 Sam James
2020-06-23 21:38 Anthony G. Basile
2020-05-28 21:49 Anthony G. Basile
2020-05-28 21:49 Anthony G. Basile
2020-03-16 21:23 Sergei Trofimovich
2019-11-22  9:54 Mikle Kolyada
2019-11-05  9:27 Agostino Sarubbo
2019-11-05  8:24 Agostino Sarubbo
2019-11-04 17:39 Matt Turner
2019-11-04 17:39 Matt Turner
2019-04-20 18:45 Mikle Kolyada
2019-04-19  0:31 Aaron Bauman
2019-04-18 20:32 Thomas Deutschmann
2019-04-18 11:57 Anthony G. Basile
2019-04-09  3:14 Austin English
2018-10-17  4:07 Anthony G. Basile
2018-04-05  8:09 Fabian Groffen
2018-03-15 13:51 Mikle Kolyada
2017-12-15  8:54 Jason Zaman
2017-12-12 21:59 Austin English
2017-10-22 21:53 Matt Turner
2017-10-22 21:53 Matt Turner
2017-10-22 20:33 Thomas Deutschmann
2017-09-17 11:42 Sergei Trofimovich
2017-09-17 11:42 Sergei Trofimovich
2017-09-17 11:42 Sergei Trofimovich
2017-09-17 11:14 Sergei Trofimovich
2017-08-10 19:10 Austin English
2017-06-18 17:40 Alexis Ballier
2017-06-17 23:25 Anthony G. Basile
2017-06-10 18:12 Anthony G. Basile
2017-06-10 18:12 Anthony G. Basile
2017-04-01 22:23 Anthony G. Basile
2017-03-01  1:08 Austin English
2015-11-23  1:06 Anthony G. Basile
2015-11-23  1:05 Anthony G. Basile

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=1674428833.b9589621d3748e5bb7486ee14d32f87ec7bcc503.sam@gentoo \
    --to=sam@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