-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Envoy v1.29.0 build fails on Mac OS #31932
Comments
I think it was likely I was just the first to hit this. If this is WONTFIX, we should update documentation to say building on MacOS no longer possible after relevant commit. Wondering how many people are running MacOS instances in the cloud. |
i think it should be resolvable one way or other to clarify - macos does build, as we are building/testing in ci still (macos12 github runners) i believe the constraint is to use the correct versions of compiler - it may be that our ci just builds less and excludes cel - not sure and no way to test the setup for the macos12 images is here https://github.com/actions/runner-images/blob/main/images/macos/macos-12-Readme.md - i dont see any setup for this on our end (here https://github.com/envoyproxy/envoy/blob/main/ci/mac_ci_setup.sh) so assume that we are just using whatever is default in the macos12 image
perhaps we can (figure out and) specify what does work |
|
@phlax that's a fairly old version of macOS for CI. Is there a runner based on macOS version 14 we can use? |
Related #31456 (comment) |
Thanks for the extra context; I hadn't seen that. |
Attempting to catch build breaks similar to those in envoyproxy#31932 Signed-off-by: Greg Greenway <[email protected]>
Attempting to catch build breaks similar to those in #31932 Signed-off-by: Greg Greenway <[email protected]>
Title: Envoy v1.29.0 build fails on Mac OS
Description:
When I am building Envoy v1.29.0 on MacOS 12.7.1 with clang 14.0.0 I noticed an error
Envoy build error
I've tried both conrtib and not contrib build but I have the same issue.
Repro steps:
I've noticed that more people have the same issue Homebrew/homebrew-core#160068
The text was updated successfully, but these errors were encountered: