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-perl/Crypt-OpenSSL-RSA/
Date: Sat, 24 Dec 2022 07:11:40 +0000 (UTC)	[thread overview]
Message-ID: <1671865511.c03f68eb36b4274adffb9d56deeb004b3951120f.sam@gentoo> (raw)

commit:     c03f68eb36b4274adffb9d56deeb004b3951120f
Author:     James Le Cuirot <chewi <AT> gentoo <DOT> org>
AuthorDate: Mon Nov 14 23:07:25 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Dec 24 07:05:11 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c03f68eb

dev-perl/Crypt-OpenSSL-RSA: Search for OpenSSL in specific location

Crypt-OpenSSL-Guess looks for OpenSSL in a bunch of random places, which
we want to avoid. Specifying it this way also fixes cross-compiling, at
least when combined with other fixes.

Signed-off-by: James Le Cuirot <chewi <AT> gentoo.org>
Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-perl/Crypt-OpenSSL-RSA/Crypt-OpenSSL-RSA-0.330.0.ebuild | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/dev-perl/Crypt-OpenSSL-RSA/Crypt-OpenSSL-RSA-0.330.0.ebuild b/dev-perl/Crypt-OpenSSL-RSA/Crypt-OpenSSL-RSA-0.330.0.ebuild
index 2bdd41f70762..b0fef1547406 100644
--- a/dev-perl/Crypt-OpenSSL-RSA/Crypt-OpenSSL-RSA-0.330.0.ebuild
+++ b/dev-perl/Crypt-OpenSSL-RSA/Crypt-OpenSSL-RSA-0.330.0.ebuild
@@ -37,3 +37,5 @@ PERL_RM_FILES=(
 )
 
 mydoc="rfc*.txt"
+
+export OPENSSL_PREFIX="${ESYSROOT}/usr"


             reply	other threads:[~2022-12-24  7:11 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-24  7:11 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-16 23:18 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Crypt-OpenSSL-RSA/ Sam James
2022-11-16  7:58 Arthur Zamarin
2022-11-15 10:04 Sam James
2022-11-15 10:04 Sam James
2022-11-15  8:46 Sam James
2022-11-15  8:46 Sam James
2022-11-15  8:46 Sam James
2022-11-15  8:46 Sam James
2022-07-09  5:57 Sam James
2021-12-05 20:36 Arthur Zamarin
2021-12-05  3:15 Sam James
2021-12-05  3:15 Sam James
2021-12-05  3:11 Sam James
2021-12-05  3:09 Sam James
2021-12-05  3:08 Sam James
2021-10-16 10:43 Andreas K. Hüttel
2021-10-16 10:43 Andreas K. Hüttel
2021-05-15 18:02 Sam James
2021-05-15  2:37 Sam James
2021-05-14  9:36 Agostino Sarubbo
2021-05-14  9:35 Agostino Sarubbo
2021-05-14  9:32 Agostino Sarubbo
2021-05-14  9:31 Agostino Sarubbo
2021-05-14  6:40 Agostino Sarubbo
2021-05-03 10:21 Mikle Kolyada
2020-12-05  4:20 Kent Fredric
2020-11-28  9:57 Sam James
2020-10-22  5:11 Joshua Kinard
2020-09-26 19:44 Matt Turner
2020-09-03  4:26 Yixun Lan
2020-07-12  0:10 Sam James
2020-07-10 11:16 Sam James
2020-07-09 13:23 Sam James
2020-07-07  6:58 Sergei Trofimovich
2020-07-06 16:43 Sergei Trofimovich
2020-07-05 11:37 Sergei Trofimovich
2020-07-05 11:35 Sergei Trofimovich
2020-07-04  8:56 Sergei Trofimovich
2020-07-01 18:02 Kent Fredric
2019-07-29 18:42 Aaron Bauman
2019-04-01 19:33 Andreas Sturmlechner
2018-10-27 12:31 Fabian Groffen
2018-08-18  5:29 Mikle Kolyada
2018-06-13 16:21 Lars Wendler
2016-08-16  5:05 Kent Fredric
2015-12-30 23:04 Andreas Hüttel
2015-09-20 16:39 Julian Ospald

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=1671865511.c03f68eb36b4274adffb9d56deeb004b3951120f.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