From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-libs/rocFFT/
Date: Fri, 8 Mar 2024 19:22:51 +0000 (UTC) [thread overview]
Message-ID: <1709925721.58d02b04f88546a40e809b0911e87de092f9ad69.sam@gentoo> (raw)
commit: 58d02b04f88546a40e809b0911e87de092f9ad69
Author: Sv. Lockal <lockalsash <AT> gmail <DOT> com>
AuthorDate: Fri Jan 5 15:33:01 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Mar 8 19:22:01 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=58d02b04
sci-libs/rocFFT: lock dev-util/hip version, as with hip-6.0 build fails with "no member named 'gcnArch'"
Signed-off-by: Sv. Lockal <lockalsash <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>
sci-libs/rocFFT/rocFFT-5.7.1-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sci-libs/rocFFT/rocFFT-5.7.1-r1.ebuild b/sci-libs/rocFFT/rocFFT-5.7.1-r1.ebuild
index 0fba2a7508a3..5da8c917f384 100644
--- a/sci-libs/rocFFT/rocFFT-5.7.1-r1.ebuild
+++ b/sci-libs/rocFFT/rocFFT-5.7.1-r1.ebuild
@@ -29,7 +29,7 @@ perfscripts? (
dev-python/pandas[${PYTHON_USEDEP}] )
${PYTHON_DEPS}"
-DEPEND="dev-util/hip
+DEPEND="=dev-util/hip-5*
${PYTHON_DEPS}"
BDEPEND="
next reply other threads:[~2024-03-08 19:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 19:22 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-04 10:55 [gentoo-commits] repo/gentoo:master commit in: sci-libs/rocFFT/ Patrick Lauer
2025-02-08 10:07 Patrick Lauer
2025-01-26 14:07 Sam James
2025-01-05 21:49 Sam James
2024-09-09 18:20 Sam James
2024-06-26 9:21 Sam James
2024-03-08 19:22 Sam James
2023-11-19 16:32 Benda XU
2023-07-30 4:39 Benda XU
2023-07-30 4:39 Benda XU
2023-07-05 18:15 Craig Andrews
2022-12-19 14:00 Andreas Sturmlechner
2022-08-06 14:23 Benda XU
2022-07-09 6:10 Benda XU
2022-07-09 6:10 Benda XU
2022-07-09 6:10 Benda XU
2022-03-20 8:57 Benda XU
2021-01-24 7:49 Benda XU
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=1709925721.58d02b04f88546a40e809b0911e87de092f9ad69.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