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-libs/libpfm/
Date: Sat, 27 Feb 2021 06:19:46 +0000 (UTC)	[thread overview]
Message-ID: <1614406774.9ee1998062f8e1430de2f47e334edb86e4cfe090.sam@gentoo> (raw)

commit:     9ee1998062f8e1430de2f47e334edb86e4cfe090
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Feb 27 06:15:54 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Feb 27 06:19:34 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9ee19980

dev-libs/libpfm: delete static-libs properly

Closes: https://bugs.gentoo.org/773232
Package-Manager: Portage-3.0.15, Repoman-3.0.2
Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-libs/libpfm/libpfm-4.11.0.ebuild | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/dev-libs/libpfm/libpfm-4.11.0.ebuild b/dev-libs/libpfm/libpfm-4.11.0.ebuild
index 55e05a64d12..b6483a94ff5 100644
--- a/dev-libs/libpfm/libpfm-4.11.0.ebuild
+++ b/dev-libs/libpfm/libpfm-4.11.0.ebuild
@@ -33,6 +33,8 @@ src_install() {
 	dodoc README
 
 	if ! use static-libs ; then
-		find "${ED}" -name '*.la' -delete || die
+		find "${ED}" -name '*.a' -delete || die
 	fi
+
+	find "${ED}" -name '*.la' -delete || die
 }


             reply	other threads:[~2021-02-27  6:19 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-27  6:19 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-10 13:21 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libpfm/ Petr Vaněk
2024-08-24 14:16 Arthur Zamarin
2024-08-24 13:12 Michał Górny
2024-08-24 11:49 Sam James
2024-08-24 11:49 Sam James
2024-08-24 11:08 Arthur Zamarin
2024-08-24 11:08 Arthur Zamarin
2024-06-29 14:09 Arthur Zamarin
2024-05-28  5:15 Sam James
2023-12-30  1:26 Ionen Wolkens
2023-04-05 12:39 Arthur Zamarin
2023-04-04 23:17 Sam James
2023-04-04 22:54 Sam James
2023-04-04 22:42 Sam James
2023-04-04 22:24 Sam James
2023-04-04 19:26 Arthur Zamarin
2023-04-04 19:19 Arthur Zamarin
2023-02-21 16:17 Florian Schmaus
2022-08-13 16:00 WANG Xuerui
2022-08-02 19:50 Arthur Zamarin
2022-04-17 19:00 Sam James
2022-03-20  0:53 Sam James
2022-01-01 15:15 Arthur Zamarin
2021-04-02  8:49 Sergei Trofimovich
2021-03-27 16:04 Sam James
2021-03-27 16:04 Sam James
2021-03-26 18:37 Sam James
2021-03-26 15:54 Agostino Sarubbo
2021-03-26 14:56 Agostino Sarubbo
2021-02-27  1:00 Sam James
2021-02-27  1:00 Sam James
2021-02-27  1:00 Sam James
2021-01-07 19:04 Sam James
2021-01-07 18:57 Sam James
2021-01-04  1:32 Sam James
2021-01-04  1:32 Sam James
2021-01-04  1:32 Sam James
2020-12-18 10:14 Sergei Trofimovich
2020-05-28 15:42 Agostino Sarubbo
2020-05-26 21:56 Sergei Trofimovich
2020-05-26 21:56 Sergei Trofimovich
2019-07-28  9:34 Mikle Kolyada
2019-05-13 17:36 Aaron Bauman
2019-05-13  1:47 Aaron Bauman
2019-05-11 11:25 Mikle Kolyada
2019-05-11 11:25 Mikle Kolyada
2019-04-13  3:08 Aaron Bauman
2018-12-04 22:21 Sergei Trofimovich
2018-12-04 21:44 Sergei Trofimovich
2018-11-18 12:35 Mikle Kolyada
2017-11-13 22:37 Sergei Trofimovich
2016-11-22  6:47 Slawek Lis
2016-05-25  5:59 Jeroen Roovers
2016-05-25  5:36 Jeroen Roovers

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=1614406774.9ee1998062f8e1430de2f47e334edb86e4cfe090.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