From: "John Helmert III" <ajak@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/rizin/
Date: Sun, 10 Sep 2023 18:04:08 +0000 (UTC) [thread overview]
Message-ID: <1694369031.4c26f4210350b8ecd4d6369284a7416eb0e1b644.ajak@gentoo> (raw)
commit: 4c26f4210350b8ecd4d6369284a7416eb0e1b644
Author: John Helmert III <ajak <AT> gentoo <DOT> org>
AuthorDate: Sun Sep 10 17:45:38 2023 +0000
Commit: John Helmert III <ajak <AT> gentoo <DOT> org>
CommitDate: Sun Sep 10 18:03:51 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4c26f421
dev-util/rizin: temporarily disable system openssl
There's an upstream bug around using openssl's code paths for the md4
hash tests. Disabling system openssl use makes rizin use its own code
paths rather than a bundled openssl.
Signed-off-by: John Helmert III <ajak <AT> gentoo.org>
dev-util/rizin/rizin-0.6.1.ebuild | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/dev-util/rizin/rizin-0.6.1.ebuild b/dev-util/rizin/rizin-0.6.1.ebuild
index 5c2f92105259..c487f6213887 100644
--- a/dev-util/rizin/rizin-0.6.1.ebuild
+++ b/dev-util/rizin/rizin-0.6.1.ebuild
@@ -77,7 +77,8 @@ src_configure() {
-Duse_sys_lz4=enabled
-Duse_sys_lzma=enabled
-Duse_sys_magic=enabled
- -Duse_sys_openssl=enabled
+ # https://github.com/rizinorg/rizin/issues/3841
+ # -Duse_sys_openssl=enabled
-Duse_sys_tree_sitter=enabled
-Duse_sys_xxhash=enabled
-Duse_sys_zlib=enabled
next reply other threads:[~2023-09-10 18:04 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 18:04 John Helmert III [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-09 2:54 [gentoo-commits] repo/gentoo:master commit in: dev-util/rizin/ John Helmert III
2025-02-01 23:08 John Helmert III
2025-02-01 23:08 John Helmert III
2025-02-01 23:08 John Helmert III
2025-01-20 23:56 John Helmert III
2024-12-15 4:57 John Helmert III
2024-09-02 6:00 John Helmert III
2024-07-28 18:51 John Helmert III
2024-07-28 18:51 John Helmert III
2024-07-28 2:39 Sam James
2024-05-11 19:08 Sam James
2024-04-21 23:33 John Helmert III
2024-04-21 23:33 John Helmert III
2024-04-15 7:25 Matthew Smith
2024-03-04 5:21 John Helmert III
2024-03-04 5:21 John Helmert III
2023-12-15 7:36 Sam James
2023-10-25 18:19 John Helmert III
2023-09-25 4:49 John Helmert III
2023-09-25 4:49 John Helmert III
2023-09-17 0:06 John Helmert III
2023-09-10 18:04 John Helmert III
2023-09-10 18:04 John Helmert III
2023-08-31 4:21 Sam James
2023-08-31 4:21 Sam James
2023-04-30 23:36 John Helmert III
2023-04-30 23:36 John Helmert III
2023-04-19 6:07 Sam James
2023-04-16 18:52 John Helmert III
2023-02-19 16:46 John Helmert III
2023-02-19 0:58 John Helmert III
2022-10-29 21:32 Sam James
2022-09-10 15:29 John Helmert III
2022-09-09 17:24 John Helmert III
2022-09-09 17:24 John Helmert III
2022-07-04 20:01 John Helmert III
2022-07-04 20:01 John Helmert III
2022-05-11 2:11 Sam James
2022-03-02 2:43 John Helmert III
2022-01-10 6:10 John Helmert III
2022-01-09 7:39 John Helmert III
2021-11-20 23:30 John Helmert III
2021-11-20 17:26 John Helmert III
2021-09-09 4:22 Sam James
2021-07-02 5:58 Sergei Trofimovich
2021-06-10 17:51 Sergei Trofimovich
2021-05-15 13:58 Sergei Trofimovich
2021-05-01 20:44 Sergei Trofimovich
2021-04-24 23:11 Sergei Trofimovich
2021-04-24 12:37 Sergei Trofimovich
2021-04-09 9:58 Sergei Trofimovich
2021-04-09 9:52 Sergei Trofimovich
2021-04-08 20:57 John Helmert III
2021-04-06 19:03 Sergei Trofimovich
2021-04-02 9:54 Sergei Trofimovich
2021-03-31 15:42 John Helmert III
2021-03-29 19:35 Sergei Trofimovich
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=1694369031.4c26f4210350b8ecd4d6369284a7416eb0e1b644.ajak@gentoo \
--to=ajak@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