TileDB is an efficient multi-dimensional array management system which
introduces a novel format that can effectively store dense and sparse array data
with support for fast updates and reads. It features excellent compression, an
efficient parallel I/O system for high scalability, and high-level APIs
including Python, R, Golang and more.
TileDB stores your array data on persistent storage locally or in the cloud,
with built-in support for S3 and HDFS storage backends.
Features:
- Novel Format.
- Multiple Backends.
- Compression.
- Parallelism.
- Portability.
- Language Bindings.
- Key-value Store.
- Virtual Filesystem.
===> The following configuration options are available for tiledb-2.30.1_1:
AVX2=off: AVX2 instructions support
===> Use 'make config' to modify these settings
devel/spdlog: Update to 1.17.0
- Use complete arguments/options
- Bump PORTREVISION of dependent ports for shlib change
Changes: https://github.com/gabime/spdlog/releases
devel/libfmt: Bump PORTREVISION of dependent ports for shlib change after
786cb608216ce14e8ced27108c96a1f2c8492fca
The following ports are skipped because they have been updated after
786cb608216ce14e8ced27108c96a1f2c8492fca.
- chinese/fcitx5-chinese-addons
- chinese/fcitx5-mcbopomofo
- devel/fatal
- devel/fbthrift
- devel/folly
- devel/spdlog
- mail/mu
- net/fb303
- net/mvfst
- net/wangle
- science/seacas
- security/fizz
- www/proxygen
databases/tiledb: fix build on non-amd64
1. Fix build on powerpc by adding -Wno-c++11-narrowing.
2. Disable AVX2 by default since only modern amd64 supports it.
databases/tiledb: Fix configure with CMake >= 3.27
After [1], CMake trusts OPENSSL_ROOT_DIR implicitly, so if isn't set
right, OpenSSL may not be found.
This project uses OPENSSL_PATHS to set OPENSSL_ROOT_DIR, so CMake tries
to find OpenSSL in TILEDB_EP_INSTALL_PREFIX which is problably not where
we want to look. Pass ${OPENSSLBASE} to set OPENSSL_PATHS so we are
looking in the right location.
[1]
https://github.com/Kitware/CMake/commit/5cc8a69867ac42333a656607d90059a6db823abd
PR: 274225
Approved by: portmgr (blanket build fix)
databases/tiledb: fix build on armv6/armv7
Same fix as the one sunpoet@ previously applied for i386.
Obtained from: 204c0a1aad55dee9e4e0c34e975d40f6f6e51b02
Approved by: portmgr (build fix blanket)
MFH: 2023Q4
databases/tiledb: Update to 2.17.1
databases/tiledb: Fix build on i386
/wrkdirs/usr/ports/databases/tiledb/work/TileDB-2.17.1/tiledb/../tiledb/sm/array_schema/enumeration.h:281:50:
error: non-constant-expression cannot be narrowed from type 'uint64_t' (aka
'unsigned long long') to 'size_type' (aka 'unsigned int') in initializer list
[-Wc++11-narrowing]
return {static_cast<uint8_t*>(data_.data()), data_.size()};
^~~~~~~~~~~~
/wrkdirs/usr/ports/databases/tiledb/work/TileDB-2.17.1/tiledb/../tiledb/sm/array_schema/enumeration.h:281:50:
note: insert an explicit cast to silence this issue
return {static_cast<uint8_t*>(data_.data()), data_.size()};
^~~~~~~~~~~~
static_cast<size_type>( )
/wrkdirs/usr/ports/databases/tiledb/work/TileDB-2.17.1/tiledb/../tiledb/sm/array_schema/enumeration.h:291:53:
error: non-constant-expression cannot be narrowed from type 'uint64_t' (aka
'unsigned long long') to 'size_type' (aka 'unsigned int') in initializer list
[-Wc++11-narrowing]
return {static_cast<uint8_t*>(offsets_.data()), offsets_.size()};
^~~~~~~~~~~~~~~
/wrkdirs/usr/ports/databases/tiledb/work/TileDB-2.17.1/tiledb/../tiledb/sm/array_schema/enumeration.h:291:53:
note: insert an explicit cast to silence this issue
return {static_cast<uint8_t*>(offsets_.data()), offsets_.size()};
^~~~~~~~~~~~~~~
static_cast<size_type>( )
2 errors generated.
Reference: https://pkg-status.freebsd.org/beefy17/data/main-i386-default/pe4b8bfc7570d_sf7a5903de2/logs/tiledb-2.17.1.loghttps://pkg-status.freebsd.org/beefy15/data/132i386-default/e4b8bfc7570d/logs/tiledb-2.17.1.log
databases/tiledb: Fix build on i386
/wrkdirs/usr/ports/databases/tiledb/work/TileDB-2.15.2/tiledb/sm/fragment/fragment_metadata.cc:1721:18:
error: non-constant-expression cannot be narrowed from type 'unsigned long long'
to 'std::basic_string_view::size_type' (aka 'unsigned int') in initializer list
[-Wc++11-narrowing]
return {min, size};
^~~~
/wrkdirs/usr/ports/databases/tiledb/work/TileDB-2.15.2/tiledb/sm/fragment/fragment_metadata.cc:1721:18:
note: insert an explicit cast to silence this issue
return {min, size};
^~~~
static_cast<size_type>( )
/wrkdirs/usr/ports/databases/tiledb/work/TileDB-2.15.2/tiledb/sm/fragment/fragment_metadata.cc:1725:38:
error: non-constant-expression cannot be narrowed from type 'uint64_t' (aka
'unsigned long long') to 'std::basic_string_view::size_type' (aka 'unsigned
int') in initializer list [-Wc++11-narrowing]
return {static_cast<char*>(min), size};
^~~~
/wrkdirs/usr/ports/databases/tiledb/work/TileDB-2.15.2/tiledb/sm/fragment/fragment_metadata.cc:1725:38:
note: insert an explicit cast to silence this issue
return {static_cast<char*>(min), size};
^~~~
(Only the first 15 lines of the commit message are shown above )
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
Disable TBB
- Bump PORTREVISION for dependency change
Upstream has disabled the use of TBB by default and will likely be removing
support for it in the an upcoming release over the next couple months. They
also replaced the use of TBB with their own internal threadpool implementation
that uses standard C++ threading.
Reference: https://github.com/TileDB-Inc/TileDB/issues/2039
