public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Haelwenn Monnier" <contact@hacktivis.me>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: dev-libs/open62541/
Date: Sat,  4 Apr 2020 21:18:12 +0000 (UTC)	[thread overview]
Message-ID: <1586001929.c8f197574898a17259220d41337ed321d1ba95bb.lanodan@gentoo> (raw)

commit:     c8f197574898a17259220d41337ed321d1ba95bb
Author:     Kurt Kanzenbach <kurt <AT> kmk-computers <DOT> de>
AuthorDate: Sat Apr  4 12:05:25 2020 +0000
Commit:     Haelwenn Monnier <contact <AT> hacktivis <DOT> me>
CommitDate: Sat Apr  4 12:05:29 2020 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=c8f19757

dev-libs/open62541: Fix tests and encryption support

There are two problems:

 * Tests need valgrind
 * Typo for enabling/disabling encryption

Fix it.

Package-Manager: Portage-2.3.89, Repoman-2.3.20
Signed-off-by: Kurt Kanzenbach <kurt <AT> kmk-computers.de>

 dev-libs/open62541/open62541-1.0.1.ebuild | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/dev-libs/open62541/open62541-1.0.1.ebuild b/dev-libs/open62541/open62541-1.0.1.ebuild
index d11f16a..d461b63 100644
--- a/dev-libs/open62541/open62541-1.0.1.ebuild
+++ b/dev-libs/open62541/open62541-1.0.1.ebuild
@@ -31,6 +31,7 @@ BDEPEND="
 	)
 	test? (
 		dev-libs/check
+		dev-util/valgrind
 		$(python_gen_cond_dep '
 			dev-python/subunit[${PYTHON_MULTI_USEDEP}]
 		')
@@ -53,7 +54,7 @@ src_configure() {
 		-DUA_BUILD_EXAMPLES=OFF
 		-DUA_BUILD_TOOLS=$(usex tools)
 		-DUA_BUILD_UNIT_TESTS=$(usex test)
-		-UUA_ENABLE_ENCRYPTION=$(usex mbedtls)
+		-DUA_ENABLE_ENCRYPTION=$(usex mbedtls)
 		-DUA_ENABLE_PUBSUB=$(usex pubsub)
 	)
 


             reply	other threads:[~2020-04-04 21:18 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-04 21:18 Haelwenn Monnier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-05-01  9:59 [gentoo-commits] repo/proj/guru:master commit in: dev-libs/open62541/ Andrew Ammerlaan
2020-05-01  9:59 Andrew Ammerlaan
2020-05-31 17:00 Andrew Ammerlaan
2021-04-08 17:21 Andrew Ammerlaan
2022-08-24 15:52 Ronny Gutbrod
2023-05-19 18:51 Viorel Munteanu
2023-05-19 18:51 Viorel Munteanu
2023-09-24  0:33 David Roman
2023-09-24  0:33 David Roman
2023-09-24  0:33 David Roman
2023-10-15 22:23 Haelwenn Monnier
2023-10-15 22:23 Haelwenn Monnier
2023-12-21  6:32 Viorel Munteanu
2023-12-21  6:32 Viorel Munteanu
2024-04-14 15:13 Julien Roy
2024-06-04 12:26 David Roman
2024-06-04 12:26 David Roman
2024-07-14 17:47 Florian Schmaus
2024-07-14 17:47 Florian Schmaus
2024-07-25 10:10 David Roman
2024-07-25 10:10 David Roman
2024-08-07 10:33 Lucio Sauer
2024-08-07 10:33 Lucio Sauer
2024-09-08 16:32 David Roman
2024-09-08 16:32 David Roman
2024-10-08 10:23 David Roman
2024-10-08 10:23 David Roman
2024-10-12 18:59 David Roman
2024-10-12 18:59 David Roman
2024-12-02 10:48 David Roman
2024-12-02 10:48 David Roman
2025-02-06  9:25 David Roman
2025-02-06  9:25 David Roman
2025-02-18 14:01 David Roman
2025-02-18 14:01 David Roman
2025-02-21 12:04 David Roman

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=1586001929.c8f197574898a17259220d41337ed321d1ba95bb.lanodan@gentoo \
    --to=contact@hacktivis.me \
    --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