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-libs/hyperscan/
Date: Thu, 25 Feb 2021 09:11:44 +0000 (UTC)	[thread overview]
Message-ID: <1614243809.70163d5941c2ea2911a3a0f5d16a31306cc6df0f.sam@gentoo> (raw)

commit:     70163d5941c2ea2911a3a0f5d16a31306cc6df0f
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Feb 25 09:03:29 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Feb 25 09:03:29 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=70163d59

dev-libs/hyperscan: restore CMAKE_BUILD_TYPE="Release" for now

Bug: https://bugs.gentoo.org/772086
Package-Manager: Portage-3.0.15, Repoman-3.0.2
Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-libs/hyperscan/hyperscan-5.4.0.ebuild | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/dev-libs/hyperscan/hyperscan-5.4.0.ebuild b/dev-libs/hyperscan/hyperscan-5.4.0.ebuild
index f5eac0bc20f..6303beabeee 100644
--- a/dev-libs/hyperscan/hyperscan-5.4.0.ebuild
+++ b/dev-libs/hyperscan/hyperscan-5.4.0.ebuild
@@ -38,6 +38,9 @@ src_configure() {
 	use cpu_flags_x86_ssse3 && append-flags -mssse3
 	use cpu_flags_x86_avx2  && append-flags -mavx2
 
+	# Temporary, see #772086#c1 and associated PR
+	CMAKE_BUILD_TYPE="Release"
+
 	local mycmakeargs=(
 		-DBUILD_SHARED_LIBS=$(usex static-libs OFF ON)
 		-DBUILD_STATIC_AND_SHARED=$(usex static-libs ON OFF)


             reply	other threads:[~2021-02-25  9:11 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25  9:11 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-29 21:16 [gentoo-commits] repo/gentoo:master commit in: dev-libs/hyperscan/ Petr Vaněk
2023-05-29 10:59 Andreas Sturmlechner
2023-05-27  6:42 Joonas Niilola
2023-05-27  6:42 Joonas Niilola
2023-04-29  6:44 Sam James
2023-03-19 21:21 Sam James
2023-02-28 14:35 Joonas Niilola
2023-02-22 16:16 Sam James
2022-08-27 11:38 Sam James
2022-07-09  7:49 Sam James
2022-02-10 20:12 Jonas Stein
2022-02-05 19:03 Arthur Zamarin
2021-09-03 12:15 Marek Szuba
2021-03-30 13:03 Joonas Niilola
2021-03-25 14:39 Sam James
2021-02-26 20:58 Agostino Sarubbo
2021-01-14  1:20 Sam James
2021-01-14  1:20 Sam James
2021-01-04 15:32 Sam James
2020-09-05 15:16 Sam James
2020-06-10 14:25 Joonas Niilola
2020-06-10 14:25 Joonas Niilola
2020-04-04  7:39 Joonas Niilola
2020-04-04  7:39 Joonas Niilola
2020-04-04  7:39 Joonas Niilola
2020-02-07  6:16 Joonas Niilola
2020-02-07  6:16 Joonas Niilola
2019-10-08 14:35 Alexey Shvetsov
2019-10-08 14:35 Alexey Shvetsov
2019-10-07  7:32 Alexey Shvetsov
2019-10-06 13:45 Alexey Shvetsov
2019-08-12 19:52 Michał Górny
2019-08-12 19:47 Michał Górny
2019-02-22 20:51 Andreas Sturmlechner
2018-03-21  9:24 Dirkjan Ochtman
2018-03-21  9:24 Dirkjan Ochtman
2017-10-29 19:33 Dirkjan Ochtman
2017-07-26 13:18 Dirkjan Ochtman
2017-05-30 15:34 Lars Wendler
2017-04-26 18:43 Dirkjan Ochtman
2017-04-26  8:14 Michał Górny
2017-04-26  5:08 Mike Gilbert
2017-04-25 19:29 Dirkjan Ochtman
2017-04-22  9:55 Dirkjan Ochtman
2017-04-22  9:55 Dirkjan Ochtman
2017-04-22  9:55 Dirkjan Ochtman

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=1614243809.70163d5941c2ea2911a3a0f5d16a31306cc6df0f.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