forked from amazingfate/loongoffice
e5c6574f5d
Upstream maintainers, with few exceptions, generally don't care about warnings in boost headers, hence we re-base our warning fix patches on every upgrade, which is a pointless exercise in frustration. Most of the patches are for GCC/Clang warnings, where we could use -isystem to suppress the warnings (with corresponding hacks in the build system, because -isystem also disables dependency generation) - but clang-cl does not support -isystem. So generate a bunch of wrapper headers into external/boost/include, that disable all known warnings and use #include_next to get the real boost header. This allows us to get rid of most of the existing patches. There is however a bug in GCC that preprocessor warnings like -Wundef cannot be disabled with a #pragma, so those patches cannot be removed. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53431 Change-Id: I2992bf4a463015f1140489df867bd80757f84541 Reviewed-on: https://gerrit.libreoffice.org/25563 Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Michael Stahl <mstahl@redhat.com>
14 lines
378 B
Plaintext
14 lines
378 B
Plaintext
Work around -fsanitize=bool
|
|
|
|
--- boost/algorithm/string/find_iterator.hpp
|
|
+++ boost/algorithm/string/find_iterator.hpp
|
|
@@ -240,7 +240,7 @@
|
|
m_Match(Other.m_Match),
|
|
m_Next(Other.m_Next),
|
|
m_End(Other.m_End),
|
|
- m_bEof(Other.m_bEof)
|
|
+ m_bEof(Other.eof())
|
|
{}
|
|
|
|
//! Constructor
|