From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-libs/pdal/
Date: Sun, 18 May 2025 13:48:24 +0000 (UTC) [thread overview]
Message-ID: <1747576084.f2329f537e6c235f04e3ac71ffea84342a23afde.sam@gentoo> (raw)
commit: f2329f537e6c235f04e3ac71ffea84342a23afde
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun May 18 13:47:40 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun May 18 13:48:04 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f2329f53
sci-libs/pdal: add 2.8.4
The USE=debug LTO issue is gone, but there's another (irrespective of USE)
ODR problem now.
Bug: https://github.com/PDAL/PDAL/issues/4709
Bug: https://bugs.gentoo.org/862915
Signed-off-by: Sam James <sam <AT> gentoo.org>
sci-libs/pdal/Manifest | 1 +
sci-libs/pdal/pdal-2.8.4.ebuild | 63 +++++++++++++++++++++++++++++++++++++++++
2 files changed, 64 insertions(+)
diff --git a/sci-libs/pdal/Manifest b/sci-libs/pdal/Manifest
index 4393152b9eb5..dce829479db7 100644
--- a/sci-libs/pdal/Manifest
+++ b/sci-libs/pdal/Manifest
@@ -1,3 +1,4 @@
DIST PDAL-2.8.0-src.tar.bz2 87483358 BLAKE2B 8d15187f2b6a7110d52e2621d65ee8eedce0dd21c415c18fbb1e48dbdb0b24307b42487f4631f227875079ba47031c27196399970458236c7139b8f1418aa3b8 SHA512 d3b02f13e56423c5086e72908f932db384cb0d64f3d3e5cec121c1e283268f8e38f6123ff852d77c07ea9777001a78595bdafed458dc06aa52402d92e76ce995
DIST PDAL-2.8.1-src.tar.bz2 87507277 BLAKE2B 634ba5f2c5548bfa1fbdcc257185dcd99d2c8bda73e3ac24cf092d378150285912d9c5b48c88e21df14d5502221865273fa6167b82886ef848fc7d445c8937dc SHA512 fb1d0e892ea38518526ce0086415fffd92f356d104d9982f8883d254a206a75b51ff796dbf5db266a4dc8345ae91b825e8a50ae78eb21552c86ab600905850ad
DIST PDAL-2.8.2-src.tar.bz2 87504277 BLAKE2B b2037a4fe5ac369380d2b2d83a2210a3c17757f9e6f749e819854d7356ba07d85b83fe3221ab9024f40f8a9f0ec6ee86573092914ac633af56b361a2f128cb00 SHA512 82dc84192e0cda809f4b12233e009c0c92328bf78001fc6394f56b28514a4b20de17dd354904d44cebc40c28a78828c47a1324b749143cc5b41b6c322902a442
+DIST PDAL-2.8.4-src.tar.bz2 86725389 BLAKE2B f1f1009be5d0655f33fe6c57f1efe0f878bb2a2de2075a3d18b2e64d4a07d5201857a78b13288365b9110e106022a473cf7793e1ac2c744499ba0752c67bd0c3 SHA512 5d754d6fa656615aa4a9dc31ca5d5c051194148d721ce217ca4b8a87af54889717b8470b789899e486e0ed3154906659b0c336ed7571abddda0a182febf37e6b
diff --git a/sci-libs/pdal/pdal-2.8.4.ebuild b/sci-libs/pdal/pdal-2.8.4.ebuild
new file mode 100644
index 000000000000..a78df3c9e644
--- /dev/null
+++ b/sci-libs/pdal/pdal-2.8.4.ebuild
@@ -0,0 +1,63 @@
+# Copyright 2021-2025 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+inherit cmake flag-o-matic
+
+DESCRIPTION="A C++ library for translating and manipulating point cloud data"
+HOMEPAGE="https://pdal.io/"
+SRC_URI="https://github.com/PDAL/PDAL/releases/download/${PV}/PDAL-${PV}-src.tar.bz2"
+S="${WORKDIR}/PDAL-${PV}-src"
+
+LICENSE="BSD"
+SLOT="0/18"
+KEYWORDS="~amd64 ~arm ~arm64 ~x86"
+IUSE="debug postgres test"
+
+BDEPEND="
+ sys-devel/gettext
+ virtual/pkgconfig
+"
+RDEPEND="
+ net-misc/curl
+ app-arch/zstd:=
+ dev-libs/libxml2
+ dev-libs/openssl:=
+ sci-libs/gdal:=
+ sci-libs/libgeotiff:=
+ sys-libs/zlib
+ debug? ( sys-libs/libunwind:= )
+ postgres? ( dev-db/postgresql:*[xml] )
+"
+
+DEPEND="
+ test? ( sci-libs/gdal[geos,jpeg,png,sqlite] )
+ ${RDEPEND}
+"
+
+RESTRICT="!test? ( test )"
+
+src_configure() {
+ # https://github.com/PDAL/PDAL/issues/4709
+ append-flags -fno-strict-aliasing
+ filter-lto
+
+ local mycmakeargs=(
+ -DBUILD_PLUGIN_PGPOINTCLOUD="$(usex postgres)"
+ -DWITH_COMPLETION=ON
+ -DWITH_BACKTRACE="$(usex debug)"
+ )
+
+ cmake_src_configure
+}
+
+src_test() {
+ local myctestargs=(
+ --exclude-regex '(pgpointcloudtest|pdal_info_test|pdal_io_bpf_base_test|pdal_io_bpf_zlib_test|pdal_filters_overlay_test|pdal_filters_stats_test|pdal_app_plugin_test|pdal_merge_test|pdal_io_stac_reader_test)'
+ --output-on-failure
+ -j1
+ )
+
+ cmake_src_test
+}
next reply other threads:[~2025-05-18 13:48 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-18 13:48 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-30 13:57 [gentoo-commits] repo/gentoo:master commit in: sci-libs/pdal/ Sam James
2025-10-13 16:43 Sam James
2025-09-10 19:40 Andreas Sturmlechner
2025-09-10 19:40 Andreas Sturmlechner
2025-08-30 1:26 Sam James
2025-07-22 19:41 Sam James
2025-06-24 4:01 Eli Schwartz
2025-03-10 22:43 Sam James
2024-12-22 18:55 Sam James
2024-12-17 17:34 Sam James
2024-12-14 7:28 Joonas Niilola
2024-12-01 11:45 Sam James
2024-12-01 11:45 Sam James
2024-11-23 20:15 Arthur Zamarin
2024-11-11 22:39 Sam James
2024-09-23 15:17 Andrew Ammerlaan
2024-08-15 20:30 Sam James
2024-03-17 7:50 Sam James
2024-02-07 8:19 Joonas Niilola
2024-01-30 19:29 Sam James
2024-01-27 6:35 Joonas Niilola
2023-12-05 6:38 Joonas Niilola
2023-11-29 14:13 Andrew Ammerlaan
2023-05-06 3:55 Sam James
2022-11-24 8:10 Joonas Niilola
2022-11-22 20:55 Sam James
2022-11-22 7:56 Arthur Zamarin
2022-11-10 19:48 Arthur Zamarin
2022-10-31 17:43 Sam James
2022-10-31 11:50 Joonas Niilola
2022-10-31 11:50 Joonas Niilola
2022-10-12 23:32 Sam James
2022-06-03 5:50 Jakov Smolić
2022-04-17 17:31 Sam James
2022-04-17 11:11 Jakov Smolić
2022-04-17 9:49 Joonas Niilola
2022-02-20 23:33 Sam James
2022-02-20 23:12 Sam James
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=1747576084.f2329f537e6c235f04e3ac71ffea84342a23afde.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