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: media-libs/osl/
Date: Wed,  1 Dec 2021 19:35:45 +0000 (UTC)	[thread overview]
Message-ID: <1638387337.4b89d007ec8f092429d9c69fa7a1de89b29525c0.sam@gentoo> (raw)

commit:     4b89d007ec8f092429d9c69fa7a1de89b29525c0
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Dec  1 19:35:13 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Dec  1 19:35:37 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4b89d007

media-libs/osl: drop tests CMake option

We're not running them for now & they're broken anyway.

(Not sure how I didn't notice this earlier?!)

Closes: https://bugs.gentoo.org/827949
Signed-off-by: Sam James <sam <AT> gentoo.org>

 media-libs/osl/osl-1.11.16.0.ebuild | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/media-libs/osl/osl-1.11.16.0.ebuild b/media-libs/osl/osl-1.11.16.0.ebuild
index fca8230620e4..210576bec26a 100644
--- a/media-libs/osl/osl-1.11.16.0.ebuild
+++ b/media-libs/osl/osl-1.11.16.0.ebuild
@@ -91,7 +91,8 @@ src_configure() {
 		-DUSE_CCACHE=OFF
 		-DLLVM_STATIC=OFF
 		-DLLVM_ROOT="$(get_llvm_prefix ${LLVM_MAX_SLOT})"
-		-DOSL_BUILD_TESTS=$(usex test)
+		# Breaks build for now: bug #827949
+		#-DOSL_BUILD_TESTS=$(usex test)
 		-DOSL_SHADER_INSTALL_DIR="${EPREFIX}/usr/include/${PN^^}/shaders"
 		-DOSL_PTX_INSTALL_DIR="${EPREFIX}/usr/include/${PN^^}/ptx"
 		-DSTOP_ON_WARNING=OFF


             reply	other threads:[~2021-12-01 19:35 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01 19:35 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-01 16:59 [gentoo-commits] repo/gentoo:master commit in: media-libs/osl/ Sam James
2025-04-22  0:41 Sam James
2025-04-22  0:41 Sam James
2025-01-13 17:12 Andreas Sturmlechner
2025-01-13  6:54 Joonas Niilola
2025-01-09 23:05 Sam James
2025-01-09 23:05 Sam James
2025-01-09 23:05 Sam James
2025-01-09 23:05 Sam James
2025-01-05 20:35 Sam James
2025-01-05 20:35 Sam James
2024-10-04 21:40 Andreas Sturmlechner
2024-07-15 11:27 Joonas Niilola
2024-06-29 16:51 Sam James
2024-06-29 16:51 Sam James
2024-06-02  4:12 Sam James
2024-05-03  3:33 Sam James
2024-05-03  3:33 Sam James
2024-04-10  6:24 Joonas Niilola
2024-01-10 12:41 Sam James
2023-07-16 18:46 Sam James
2023-06-10 20:47 Andreas Sturmlechner
2023-05-01 15:15 Sam James
2022-12-24 14:06 Andreas Sturmlechner
2022-12-14  5:19 Sam James
2022-11-03  6:15 Sam James
2022-10-02  2:26 Sam James
2022-10-02  2:26 Sam James
2022-07-09  5:57 Sam James
2022-06-06  1:40 Sam James
2022-05-20 13:21 Joonas Niilola
2022-03-19 23:39 Sam James
2022-02-28  5:21 Sam James
2022-02-19 19:41 Sam James
2022-02-14  2:07 Sam James
2022-02-14  2:07 Sam James
2022-02-12  4:43 Sam James
2022-02-12  3:55 Sam James
2022-02-12  3:55 Sam James
2022-02-12  3:55 Sam James
2021-12-02  3:53 Sam James
2021-12-02  3:50 Sam James
2021-12-01 17:03 Sam James
2021-11-02 20:29 Sam James
2021-11-02 20:29 Sam James
2021-10-04  0:21 Sam James
2021-10-04  0:12 Sam James
2021-10-04  0:08 Sam James
2021-09-19  5:24 Sam James
2021-09-19  5:20 Sam James
2021-09-19  5:20 Sam James
2021-09-19  3:30 Sam James
2021-09-19  3:09 Sam James
2021-09-19  3:09 Sam James
2021-03-05 18:39 Sam James
2021-02-22  7:12 Sam James
2020-12-11  7:58 Joonas Niilola
2020-12-11  7:58 Joonas Niilola
2020-12-01 11:24 Joonas Niilola
2020-12-01 11:24 Joonas Niilola
2020-07-30 22:07 Sam James
2020-06-10  7:32 Michał Górny
2020-03-22 18:02 Mikle Kolyada
2020-03-22 14:40 Andreas Sturmlechner
2019-07-15 13:36 Michał Górny
2018-08-15 20:08 Jonathan Scruggs
2018-03-30 16:04 Aaron Bauman
2018-01-30 21:01 Jonathan Scruggs
2018-01-27 17:19 Jonathan Scruggs
2018-01-12 21:07 Craig Andrews

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=1638387337.4b89d007ec8f092429d9c69fa7a1de89b29525c0.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