public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/keystone/
Date: Fri, 28 Apr 2023 06:31:23 +0000 (UTC)	[thread overview]
Message-ID: <1682663470.18901e3f2ee71a9050030e33ab9a0913c1d77a2e.sam@gentoo> (raw)

commit:     18901e3f2ee71a9050030e33ab9a0913c1d77a2e
Author:     Mario Haustein <mario.haustein <AT> hrz <DOT> tu-chemnitz <DOT> de>
AuthorDate: Thu Apr 27 21:24:47 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Apr 28 06:31:10 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=18901e3f

dev-libs/keystone: remove llvm.eclass

Signed-off-by: Mario Haustein <mario.haustein <AT> hrz.tu-chemnitz.de>
Closes: https://github.com/gentoo/gentoo/pull/30782
Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-libs/keystone/keystone-0.9.2-r2.ebuild | 2 +-
 dev-libs/keystone/keystone-9999.ebuild     | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-libs/keystone/keystone-0.9.2-r2.ebuild b/dev-libs/keystone/keystone-0.9.2-r2.ebuild
index 7298fa032259..12644c2ca473 100644
--- a/dev-libs/keystone/keystone-0.9.2-r2.ebuild
+++ b/dev-libs/keystone/keystone-0.9.2-r2.ebuild
@@ -8,7 +8,7 @@ DISTUTILS_OPTIONAL=1
 DISTUTILS_USE_PEP517=setuptools
 PYTHON_COMPAT=( python3_{9..11} )
 
-inherit cmake distutils-r1 llvm
+inherit cmake distutils-r1
 
 DESCRIPTION="assembly/assembler framework + bindings"
 HOMEPAGE="https://www.keystone-engine.org/"

diff --git a/dev-libs/keystone/keystone-9999.ebuild b/dev-libs/keystone/keystone-9999.ebuild
index aec73814fd16..8cdc8b7a9bae 100644
--- a/dev-libs/keystone/keystone-9999.ebuild
+++ b/dev-libs/keystone/keystone-9999.ebuild
@@ -8,7 +8,7 @@ DISTUTILS_OPTIONAL=1
 DISTUTILS_USE_PEP517=setuptools
 PYTHON_COMPAT=( python3_{9..11} )
 
-inherit cmake distutils-r1 llvm
+inherit cmake distutils-r1
 
 DESCRIPTION="assembly/assembler framework + bindings"
 HOMEPAGE="https://www.keystone-engine.org/"


             reply	other threads:[~2023-04-28  6:31 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28  6:31 Sam James [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-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-10-05  7:16 Joonas Niilola
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=1682663470.18901e3f2ee71a9050030e33ab9a0913c1d77a2e.sam@gentoo \
    --to=sam@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