From: "Georgy Yakovlev" <gyakovlev@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libdispatch/
Date: Mon, 3 Apr 2023 20:16:52 +0000 (UTC) [thread overview]
Message-ID: <1680552751.102d9b22dc3c74927226fe3fa7b3a39eb4b1a012.gyakovlev@gentoo> (raw)
commit: 102d9b22dc3c74927226fe3fa7b3a39eb4b1a012
Author: Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 3 20:12:31 2023 +0000
Commit: Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
CommitDate: Mon Apr 3 20:12:31 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=102d9b22
dev-libs/libdispatch: add USE=test
build system unconditionally was evaluating BUILD_TESTING as true
this leads to build failures in one of the test deps on some arches.
/usr/bin/powerpc64le-unknown-linux-gnu-ld.bfd: tests/libbsdtests.a(bsdtests.c.o): in function `test_ptr_null_format':
bsdtests.c:(.text+0x1d8): undefined reference to `vsnprintf.inline'
/usr/bin/powerpc64le-unknown-linux-gnu-ld.bfd: tests/libbsdtests.a(bsdtests.c.o): in function `test_ptr_notnull_format':
bsdtests.c:(.text+0x478): undefined reference to `vsnprintf.inline'
/usr/bin/powerpc64le-unknown-linux-gnu-ld.bfd: tests/libbsdtests.a(bsdtests.c.o): in function `test_ptr_format':
bsdtests.c:(.text+0x72c): undefined reference to `vsnprintf.inline'
/usr/bin/powerpc64le-unknown-linux-gnu-ld.bfd: tests/libbsdtests.a(bsdtests.c.o): in function `test_ptr_not_format':
bsdtests.c:(.text+0x9dc): undefined reference to `vsnprintf.inline'
/usr/bin/powerpc64le-unknown-linux-gnu-ld.bfd: tests/libbsdtests.a(bsdtests.c.o): in function `test_uint32_format':
bsdtests.c:(.text+0xc8c): undefined reference to `vsnprintf.inline'
/usr/bin/powerpc64le-unknown-linux-gnu-ld.bfd: tests/libbsdtests.a(bsdtests.c.o):bsdtests.c:(.text+0xf3c): more undefined references to `vsnprintf.inline' follow
explicitly passing -DBUILD_TESTINF=OFF allows to skip building and
linking offending test.
Library works well on ppc64le, just the test does not build with 128bit
ieee-long-double toolchain due to old headers somewhere in test deps.
The actual falure will still be visible with FEATURES="test"
but only on ppc64le systems with USE=ieee-long-double toolchain.
Signed-off-by: Georgy Yakovlev <gyakovlev <AT> gentoo.org>
dev-libs/libdispatch/libdispatch-5.7.1.ebuild | 4 ++++
dev-libs/libdispatch/libdispatch-5.7.3.ebuild | 4 ++++
2 files changed, 8 insertions(+)
diff --git a/dev-libs/libdispatch/libdispatch-5.7.1.ebuild b/dev-libs/libdispatch/libdispatch-5.7.1.ebuild
index c0c209226f47..da9e6411f534 100644
--- a/dev-libs/libdispatch/libdispatch-5.7.1.ebuild
+++ b/dev-libs/libdispatch/libdispatch-5.7.1.ebuild
@@ -15,6 +15,9 @@ SRC_URI="https://github.com/apple/${MY_PN}/archive/${MY_PV}.tar.gz -> ${P}.tar.g
LICENSE="Apache-2.0"
SLOT="0"
KEYWORDS="amd64 ~arm64 ppc64 ~riscv x86"
+IUSE="test"
+
+RESTRICT="!test? ( test )"
DEPEND="
!gnustep-base/libobjc2
@@ -49,5 +52,6 @@ src_configure () {
export HOST_CXX="$(tc-getBUILD_CXX)"
tc-export CC CXX LD AR NM OBJDUMP RANLIB PKG_CONFIG
+ local mycmakeargs=( -DBUILD_TESTING=$(usex test) )
cmake_src_configure
}
diff --git a/dev-libs/libdispatch/libdispatch-5.7.3.ebuild b/dev-libs/libdispatch/libdispatch-5.7.3.ebuild
index 33616ad732de..95454fe7e805 100644
--- a/dev-libs/libdispatch/libdispatch-5.7.3.ebuild
+++ b/dev-libs/libdispatch/libdispatch-5.7.3.ebuild
@@ -15,6 +15,9 @@ SRC_URI="https://github.com/apple/${MY_PN}/archive/${MY_PV}.tar.gz -> ${P}.tar.g
LICENSE="Apache-2.0"
SLOT="0"
KEYWORDS="~amd64 ~arm64 ~ppc64 ~riscv ~x86"
+IUSE="test"
+
+RESTRICT="!test? ( test )"
DEPEND="
!gnustep-base/libobjc2
@@ -49,5 +52,6 @@ src_configure () {
export HOST_CXX="$(tc-getBUILD_CXX)"
tc-export CC CXX LD AR NM OBJDUMP RANLIB PKG_CONFIG
+ local mycmakeargs=( -DBUILD_TESTING=$(usex test) )
cmake_src_configure
}
next reply other threads:[~2023-04-03 20:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 20:16 Georgy Yakovlev [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-02 6:06 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libdispatch/ WANG Xuerui
2023-05-27 11:27 Arthur Zamarin
2023-05-21 13:49 Arthur Zamarin
2023-05-21 0:50 Sam James
2023-05-03 3:53 Sam James
2023-05-02 17:35 Sam James
2023-05-02 15:28 Arthur Zamarin
2023-04-18 21:24 Piotr Karbowski
2023-03-29 20:51 Piotr Karbowski
2023-03-29 20:51 Piotr Karbowski
2023-03-07 11:42 Sam James
2023-03-06 13:04 Arthur Zamarin
2023-03-06 12:51 Arthur Zamarin
2022-11-14 21:32 Piotr Karbowski
2022-11-14 21:32 Piotr Karbowski
2022-11-06 8:05 Agostino Sarubbo
2022-11-06 3:59 Sam James
2022-11-06 3:59 Sam James
2022-06-26 12:36 Piotr Karbowski
2022-03-12 10:15 Arthur Zamarin
2022-02-07 6:32 Sam James
2022-02-06 13:42 Piotr Karbowski
2022-01-24 3:42 Sam James
2022-01-21 12:40 Sam James
2022-01-21 12:40 Sam James
2022-01-07 17:01 Georgy Yakovlev
2022-01-06 23:47 Georgy Yakovlev
2022-01-06 23:47 Georgy Yakovlev
2021-03-12 12:31 Piotr Karbowski
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=1680552751.102d9b22dc3c74927226fe3fa7b3a39eb4b1a012.gyakovlev@gentoo \
--to=gyakovlev@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