public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "James Le Cuirot" <chewi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-video/ffmpeg-chromium/
Date: Sun,  3 Dec 2023 16:33:25 +0000 (UTC)	[thread overview]
Message-ID: <1701621167.a6d55492eca0425b5bc9750681d00510d809e4ea.chewi@gentoo> (raw)

commit:     a6d55492eca0425b5bc9750681d00510d809e4ea
Author:     James Le Cuirot <chewi <AT> gentoo <DOT> org>
AuthorDate: Sun Dec  3 16:32:47 2023 +0000
Commit:     James Le Cuirot <chewi <AT> gentoo <DOT> org>
CommitDate: Sun Dec  3 16:32:47 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a6d55492

media-video/ffmpeg-chromium: Work around vulkan linking issue with flag

This should be fixed upstream in the next release.

Closes: https://bugs.gentoo.org/918997
Signed-off-by: James Le Cuirot <chewi <AT> gentoo.org>

 media-video/ffmpeg-chromium/ffmpeg-chromium-117.ebuild | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/media-video/ffmpeg-chromium/ffmpeg-chromium-117.ebuild b/media-video/ffmpeg-chromium/ffmpeg-chromium-117.ebuild
index c51a4c4b8b9b..3709cb55e8ee 100644
--- a/media-video/ffmpeg-chromium/ffmpeg-chromium-117.ebuild
+++ b/media-video/ffmpeg-chromium/ffmpeg-chromium-117.ebuild
@@ -137,6 +137,9 @@ src_prepare() {
 src_configure() {
 	local myconf=( )
 
+	# Bug #918997. Will probably be fixed upstream in the next release.
+	use vulkan && append-ldflags -Wl,-z,muldefs
+
 	# bug 842201
 	use ia64 && tc-is-gcc && append-flags \
 		-fno-tree-ccp \


             reply	other threads:[~2023-12-03 16:33 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-03 16:33 James Le Cuirot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-23 16:58 [gentoo-commits] repo/gentoo:master commit in: media-video/ffmpeg-chromium/ Sam James
2024-11-23 16:58 Sam James
2024-11-16 22:08 Matt Jolly
2024-11-12 14:43 Matt Jolly
2024-10-12 11:05 Matt Jolly
2024-09-23  5:31 Matt Jolly
2024-09-21  1:06 Sam James
2024-09-21  1:06 Sam James
2024-09-09 10:43 Matt Jolly
2024-08-22 17:03 Arthur Zamarin
2024-08-22 17:03 Arthur Zamarin
2024-08-01  8:58 Matt Jolly
2024-07-25 22:26 Sam James
2024-07-25 22:25 Jakov Smolić
2024-07-20 14:32 James Le Cuirot
2024-06-19  5:40 Matt Jolly
2024-06-19  5:40 Matt Jolly
2024-06-14 22:05 Sam James
2024-06-13 19:44 Arthur Zamarin
2024-05-28  6:24 Jakov Smolić
2024-05-22 11:40 Michał Górny
2024-05-21  7:19 WANG Xuerui
2024-05-21  7:19 WANG Xuerui
2024-05-21  5:59 Matt Jolly
2024-04-25 21:52 James Le Cuirot
2024-04-25  6:31 Matt Jolly
2024-04-19 10:38 Arthur Zamarin
2024-04-19 10:38 Arthur Zamarin
2024-04-18 15:30 Matt Jolly
2024-04-07 19:20 Arthur Zamarin
2024-04-04  1:17 Sam James
2024-04-03 22:55 Matt Jolly
2024-03-27 23:11 Sam James
2024-03-27 14:34 Matt Jolly
2024-03-27  6:46 Matt Jolly
2024-03-27  6:46 Matt Jolly
2024-03-09 14:13 James Le Cuirot
2024-02-10 17:53 James Le Cuirot
2024-01-24  6:55 Sam James
2024-01-16 21:57 James Le Cuirot
2023-12-23 21:50 James Le Cuirot
2023-12-03 23:20 James Le Cuirot
2023-06-24  2:59 Sam James
2023-06-21  8:27 James Le Cuirot
2023-06-21  8:27 James Le Cuirot
2023-06-10 10:25 Sam James
2023-05-23  2:52 Sam James
2023-05-20 14:24 James Le Cuirot
2023-05-04 21:12 James Le Cuirot
2023-04-30  8:06 James Le Cuirot
2023-02-03 22:33 James Le Cuirot
2023-01-14 10:22 James Le Cuirot
2022-06-11 10:46 James Le Cuirot
2022-05-29  7:33 James Le Cuirot
2022-04-13 21:48 James Le Cuirot
2022-03-23  9:24 James Le Cuirot
2021-12-15 23:41 James Le Cuirot
2021-11-03  9:30 James Le Cuirot
2021-11-03  9:30 James Le Cuirot
2021-10-23  8:12 James Le Cuirot

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=1701621167.a6d55492eca0425b5bc9750681d00510d809e4ea.chewi@gentoo \
    --to=chewi@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