From: "Guilherme Amadio" <amadio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/rocksdb/
Date: Tue, 14 Nov 2023 15:23:59 +0000 (UTC) [thread overview]
Message-ID: <1699975363.279f528803f03f27f70c255d38e8cec0f84215ea.amadio@gentoo> (raw)
commit: 279f528803f03f27f70c255d38e8cec0f84215ea
Author: Guilherme Amadio <amadio <AT> gentoo <DOT> org>
AuthorDate: Tue Nov 14 15:22:03 2023 +0000
Commit: Guilherme Amadio <amadio <AT> gentoo <DOT> org>
CommitDate: Tue Nov 14 15:22:43 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=279f5288
dev-libs/rocksdb: fix detection of liburing
Signed-off-by: Guilherme Amadio <amadio <AT> gentoo.org>
dev-libs/rocksdb/rocksdb-7.9.2-r1.ebuild | 1 +
dev-libs/rocksdb/rocksdb-8.6.7.ebuild | 1 +
2 files changed, 2 insertions(+)
diff --git a/dev-libs/rocksdb/rocksdb-7.9.2-r1.ebuild b/dev-libs/rocksdb/rocksdb-7.9.2-r1.ebuild
index 843cd318edfb..8ea5722d7228 100644
--- a/dev-libs/rocksdb/rocksdb-7.9.2-r1.ebuild
+++ b/dev-libs/rocksdb/rocksdb-7.9.2-r1.ebuild
@@ -35,6 +35,7 @@ PATCHES=(
)
src_prepare() {
+ sed -i -e 's/liburing.a/uring/' cmake/modules/Finduring.cmake || die
sed -i -e '/find_program(CCACHE_FOUND ccache)/d' CMakeLists.txt || die
cmake_src_prepare
}
diff --git a/dev-libs/rocksdb/rocksdb-8.6.7.ebuild b/dev-libs/rocksdb/rocksdb-8.6.7.ebuild
index ca3ef0a98c1a..283a918f7c75 100644
--- a/dev-libs/rocksdb/rocksdb-8.6.7.ebuild
+++ b/dev-libs/rocksdb/rocksdb-8.6.7.ebuild
@@ -31,6 +31,7 @@ DEPEND="
RDEPEND="${DEPEND}"
src_prepare() {
+ sed -i -e 's/liburing.a/uring/' cmake/modules/Finduring.cmake || die
sed -i -e '/find_program(CCACHE_FOUND ccache)/d' CMakeLists.txt || die
cmake_src_prepare
}
next reply other threads:[~2023-11-14 15:24 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 15:23 Guilherme Amadio [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-02 12:58 [gentoo-commits] repo/gentoo:master commit in: dev-libs/rocksdb/ Guilherme Amadio
2025-02-02 12:53 Guilherme Amadio
2025-02-02 12:53 Guilherme Amadio
2025-02-02 12:53 Guilherme Amadio
2024-12-28 14:04 Arthur Zamarin
2024-12-18 14:33 Guilherme Amadio
2024-12-06 9:27 Guilherme Amadio
2024-11-24 11:02 Sam James
2024-11-24 11:02 Sam James
2024-11-11 16:15 Guilherme Amadio
2024-11-11 16:15 Guilherme Amadio
2024-11-11 16:15 Guilherme Amadio
2024-10-25 21:42 Sam James
2024-08-12 9:51 Guilherme Amadio
2024-07-03 12:55 Guilherme Amadio
2024-03-10 22:04 Guilherme Amadio
2024-03-10 22:04 Guilherme Amadio
2024-01-29 10:38 Guilherme Amadio
2024-01-03 18:52 Arthur Zamarin
2023-12-13 14:39 Guilherme Amadio
2023-11-14 15:13 Guilherme Amadio
2023-11-14 15:13 Guilherme Amadio
2023-11-14 15:13 Guilherme Amadio
2023-11-14 15:13 Guilherme Amadio
2023-11-14 15:13 Guilherme Amadio
2023-04-30 6:38 Sam James
2023-03-13 21:56 Sam James
2023-02-12 3:47 Sam James
2023-01-27 5:26 Sam James
2022-03-19 4:15 Yixun Lan
2021-08-23 17:01 Marek Szuba
2021-03-21 3:07 Patrick McLean
2021-02-26 0:44 Patrick McLean
2021-01-21 23:03 Patrick McLean
2021-01-04 22:15 Patrick McLean
2021-01-04 21:43 Patrick McLean
2021-01-01 23:00 Sam James
2020-12-02 0:17 Patrick McLean
2020-11-26 17:25 Sam James
2020-11-20 22:26 Sam James
2020-11-19 7:29 Patrick McLean
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=1699975363.279f528803f03f27f70c255d38e8cec0f84215ea.amadio@gentoo \
--to=amadio@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