From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/rasqal/
Date: Sun, 14 Sep 2025 10:37:17 +0000 (UTC)	[thread overview]
Message-ID: <1757846094.ad730e7afc99cf9e8ee7645d12bc7cb8c6239fb0.sam@gentoo> (raw)
commit:     ad730e7afc99cf9e8ee7645d12bc7cb8c6239fb0
Author:     Holger Hoffstätte <holger <AT> applied-asynchrony <DOT> com>
AuthorDate: Fri Sep 12 16:36:50 2025 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Sep 14 10:34:54 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ad730e7a
dev-libs/rasqal: fix build with USE=pcre when old libpcre is not installed
The previously committed upstream patch for libpcre2 support has some
dodgy behaviour wrt. the --enable-pcre flag. Instead we can let configure
autodetect whatever it finds and then select the library we want
(libpcre2 or posix) depending on USE.
Also properly depend on libcre2 subslot.
Closes: https://bugs.gentoo.org/962785
Signed-off-by: Holger Hoffstätte <holger <AT> applied-asynchrony.com>
Part-of: https://github.com/gentoo/gentoo/pull/43756
Closes: https://github.com/gentoo/gentoo/pull/43756
Signed-off-by: Sam James <sam <AT> gentoo.org>
 dev-libs/rasqal/rasqal-0.9.33-r5.ebuild | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/dev-libs/rasqal/rasqal-0.9.33-r5.ebuild b/dev-libs/rasqal/rasqal-0.9.33-r5.ebuild
index ddecc6b530dd..74230e78171a 100644
--- a/dev-libs/rasqal/rasqal-0.9.33-r5.ebuild
+++ b/dev-libs/rasqal/rasqal-0.9.33-r5.ebuild
@@ -24,7 +24,7 @@ RDEPEND="
 	!gmp? ( dev-libs/mpfr:= )
 	gmp? ( dev-libs/gmp:= )
 	kernel_linux? ( >=sys-apps/util-linux-2.19 )
-	pcre? ( dev-libs/libpcre2 )
+	pcre? ( dev-libs/libpcre2:= )
 	xml? ( dev-libs/libxml2:= )
 "
 DEPEND="${RDEPEND}"
@@ -58,7 +58,6 @@ src_configure() {
 	local myeconfargs=(
 		--with-decimal=$(usex gmp gmp mpfr)
 		--with-uuid-library=$(usex kernel_linux libuuid internal)
-		$(use_enable pcre)
 		--with-regex-library=$(usex pcre pcre2 posix)
 		$(use_enable static-libs static)
 		$(use_enable xml xml2)
next             reply	other threads:[~2025-09-14 10:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-14 10:37 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-27 10:45 [gentoo-commits] repo/gentoo:master commit in: dev-libs/rasqal/ Miroslav Šulc
2024-02-24  2:44 Ionen Wolkens
2024-02-08 10:21 Arthur Zamarin
2024-02-08 10:21 Arthur Zamarin
2024-02-08 10:21 Arthur Zamarin
2024-02-08 10:21 Arthur Zamarin
2024-02-08 10:21 Arthur Zamarin
2023-07-04 22:17 Conrad Kostecki
2022-09-26 16:11 Sam James
2022-08-12 12:26 WANG Xuerui
2021-12-13  5:54 Yixun Lan
2020-07-23  8:04 Kent Fredric
2019-05-21 22:43 Aaron Bauman
2018-12-22 11:43 Andreas Sturmlechner
2018-12-19 22:48 Sergei Trofimovich
2018-12-01 14:51 Sergei Trofimovich
2018-11-28 12:15 Tobias Klausmann
2018-11-19  7:21 Mikle Kolyada
2018-11-08 12:29 Andreas Sturmlechner
2018-11-07 23:44 Thomas Deutschmann
2018-11-06  7:15 Mikle Kolyada
2018-11-05 19:43 Sergei Trofimovich
2018-10-04  7:28 Andreas Sturmlechner
2018-10-03 22:58 Andreas Sturmlechner
2018-10-03 22:58 Andreas Sturmlechner
2017-08-27 15:34 Michael Palimaka
2017-01-29 16:19 Fabian Groffen
2016-07-24 17:08 Jeroen Roovers
2016-07-24 16:03 Jeroen Roovers
2016-06-08 20:13 Markus Meier
2016-06-06 16:15 Agostino Sarubbo
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=1757846094.ad730e7afc99cf9e8ee7645d12bc7cb8c6239fb0.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