boost-libs: make boost type_traits build with clang 21
Recent versions of clang made -Wenum-constexpr-conversion errors into a
hard error, as was announced several versions ago.
Boost type_traits has two instances where it attempts to convert
out-of-range enum values, leading to errors similar to:
In file included from ../src/lib/dhcpsrv/csv_lease_file6.cc:9:
In file included from ../src/lib/dhcpsrv/dhcpsrv_log.h:11:
In file included from ../src/lib/log/macros.h:10:
In file included from ../src/lib/log/logger.h:19:
In file included from ../src/lib/log/log_formatter.h:19:
In file included from /usr/local/include/boost/lexical_cast.hpp:33:
In file included from /usr/local/include/boost/lexical_cast/try_lexical_convert.hpp:31:
In file included from /usr/local/include/boost/lexical_cast/detail/converter_numeric.hpp:31:
In file included from /usr/local/include/boost/type_traits/make_unsigned.hpp:14:
/usr/local/include/boost/type_traits/is_signed.hpp:37:25: error: in-class initializer for static data member is not a constant expression
37 | static const no_cv_t minus_one = (static_cast<no_cv_t>(-1));
[58 lines not shown]
boost-libs: make boost type_traits build with clang 21
Recent versions of clang made -Wenum-constexpr-conversion errors into a
hard error, as was announced several versions ago.
Boost type_traits has two instances where it attempts to convert
out-of-range enum values, leading to errors similar to:
In file included from ../src/lib/dhcpsrv/csv_lease_file6.cc:9:
In file included from ../src/lib/dhcpsrv/dhcpsrv_log.h:11:
In file included from ../src/lib/log/macros.h:10:
In file included from ../src/lib/log/logger.h:19:
In file included from ../src/lib/log/log_formatter.h:19:
In file included from /usr/local/include/boost/lexical_cast.hpp:33:
In file included from /usr/local/include/boost/lexical_cast/try_lexical_convert.hpp:31:
In file included from /usr/local/include/boost/lexical_cast/detail/converter_numeric.hpp:31:
In file included from /usr/local/include/boost/type_traits/make_unsigned.hpp:14:
/usr/local/include/boost/type_traits/is_signed.hpp:37:25: error: in-class initializer for static data member is not a constant expression
37 | static const no_cv_t minus_one = (static_cast<no_cv_t>(-1));
[56 lines not shown]
sysutils/mtail: New Port
mtail is a tool for extracting metrics from application logs to be
exported into a timeseries database or timeseries calculator for
alerting and dashboarding.
It fills a monitoring niche by being the glue between applications that
do not export their own internal state (other than via logs) and
existing monitoring systems, such that system operators do not need to
patch those applications to instrument them or writing custom extraction
code for every such application.
curlwp_bind(9): tweak example's markup
`-offset indent` indents less than a literal tab. While here,
untabify the example, groff's PS output is slightly misaligned
otherwise (within the literal display itself).
wifi: mt76: Remove blank line after mt792x firmware version dmesg
An extra blank line gets printed after printing firmware version
because the build date is null terminated. Remove the "\n" from
dev_info() calls to print firmware version and build date to fix
the problem.
Reported-by: Mario Limonciello <superm1 at gmail.com>
Signed-off-by: Shuah Khan <skhan at linuxfoundation.org>
Signed-off-by: Linus Torvalds <torvalds at linux-foundation.org>
ValueTracking: Improve handling of fadd in computeKnownFPClass.
This already recognized that if both inputs are positive, the
result is positive. Extend this to the mirror situation with
negative inputs.
Also special case fadd x, x. Canonically, fmul x, 2 is fadd x, x.
We can tell the sign bit won't change, and 0 will propagate.
ValueTracking: Add more baseline tests for computeKnownPPClass of fadd
Test cases with fadd x, x. Also test cases where both inputs are known
negative.
urndis(4): Attach at usbifif, not usbdevif, in the if_urndis module.
We really ought to have a static type system for config(5) interface
attributes to catch mistakes like this!
Came up while trying to test a fix for:
PR kern/59872: urndis(4): missing support for some devices
urndis(4): Match more interface ids.
There are some others we should consider too, based on what OpenBSD,
FreeBSD, and Linux match, but I haven't tested with these devices:
class subclass protocol
1. 0x02 (CDC) 0x02 (abstract control model) 0xff (? rndis?)
2. 0xef (misc) 0x01 (sync) 0x01 (active)
3. 0xef (misc) 0x04 (rndis) 0x03 (wimax)
4. 0xef (misc) 0x04 (rndis) 0x04 (wwan)
Note: FreeBSD uses `UIPROTO_RNDIS' for (3) even though the USB-IF
registry lists class 0xef, subclass 0x04, protocol 0x04 as `RNDIS
over WiMAX'; likewise `UIPROTO_ACTIVESYNC' for (4) even though it's
listed as `RNDIS over WWAN'. My guess is that for class 0xef
subclass 0x04, _any_ protocol will really be RNDIS, and it was a
mistake for FreeBSD to use those protocol numbers (which context
suggests were supposed to apply to different subclasses).
PR kern/59872: urndis(4): missing support for some devices
Update to 1.68
Upstream changes:
Changes for version 1.68 - 2025-12-21
Changes to AlphaVantage.pm and CurrencyRates/AlphaVantage.pm to throttle queries - Issue #546
YahooJSON.pm - Add additional fields/labels - PR #544
New Module, USBonds.pm
MarketWatch.pm - Added headers to fix 401 code - Issue #542
Modified AEX.pm to return no data available is currency indicator is '%' (bonds return percentage of par/facevalue) - Issue #539
Fixed YahooWeb.pm - Issue #533 - PR #538
Removed CMBChina.pm - no longer working - Issue #534
Rewrote Union.pm for URL that returns JSON - Issue #516
Modified parsing in BVB.pm - Issue #513
