From: "Joonas Niilola" <juippis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/keystone/
Date: Wed, 5 Oct 2022 07:16:10 +0000 (UTC) [thread overview]
Message-ID: <1664954153.8ef7e7967be382f393f7e76e098d31ff13e199fc.juippis@gentoo> (raw)
commit: 8ef7e7967be382f393f7e76e098d31ff13e199fc
Author: Mario Haustein <mario.haustein <AT> hrz <DOT> tu-chemnitz <DOT> de>
AuthorDate: Tue Sep 6 06:59:09 2022 +0000
Commit: Joonas Niilola <juippis <AT> gentoo <DOT> org>
CommitDate: Wed Oct 5 07:15:53 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8ef7e796
dev-libs/keystone: explicitly specify python interpreter for cmake
Closes: https://bugs.gentoo.org/867631
Signed-off-by: Mario Haustein <mario.haustein <AT> hrz.tu-chemnitz.de>
Closes: https://github.com/gentoo/gentoo/pull/27161
Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>
dev-libs/keystone/keystone-0.9.2-r1.ebuild | 5 +++++
dev-libs/keystone/keystone-9999.ebuild | 5 +++++
2 files changed, 10 insertions(+)
diff --git a/dev-libs/keystone/keystone-0.9.2-r1.ebuild b/dev-libs/keystone/keystone-0.9.2-r1.ebuild
index 68f71673a12f..a6f8dcdd8897 100644
--- a/dev-libs/keystone/keystone-0.9.2-r1.ebuild
+++ b/dev-libs/keystone/keystone-0.9.2-r1.ebuild
@@ -56,6 +56,10 @@ wrap_python() {
fi
}
+pkg_setup() {
+ python_setup
+}
+
src_prepare() {
default
@@ -73,6 +77,7 @@ src_configure() {
-DBUILD_SHARED_LIBS=ON
-DLLVM_TARGETS_TO_BUILD="${LLVM_TARGETS// /;}"
-DLLVM_HOST_TRIPLE="${CHOST}"
+ -DPYTHON_EXECUTABLE="${PYTHON}"
)
cmake_src_configure
diff --git a/dev-libs/keystone/keystone-9999.ebuild b/dev-libs/keystone/keystone-9999.ebuild
index 68f71673a12f..a6f8dcdd8897 100644
--- a/dev-libs/keystone/keystone-9999.ebuild
+++ b/dev-libs/keystone/keystone-9999.ebuild
@@ -56,6 +56,10 @@ wrap_python() {
fi
}
+pkg_setup() {
+ python_setup
+}
+
src_prepare() {
default
@@ -73,6 +77,7 @@ src_configure() {
-DBUILD_SHARED_LIBS=ON
-DLLVM_TARGETS_TO_BUILD="${LLVM_TARGETS// /;}"
-DLLVM_HOST_TRIPLE="${CHOST}"
+ -DPYTHON_EXECUTABLE="${PYTHON}"
)
cmake_src_configure
next reply other threads:[~2022-10-05 7:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 7:16 Joonas Niilola [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-06 11:10 [gentoo-commits] repo/gentoo:master commit in: dev-libs/keystone/ Sam James
2024-08-06 11:10 Sam James
2024-03-01 3:54 Sam James
2024-02-15 7:07 Joonas Niilola
2024-02-15 7:00 Joonas Niilola
2024-01-08 13:50 Joonas Niilola
2024-01-08 13:50 Joonas Niilola
2023-09-18 7:40 Sam James
2023-04-28 6:31 Sam James
2023-04-28 6:31 Sam James
2023-04-25 21:30 Sam James
2023-04-25 21:30 Sam James
2023-04-25 21:30 Sam James
2023-04-14 4:04 Sam James
2023-01-04 18:36 Arthur Zamarin
2023-01-04 18:36 Arthur Zamarin
2022-08-31 1:24 Sam James
2022-08-13 7:59 Matthew Smith
2022-08-13 7:59 Matthew Smith
2022-08-13 7:59 Matthew Smith
2022-08-13 7:59 Matthew Smith
2022-04-05 3:08 Sam James
2021-11-08 11:25 Michał Górny
2021-09-19 5:36 Sam James
2021-01-01 0:53 Michał Górny
2020-07-16 14:39 Joonas Niilola
2020-06-28 20:51 Aaron Bauman
2020-06-19 1:33 Georgy Yakovlev
2020-06-19 1:33 Georgy Yakovlev
2017-12-16 13:55 Ulrich Müller
2017-12-13 9:03 Patrice Clement
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=1664954153.8ef7e7967be382f393f7e76e098d31ff13e199fc.juippis@gentoo \
--to=juippis@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