From: "Jeroen Roovers" <jer@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/hydra/
Date: Mon, 3 Aug 2020 20:59:25 +0000 (UTC) [thread overview]
Message-ID: <1596488361.c2f2521b07dd0f7ab8a095f5a882f70abd761096.jer@gentoo> (raw)
commit: c2f2521b07dd0f7ab8a095f5a882f70abd761096
Author: Jeroen Roovers <jer <AT> gentoo <DOT> org>
AuthorDate: Mon Aug 3 20:56:25 2020 +0000
Commit: Jeroen Roovers <jer <AT> gentoo <DOT> org>
CommitDate: Mon Aug 3 20:59:21 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c2f2521b
net-analyzer/hydra: Fix USE=-rdp
Version 9.1 added support for libfreerdp3 (which has not yet been
released) so in configure, some variables were renamed to accomodate
that new option, and hydra_sed() needed to be called with that new
variable when disabling RDP support.
Package-Manager: Portage-3.0.1, Repoman-2.3.23
Closes: https://bugs.gentoo.org/735802
Signed-off-by: Jeroen Roovers <jer <AT> gentoo.org>
net-analyzer/hydra/hydra-9.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-analyzer/hydra/hydra-9.1.ebuild b/net-analyzer/hydra/hydra-9.1.ebuild
index 373ae9d6f43..0b2eb5c879d 100644
--- a/net-analyzer/hydra/hydra-9.1.ebuild
+++ b/net-analyzer/hydra/hydra-9.1.ebuild
@@ -94,7 +94,7 @@ src_configure() {
hydra_sed pcre '-lpcre' '$( "${PKG_CONFIG}" --libs libpcre )' '-DHAVE_PCRE'
hydra_sed postgres '-lpq' '$( "${PKG_CONFIG}" --libs libpq )' '-DLIBPOSTGRES'
hydra_sed oracle '-locci -lclntsh' '' '-DLIBORACLE'
- hydra_sed rdp '-lfreerdp2' '$( "${PKG_CONFIG}" --libs freerdp2 )' '-DLIBFREERDP2'
+ hydra_sed rdp '-lfreerdp2' '$( "${PKG_CONFIG}" --libs freerdp2 )' '-DLIBFREERDP'
# TODO: https://bugs.gentoo.org/686148
#hydra_sed subversion '-lsvn_client-1 -lapr-1 -laprutil-1 -lsvn_subr-1' '$( "${PKG_CONFIG}" --libs libsvn_client )' '-DLIBSVN'
hydra_sed subversion '-lsvn_client-1 -lapr-1 -laprutil-1 -lsvn_subr-1' '' '-DLIBSVN'
next reply other threads:[~2020-08-03 20:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 20:59 Jeroen Roovers [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-15 20:25 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/hydra/ Mike Gilbert
2024-03-17 16:35 Mike Gilbert
2024-03-17 16:35 Mike Gilbert
2023-11-04 16:13 Arthur Zamarin
2023-11-04 12:25 Sam James
2022-12-16 7:39 Sam James
2022-04-13 4:55 Sam James
2022-04-13 4:55 Sam James
2022-01-15 21:51 Sam James
2021-05-01 18:19 Agostino Sarubbo
2021-04-30 18:46 Mikle Kolyada
2021-03-26 7:45 Agostino Sarubbo
2021-03-19 2:08 Sam James
2021-03-19 2:00 Sam James
2021-03-15 22:09 Sam James
2021-03-15 21:01 Sam James
2021-03-15 21:01 Sam James
2021-03-15 21:01 Sam James
2021-03-15 21:01 Sam James
2021-01-02 15:45 Andreas K. Hüttel
2020-09-14 19:31 Michał Górny
2020-07-29 9:37 Jeroen Roovers
2020-02-02 22:28 Matt Turner
2020-01-27 14:52 Jeroen Roovers
2019-10-29 16:38 Jeroen Roovers
2019-10-12 10:21 Michał Górny
2019-10-07 4:52 Jeroen Roovers
2019-08-13 6:22 Jeroen Roovers
2019-08-13 6:22 Jeroen Roovers
2019-05-17 16:28 Jeroen Roovers
2019-04-01 8:41 Jeroen Roovers
2019-02-14 20:09 Brian Evans
2017-07-27 13:26 Jeroen Roovers
2017-07-27 13:26 Jeroen Roovers
2017-05-06 9:03 Jeroen Roovers
2017-05-06 8:57 Jeroen Roovers
2017-05-06 8:57 Jeroen Roovers
2016-07-13 17:36 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=1596488361.c2f2521b07dd0f7ab8a095f5a882f70abd761096.jer@gentoo \
--to=jer@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