From: "Lars Wendler" <polynomial-c@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/nss-pem/
Date: Thu, 12 Mar 2020 17:04:24 +0000 (UTC) [thread overview]
Message-ID: <1584032657.756e6ca788ec65b8b43ce412b324b27d28a78419.polynomial-c@gentoo> (raw)
commit: 756e6ca788ec65b8b43ce412b324b27d28a78419
Author: Lars Wendler <polynomial-c <AT> gentoo <DOT> org>
AuthorDate: Thu Mar 12 17:02:58 2020 +0000
Commit: Lars Wendler <polynomial-c <AT> gentoo <DOT> org>
CommitDate: Thu Mar 12 17:04:17 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=756e6ca7
dev-libs/nss-pem: Fixed installation in multilib environment
Closes: https://bugs.gentoo.org/712258
Package-Manager: Portage-2.3.93, Repoman-2.3.20
Signed-off-by: Lars Wendler <polynomial-c <AT> gentoo.org>
dev-libs/nss-pem/nss-pem-1.0.5.ebuild | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/dev-libs/nss-pem/nss-pem-1.0.5.ebuild b/dev-libs/nss-pem/nss-pem-1.0.5.ebuild
index 0364f65447a..8c408455b23 100644
--- a/dev-libs/nss-pem/nss-pem-1.0.5.ebuild
+++ b/dev-libs/nss-pem/nss-pem-1.0.5.ebuild
@@ -3,6 +3,8 @@
EAPI=7
+CMAKE_ECLASS="cmake"
+
inherit cmake-multilib
DESCRIPTION="PEM file reader for Network Security Services (NSS)"
@@ -21,3 +23,10 @@ DEPEND="!<=dev-libs/nss-3.50
${RDEPEND}"
S="${WORKDIR}/${P}/src"
+
+multilib_src_configure() {
+ local mycmakeargs=(
+ -DLIB_INSTALL_DIR="$(get_libdir)"
+ )
+ cmake_src_configure
+}
next reply other threads:[~2020-03-12 17:04 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 17:04 Lars Wendler [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-25 15:24 [gentoo-commits] repo/gentoo:master commit in: dev-libs/nss-pem/ Andreas K. Hüttel
2023-03-08 16:25 Joonas Niilola
2023-03-06 13:04 Arthur Zamarin
2023-03-06 12:51 Arthur Zamarin
2023-03-06 12:51 Arthur Zamarin
2023-03-06 12:51 Arthur Zamarin
2023-03-05 16:35 Arthur Zamarin
2023-03-05 7:33 Joonas Niilola
2023-03-05 7:33 Joonas Niilola
2023-02-22 7:14 Joonas Niilola
2023-02-20 8:09 Joonas Niilola
2023-02-04 13:01 Joonas Niilola
2022-10-25 15:15 Joonas Niilola
2022-09-05 16:35 Anthony G. Basile
2022-01-23 7:41 Joonas Niilola
2022-01-18 22:16 Sam James
2022-01-18 22:12 Sam James
2022-01-18 12:26 Sam James
2022-01-15 22:01 Sam James
2022-01-15 22:01 Sam James
2022-01-15 22:01 Sam James
2022-01-15 9:51 Joonas Niilola
2022-01-15 9:51 Joonas Niilola
2021-09-28 21:29 James Le Cuirot
2021-08-24 13:17 Thomas Deutschmann
2021-07-25 3:36 Matt Turner
2021-05-26 12:36 Thomas Deutschmann
2021-03-31 15:25 Sergei Trofimovich
2021-03-31 14:08 Agostino Sarubbo
2021-03-29 14:50 Sam James
2021-03-28 18:20 Sam James
2021-03-28 18:20 Sam James
2021-03-28 18:20 Sam James
2021-03-28 18:18 Sam James
2021-03-28 18:18 Sam James
2021-03-28 6:46 Thomas Deutschmann
2021-02-21 13:10 Fabian Groffen
2021-02-21 9:19 Joshua Kinard
2021-02-21 5:19 Sam James
2021-02-18 7:27 Sam James
2021-02-16 19:17 Sergei Trofimovich
2021-02-16 8:17 Sergei Trofimovich
2021-02-16 8:15 Sergei Trofimovich
2021-02-11 7:36 Sergei Trofimovich
2021-02-09 21:36 Sam James
2021-02-09 14:11 Sergei Trofimovich
2021-02-08 22:18 Thomas Deutschmann
2020-03-10 3:38 Jory Pratt
2020-03-06 14:16 Jory Pratt
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=1584032657.756e6ca788ec65b8b43ce412b324b27d28a78419.polynomial-c@gentoo \
--to=polynomial-c@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