public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-qt/qttools/
Date: Thu, 03 Apr 2025 09:10:03 +0000 (UTC)	[thread overview]
Message-ID: <1743671383.b1344b7bfd4f1f362c20a98d8c3193eb451aeef3.ionen@gentoo> (raw)

commit:     b1344b7bfd4f1f362c20a98d8c3193eb451aeef3
Author:     Ionen Wolkens <ionen <AT> gentoo <DOT> org>
AuthorDate: Thu Apr  3 08:55:21 2025 +0000
Commit:     Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Thu Apr  3 09:09:43 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b1344b7b

dev-qt/qttools: fix clang detection with libcxx

Happened to notice this while testing 6.9.0 with llvm-musl, and
this been broken since 6.8.3 (with USE=clang) that had the same
change picked to.

CMake Error at cmake/FindWrapLibClang.cmake:72 (find_package):
  find_package called with invalid argument "20.1.1+libcxx"

At first I thought this was caused by our sed, but that specific
line is unmodified and is using ${LLVM_VERSION} which has the
+libcxx bit appended (or at least, it does with llvm:20). This
is Qt's attempt at getting a "matching" version for Clang.

Given we are trying to remove version specifications to let the
eclass pick them instead (will always match), may as well just
remove it as well.

Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>

 dev-qt/qttools/qttools-6.8.3.ebuild    | 3 ++-
 dev-qt/qttools/qttools-6.9.0.ebuild    | 3 ++-
 dev-qt/qttools/qttools-6.9.9999.ebuild | 3 ++-
 dev-qt/qttools/qttools-6.9999.ebuild   | 3 ++-
 4 files changed, 8 insertions(+), 4 deletions(-)

