[C++ Client] Warn, don't fail, on unknown compiler options#14752
[C++ Client] Warn, don't fail, on unknown compiler options#14752michaeljmarshall wants to merge 1 commit intoapache:masterfrom
Conversation
|
@michaeljmarshall:Thanks for your contribution. For this PR, do we need to update docs? |
1 similar comment
|
@michaeljmarshall:Thanks for your contribution. For this PR, do we need to update docs? |
|
@oversearch @merlimat @BewareMyPower - let me know if this option makes sense to add, or if we should actually just remove the |
|
Ironically, this option isn't known to the compiler for our CI builds. An additional data point: the build is not working for me on 2.10 because of the same error on 2.8.3. |
|
I think you can use https://godbolt.org/ to test if a compiler option works for a specific compiler. |
|
The pr had no activity for 30 days, mark with Stale label. |
|
This work is no longer necessary. |
Fix: #13429
Motivation
As discussed in #13429, it's helpful to make warnings errors. As such, I (naively) propose that instead of turning off this option, we should just turn it off for unknown warning options.
An alternative option is to remove the
-Wno-error=cppoption. However, based on the comment in the code just above it, it looks like that class of warnings is generally okay to ignore. Although, this change might be problematic in the event that certain warnings will break the build for one compiler and not for another, which will only become evident at release time.Modifications
-Wno-error=unknown-warning-optionto c++ client optionsVerifying this change
I will rely on those more familiar with C++ to verify this change. I am proposing it simply to try to fix the current issues.
Note that after this change, building the Python Client has these warning logs (that used to be errors):
Does this pull request potentially affect one of the following parts:
It just affects the build.