From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/ophcrack/
Date: Thu, 2 Jun 2022 03:00:07 +0000 (UTC) [thread overview]
Message-ID: <1654138800.8fbf6d64174136c982cfb0beaeddf07bf255bf61.sam@gentoo> (raw)
commit: 8fbf6d64174136c982cfb0beaeddf07bf255bf61
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Jun 2 02:59:29 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jun 2 03:00:00 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8fbf6d64
app-crypt/ophcrack: fix finding qmake
Closes: https://bugs.gentoo.org/765229
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-crypt/ophcrack/ophcrack-3.8.0.ebuild | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/app-crypt/ophcrack/ophcrack-3.8.0.ebuild b/app-crypt/ophcrack/ophcrack-3.8.0.ebuild
index e6f536daf1ab..c74837410a94 100644
--- a/app-crypt/ophcrack/ophcrack-3.8.0.ebuild
+++ b/app-crypt/ophcrack/ophcrack-3.8.0.ebuild
@@ -1,9 +1,9 @@
-# Copyright 1999-2021 Gentoo Authors
+# Copyright 1999-2022 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=7
-inherit desktop toolchain-funcs
+inherit desktop toolchain-funcs qmake-utils
DESCRIPTION="A time-memory-trade-off-cracker"
HOMEPAGE="https://ophcrack.sourceforge.io/"
@@ -34,6 +34,9 @@ PATCHES=( "${FILESDIR}"/ophcrack-ar.patch )
src_configure() {
tc-export AR
+ # bug #765229
+ export PATH="$(qt5_get_bindir):${PATH}"
+
econf \
$(use_enable debug) \
$(use_enable qt5 gui)
next reply other threads:[~2022-06-02 3:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 3:00 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-02 16:40 [gentoo-commits] repo/gentoo:master commit in: app-crypt/ophcrack/ Mikle Kolyada
2020-12-29 16:46 Mike Auty
2020-11-16 9:53 David Seifert
2018-06-01 19:34 Mike Auty
2018-05-31 22:09 Mike Auty
2018-03-13 9:33 Andreas Sturmlechner
2018-01-18 23:05 Mike Auty
2016-06-03 14:05 Anthony G. Basile
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=1654138800.8fbf6d64174136c982cfb0beaeddf07bf255bf61.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