From: "Haelwenn Monnier" <contact@hacktivis.me>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: games-emulation/yuzu/
Date: Mon, 17 Oct 2022 11:26:45 +0000 (UTC) [thread overview]
Message-ID: <1665576155.da38365112232f79c1a79aa00c6bef9fb5936549.lanodan@gentoo> (raw)
commit: da38365112232f79c1a79aa00c6bef9fb5936549
Author: Samuel Bauer <samuel.bauer <AT> yahoo <DOT> fr>
AuthorDate: Wed Oct 12 12:02:35 2022 +0000
Commit: Haelwenn Monnier <contact <AT> hacktivis <DOT> me>
CommitDate: Wed Oct 12 12:02:35 2022 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=da383651
games-emulation/yuzu-9999: app-arch/lz4 detection
Signed-off-by: Samuel Bauer <samuel.bauer <AT> yahoo.fr>
games-emulation/yuzu/yuzu-9999.ebuild | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/games-emulation/yuzu/yuzu-9999.ebuild b/games-emulation/yuzu/yuzu-9999.ebuild
index 7fdca80d6..330329b0d 100644
--- a/games-emulation/yuzu/yuzu-9999.ebuild
+++ b/games-emulation/yuzu/yuzu-9999.ebuild
@@ -107,7 +107,6 @@ src_prepare() {
# Unbundle mbedtls: undefined reference to `mbedtls_cipher_cmac'
sed -i -e '/mbedtls/d' externals/CMakeLists.txt || die
- sed -i -e 's/mbedtls/& mbedcrypto mbedx509/'
sed -i -e 's/mbedtls/& mbedcrypto mbedx509/' \
src/dedicated_room/CMakeLists.txt \
src/core/CMakeLists.txt || die
@@ -140,6 +139,9 @@ src_prepare() {
sed -i -e '/enet/d' externals/CMakeLists.txt || die
sed -i -e '/enet\/enet\.h/{s/"/</;s/"/>/}' src/network/network.cpp || die
+ # LZ4 temporary fix: https://github.com/yuzu-emu/yuzu/pull/9054/commits/a8021f5a18bc5251aef54468fa6033366c6b92d9
+ sed -i 's/lz4::lz4/lz4/' src/common/CMakeLists.txt || die
+
cmake_src_prepare
}
next reply other threads:[~2022-10-17 11:26 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 11:26 Haelwenn Monnier [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-08 7:22 [gentoo-commits] repo/proj/guru:master commit in: games-emulation/yuzu/ Viorel Munteanu
2024-01-04 13:07 David Roman
2024-01-04 13:07 David Roman
2023-09-28 10:01 David Roman
2023-09-03 12:27 Haelwenn Monnier
2023-07-13 9:42 David Roman
2023-07-04 4:53 Viorel Munteanu
2023-07-04 4:53 Viorel Munteanu
2023-06-26 22:01 Haelwenn Monnier
2023-06-15 19:12 Haelwenn Monnier
2023-02-14 12:02 Florian Schmaus
2023-02-14 12:02 Florian Schmaus
2023-02-13 11:28 Andrew Ammerlaan
2023-02-13 11:28 Andrew Ammerlaan
2023-02-06 8:21 Viorel Munteanu
2023-02-06 8:21 Viorel Munteanu
2022-12-20 17:23 Haelwenn Monnier
2022-09-09 20:02 Ronny Gutbrod
2022-09-08 10:24 [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2022-09-08 10:24 ` [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2022-08-11 13:45 Andrew Ammerlaan
2022-08-07 9:13 Haelwenn Monnier
2022-08-07 9:13 Haelwenn Monnier
2022-01-21 9:14 Florian Schmaus
2021-11-08 13:02 Andrew Ammerlaan
2021-08-07 17:48 Florian Schmaus
2021-08-07 17:47 Florian Schmaus
2021-07-13 9:09 Andrew Ammerlaan
2021-06-26 10:53 Haelwenn Monnier
2021-06-06 8:14 Jian Lin
2021-05-25 23:07 Haelwenn Monnier
2021-05-03 16:57 Andrew Ammerlaan
2021-04-30 7:45 Andrew Ammerlaan
2021-04-30 7:45 Andrew Ammerlaan
2021-04-30 7:45 Andrew Ammerlaan
2021-04-29 8:23 Michał Górny
2021-04-29 8:23 Michał Górny
2021-04-29 8:23 Michał Górny
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=1665576155.da38365112232f79c1a79aa00c6bef9fb5936549.lanodan@gentoo \
--to=contact@hacktivis.me \
--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