Open k15tfu opened 3 years ago
I was able to work around this problem by selectively disabling "-Wunknown-warning-option" in my code. For example:
#if defined(__clang__)
#pragma clang diagnostic push
#pragma clang diagnostic ignored "-Wunknown-warning-option"
#endif
#include <boost/log/expressions.hpp>
#if defined(__clang__)
#pragma clang diagnostic pop
#endif
@ericniebler and @Kojoley - Any possibility of a fix for this issue? I would like to upgrade to boost 1.76 but am currently unable to do so because of this issue. It is unfortunate that Apple Xcode gets tripped up like this, but building with -Wno-unknown-warning-option
isn't really possible in my situation, since it can affect the meaning of configure checks for the availability of warning flags:
clang++ -Werror -Wthing-that-doesnt-exist -c ./hello_world.cpp ; echo $?
error: unknown warning option '-Wthing-that-doesnt-exist' [-Werror,-Wunknown-warning-option]
1
clang++ -Werror -Wthing-that-doesnt-exist -Wno-unknown-warning-option -c ./hello_world.cpp ; echo $?
0
So I can't really feed that flag into the build at issue via CFLAGS
on the command line. And because the error comes from a header, I can't scope application of -Wno-unknown-warning-option
just to the part of the build that compiles boost - code that consumes the expr.hpp
header is also affected. I could do as @peter-bloomfield has done and wrap all uses of boost headers that transitively include expr.hpp
, but that is somewhat unpalatable for a larger project.
In file boost/proto/expr.hpp:
Related to #22, #24.