diff --git a/dev-qt/qttools/qttools-6.8.3.ebuild b/dev-qt/qttools/qttools-6.8.3.ebuild
index 52750e2eb0d8..b8a40f8285e6 100644
--- a/dev-qt/qttools/qttools-6.8.3.ebuild
+++ b/dev-qt/qttools/qttools-6.8.3.ebuild
@@ -66,7 +66,8 @@ src_prepare() {
 	qt6-build_src_prepare
 
 	# qttools is picky about clang versions and ignores LLVM_SLOT
-	sed -i '/find_package/s/${VERSION}//' cmake/FindWrapLibClang.cmake || die
+	sed -e '/find_package/s/${\(LLVM_\)*VERSION}//' \
+		-i cmake/FindWrapLibClang.cmake || die
 }
 
 src_configure() {

diff --git a/dev-qt/qttools/qttools-6.9.0.ebuild b/dev-qt/qttools/qttools-6.9.0.ebuild
index 52750e2eb0d8..b8a40f8285e6 100644
--- a/dev-qt/qttools/qttools-6.9.0.ebuild
+++ b/dev-qt/qttools/qttools-6.9.0.ebuild
@@ -66,7 +66,8 @@ src_prepare() {
 	qt6-build_src_prepare
 
 	# qttools is picky about clang versions and ignores LLVM_SLOT
-	sed -i '/find_package/s/${VERSION}//' cmake/FindWrapLibClang.cmake || die
+	sed -e '/find_package/s/${\(LLVM_\)*VERSION}//' \
+		-i cmake/FindWrapLibClang.cmake || die
 }
 
 src_configure() {

diff --git a/dev-qt/qttools/qttools-6.9.9999.ebuild b/dev-qt/qttools/qttools-6.9.9999.ebuild
index 52750e2eb0d8..b8a40f8285e6 100644
--- a/dev-qt/qttools/qttools-6.9.9999.ebuild
+++ b/dev-qt/qttools/qttools-6.9.9999.ebuild
@@ -66,7 +66,8 @@ src_prepare() {
 	qt6-build_src_prepare
 
 	# qttools is picky about clang versions and ignores LLVM_SLOT
-	sed -i '/find_package/s/${VERSION}//' cmake/FindWrapLibClang.cmake || die
+	sed -e '/find_package/s/${\(LLVM_\)*VERSION}//' \
+		-i cmake/FindWrapLibClang.cmake || die
 }
 
 src_configure() {

diff --git a/dev-qt/qttools/qttools-6.9999.ebuild b/dev-qt/qttools/qttools-6.9999.ebuild
index 52750e2eb0d8..b8a40f8285e6 100644
--- a/dev-qt/qttools/qttools-6.9999.ebuild
+++ b/dev-qt/qttools/qttools-6.9999.ebuild
@@ -66,7 +66,8 @@ src_prepare() {
 	qt6-build_src_prepare
 
 	# qttools is picky about clang versions and ignores LLVM_SLOT
-	sed -i '/find_package/s/${VERSION}//' cmake/FindWrapLibClang.cmake || die
+	sed -e '/find_package/s/${\(LLVM_\)*VERSION}//' \
+		-i cmake/FindWrapLibClang.cmake || die
 }
 
 src_configure() {


             reply	other threads:[~2025-04-03  9:10 UTC|newest]

Thread overview: 107+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-03  9:10 Ionen Wolkens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-03 15:08 [gentoo-commits] repo/gentoo:master commit in: dev-qt/qttools/ Arthur Zamarin
2025-04-16 11:18 Arthur Zamarin
2025-04-15 10:22 Sam James
2025-04-02  5:08 Ionen Wolkens
2025-03-26 12:29 Ionen Wolkens
2025-03-20 22:56 Ionen Wolkens
2025-03-14  8:18 Ionen Wolkens
2025-03-13 11:57 Ionen Wolkens
2025-03-13 11:54 Ionen Wolkens
2025-03-06  9:20 Ionen Wolkens
2025-02-22 14:46 Arthur Zamarin
2025-01-06 22:51 Ionen Wolkens
2025-01-06  7:05 Ionen Wolkens
2024-12-27 21:01 Ionen Wolkens
2024-12-27 12:02 Sam James
2024-12-27  1:54 Sam James
2024-12-25 22:40 Sam James
2024-12-18  4:37 Ionen Wolkens
2024-12-15 20:18 Ionen Wolkens
2024-12-03 18:16 Ionen Wolkens
2024-12-02  7:23 Ionen Wolkens
2024-11-13 10:04 Ionen Wolkens
2024-11-02 14:10 Arthur Zamarin
2024-11-01  6:35 Arthur Zamarin
2024-10-09  6:22 Ionen Wolkens
2024-10-08  5:03 Ionen Wolkens
2024-09-27  7:26 Ionen Wolkens
2024-09-24  9:57 Ionen Wolkens
2024-09-03  7:44 Ionen Wolkens
2024-09-02 17:52 Ionen Wolkens
2024-07-16  1:29 Ionen Wolkens
2024-07-08 16:40 Arthur Zamarin
2024-07-08 11:16 Arthur Zamarin
2024-07-08 10:09 Sam James
2024-06-18 18:14 Ionen Wolkens
2024-06-08 13:41 Ionen Wolkens
2024-06-08  5:27 Arthur Zamarin
2024-06-04 19:36 Ionen Wolkens
2024-06-02  4:04 Sam James
2024-05-28 18:56 Arthur Zamarin
2024-05-20  8:48 Ionen Wolkens
2024-04-20 14:20 Ionen Wolkens
2024-04-19  7:55 Ionen Wolkens
2024-04-13 17:50 Arthur Zamarin
2024-04-02 13:06 Ionen Wolkens
2024-04-02  6:09 Arthur Zamarin
2024-04-01 18:29 Arthur Zamarin
2024-03-30  0:29 Ionen Wolkens
2024-03-26  7:10 Ionen Wolkens
2024-03-25 22:10 Ionen Wolkens
2024-03-24 18:39 Ionen Wolkens
2024-03-22 10:29 Ionen Wolkens
2024-03-22  6:16 Arthur Zamarin
2024-03-12 12:01 Ionen Wolkens
2024-03-07 20:46 Ionen Wolkens
2024-02-22  6:16 Ionen Wolkens
2024-02-20 14:30 Arthur Zamarin
2024-02-14 12:24 Ionen Wolkens
2024-02-10 11:26 Ionen Wolkens
2023-12-19 20:33 Ionen Wolkens
2023-12-19 15:15 Ionen Wolkens
2023-12-17 18:29 Arthur Zamarin
2023-12-12 21:25 Ionen Wolkens
2023-12-01 19:48 Jakov Smolić
2023-12-01  6:21 Sam James
2023-12-01  6:21 Sam James
2023-11-29 22:33 Sam James
2023-11-27  8:47 Ionen Wolkens
2023-11-15 19:28 Ionen Wolkens
2023-11-15 17:20 Arthur Zamarin
2023-10-22  5:55 Ionen Wolkens
2023-10-10 14:51 Ionen Wolkens
2023-09-29 23:29 Ionen Wolkens
2023-09-28 13:07 Ionen Wolkens
2023-09-27 10:03 Ionen Wolkens
2023-09-26 23:08 Ionen Wolkens
2023-09-26 19:48 Ionen Wolkens
2023-09-24 17:22 Ionen Wolkens
2023-09-24 17:09 WANG Xuerui
2023-09-24 17:09 WANG Xuerui
2023-09-22 20:53 Sam James
2023-09-15  4:49 Sam James
2023-09-13 16:42 Ionen Wolkens
2023-09-13 16:42 Ionen Wolkens
2023-09-12  1:28 Sam James
2023-09-12  1:26 Sam James
2023-09-11 22:59 Sam James
2023-09-11 21:20 Ionen Wolkens
2023-09-11 21:20 Ionen Wolkens
2023-09-11 21:20 Ionen Wolkens
2023-09-06  8:49 Ionen Wolkens
2023-09-05 13:05 Ionen Wolkens
2023-07-26 13:31 Jimi Huotari
2023-07-20 19:41 Jimi Huotari
2023-06-10 13:33 Jimi Huotari
2023-05-06 11:26 Jimi Huotari
2023-04-15 18:39 Jimi Huotari
2023-03-26 16:59 Jimi Huotari
2023-03-19 13:09 Jimi Huotari
2023-02-09 10:02 Andreas Sturmlechner
2023-01-05 22:39 Jimi Huotari
2022-12-01 19:19 Andreas Sturmlechner
2022-09-24 14:32 Andreas Sturmlechner
2022-09-24 14:32 Andreas Sturmlechner
2022-08-02 22:00 Sam James
2022-08-02 21:51 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=1743671383.b1344b7bfd4f1f362c20a98d8c3193eb451aeef3.ionen@gentoo \
    --to=ionen@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