graphics/podofo: fix build with libc++ >= 20
With libc++ 20 or higher graphics/podofo fails to build, with errors
similar to:
/wrkdirs/usr/ports/graphics/podofo/work/podofo-0.10.4/src/podofo/main/PdfColor.cpp:686:13: error: call to 'from_chars' is ambiguous
686 | if (std::from_chars(name.data() + 1, name.data() + name.size(), grayVal, chars_format::fixed).ec != std::errc())
| ^~~~~~~~~~~~~~~
/usr/include/c++/v1/__charconv/from_chars_floating_point.h:63:1: note: candidate function
63 | from_chars(const char* __first, const char* __last, double& __value, chars_format __fmt = chars_format::general) {
| ^
/wrkdirs/usr/ports/graphics/podofo/work/podofo-0.10.4/src/podofo/private/charconv_compat.h:34:30: note: candidate function
34 | inline from_chars_result from_chars(const char* first, const char* last,
| ^
This is because libc++ 20 started offering std::from_chars() for
floating point values, and pododo does not check for this. Correct the
WANT_FROM_CHARS check to correctly check for libc++ 20 or higher.
[5 lines not shown]
graphics/podofo: fix build with libc++ >= 20
With libc++ 20 or higher graphics/podofo fails to build, with errors
similar to:
/wrkdirs/usr/ports/graphics/podofo/work/podofo-0.10.4/src/podofo/main/PdfColor.cpp:686:13: error: call to 'from_chars' is ambiguous
686 | if (std::from_chars(name.data() + 1, name.data() + name.size(), grayVal, chars_format::fixed).ec != std::errc())
| ^~~~~~~~~~~~~~~
/usr/include/c++/v1/__charconv/from_chars_floating_point.h:63:1: note: candidate function
63 | from_chars(const char* __first, const char* __last, double& __value, chars_format __fmt = chars_format::general) {
| ^
/wrkdirs/usr/ports/graphics/podofo/work/podofo-0.10.4/src/podofo/private/charconv_compat.h:34:30: note: candidate function
34 | inline from_chars_result from_chars(const char* first, const char* last,
| ^
This is because libc++ 20 started offering std::from_chars() for
floating point values, and pododo does not check for this. Correct the
WANT_FROM_CHARS check to correctly check for libc++ 20 or higher.
[3 lines not shown]
devel/libddwaf: fix build with clang 21
With clang 21 devel/libddwaf fails to build, with errors similar to:
In file included from /wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/format.cc:8:
/wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/format-inl.h:61:19: error: call to consteval function 'ddwaf::fmt::basic_format_string<char, ddwaf::fmt::basic_string_view<char> &, const char (&)[3]>::basic_format_string<FMT_COMPILE_STRING, 0>' is not a constant expression
61 | format_to(it, FMT_STRING("{}{}"), message, SEP);
| ^
/wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/format.h:1905:23: note: expanded from macro 'FMT_STRING'
1905 | #define FMT_STRING(s) FMT_STRING_IMPL(s, fmt::detail::compile_string, )
| ^
/wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/format.h:1882:3: note: expanded from macro 'FMT_STRING_IMPL'
1882 | [] { \
| ^
/wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/core.h:688:54: note: subexpression not valid in a constant expression
688 | format_str_.remove_prefix(detail::to_unsigned(it - begin()));
| ~~~^~~~~~~~~
/wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/core.h:2639:5: note: in call to 'this->context_.advance_to(&"{}{}"[1])'
2639 | context_.advance_to(begin);
[64 lines not shown]
devel/libddwaf: fix build with clang 21
With clang 21 devel/libddwaf fails to build, with errors similar to:
In file included from /wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/format.cc:8:
/wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/format-inl.h:61:19: error: call to consteval function 'ddwaf::fmt::basic_format_string<char, ddwaf::fmt::basic_string_view<char> &, const char (&)[3]>::basic_format_string<FMT_COMPILE_STRING, 0>' is not a constant expression
61 | format_to(it, FMT_STRING("{}{}"), message, SEP);
| ^
/wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/format.h:1905:23: note: expanded from macro 'FMT_STRING'
1905 | #define FMT_STRING(s) FMT_STRING_IMPL(s, fmt::detail::compile_string, )
| ^
/wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/format.h:1882:3: note: expanded from macro 'FMT_STRING_IMPL'
1882 | [] { \
| ^
/wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/core.h:688:54: note: subexpression not valid in a constant expression
688 | format_str_.remove_prefix(detail::to_unsigned(it - begin()));
| ~~~^~~~~~~~~
/wrkdirs/usr/ports/devel/libddwaf/work/libddwaf-1.30.1/src/vendor/fmt/core.h:2639:5: note: in call to 'this->context_.advance_to(&"{}{}"[1])'
2639 | context_.advance_to(begin);
[62 lines not shown]
Services: Unbound DNS: Blocklists - split logic in update_blocklist() so we can reuse it easily in list_configuration().
Functionally this shouldn't change anything, but when building additional handlers, it's practical to show priorities of the ones that are registered.
To use the list action, simply call:
./blocklists.py list
[DAG] isKnownToBeAPowerOfTwo - add DemandedElts, OrZero arguments and support for zero constants (#181485)
Update the signature for isKnownToBeAPowerOfTwo methods to take
DemandedElts and OrZero arguments.
So far all I've done is add OrZero support for constants
(scalars/buildvector/splat), with the intention to incrementally extend
support in the future (or spread the work as beginner GFI patches).
Similarly the DemandedElts argument is currently only used for constant
build vector tests but support can be extended in future patches.
Fixes #178938
devel/okteta: Update to 0.26.25
Release notes:
The port to Qt6 is still on-going (only remaining blocker as before the port
from QtScript to some other JS engine), no ETA currently.
Changes since 0.26.24:
* Improved: ensure focus is set on view after bookmark activation/creation
* Improved: use correct offsets after too large primitive structures arrays
BUG: https://bugs.kde.org/514151
* Fixed: do not scan parent dir of structures data dir for definitions
* Fixed: do not crash on warning for too large structures array length
