-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cel: fix gcc contrib build #31814
cel: fix gcc contrib build #31814
Conversation
Signed-off-by: Kuat Yessenov <[email protected]>
CC @envoyproxy/dependency-shepherds: Your approval is needed for changes made to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, thanks @kyessenov
lets try and move as much of this patch upstream as we can after release
Will file a bug internally. Google doesn't build with GCC - and this is a GCC weirdness. |
This reverts commit 21c4a2c. Signed-off-by: Greg Greenway <[email protected]>
gcc complains about FieldBackedMapImpl::ListKeys when overloaded-virtual check is enabled. When using -Werror, warnings like this are converted to errors breaking builds. That's what happened to gcc build of Envoy a while back. The issue in Envoy was fixed by introducing a patch for cel-cpp that was applied to the source during Envoy build (see envoyproxy/envoy#31814). Unfortunately during cel-cpp version update in Envoy instead of updating the patch, dropping the parts that are not needed anymore, we dropped the whole cep-cpp patch all together in envoyproxy/envoy#36661. And now gcc can't build Envoy again. This change makes the change to silence the gcc warning in the cel-cpp codebase, which hopefully will be a bit more durable than maintaing a patch on the Envoy side. Signed-off-by: Mikhail Krinkin <[email protected]>
Commit Message: Fixes #31760