Some of these files were already converted to UTF-8 upstream and so
we're now turning them into mojibake. For the remaining two:
- fix multi_index/example/hashed.cpp using a patch instead of iconv, so
that when my upstream patch for that file lands in Fedora we can drop
the patch and won't silently turn that file into mojibake.
- add an rpmlint filter for serialization/example/demo_output.txt
because that needs to be ISO-8859-1 encoded to match the output of the
serialization/example/demo.cpp program.
There's also a new file that's not UTF-8 which wasn't being fixed by the
spec file. I've submitted a pull request to fix that upstream, so add a
patch for that one too.
Add another rpmlint filter for some other warnings about boost-examples.
Also include SVG files in the boost-doc subpackage.
This was shown by the unbreq plugin to be not used.
It was added in cb253a3d3f for use when
creating the libboost_thread.so linker script. That linker script was
dropped in ec7383f6bd when rebasing to
1.90.0 which removed the libboost_system.so shared lib.
boost-devel Requires: boost, which itself needs to Requires all
library subpackages so that the libboost_*.so symlinks are resolved,
and packages can safely link to them.
This change addresses the issue of
https://github.com/boostorg/math/issues/1132
the patch addresses the issue where float_next() and float_prior() return
a domain error instead +INF or -INF. this issue is a regression in
Boost 1.79.
Signed-off-by: Kefu Chai <tchaikov@gmail.com>
This change addresses the issue of
https://github.com/boostorg/multiprecision/issues/553,
the fix prevents an application from crash due to an exception
thrown in a function marked `noexcept`, when converting a `cpp_int`
to a float, if the value of this `cpp_int` cannot be represented with
a float. this issue is a regression in Boost 1.79, see more details
at https://github.com/boostorg/multiprecision/pull/618
Signed-off-by: Kefu Chai <tchaikov@gmail.com>
This change silences the warning when compiling Boost.accumulators
with GCC 13. as some projects using Boost.Accumulators are compiled
with -Werror. Without this change, these project would have to disable
-Wuninitialized warning or silence it temporarily when including
the offending headers. Neither of these two solution is ideal from
a developer's perspective. so let's apply the patch when packaging
Boost. The patch was included by Boost 1.83.
Signed-off-by: Kefu Chai <tchaikov@gmail.com>
