-
Notifications
You must be signed in to change notification settings - Fork 1.2k
osx support #5154
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
osx support #5154
Conversation
/retest |
@@ -14,7 +14,7 @@ build:remote --remote_timeout=7200 | |||
# ======================================== | |||
|
|||
# Enable libc++ and C++20 by default. | |||
build --config=libc++20 | |||
build:linux --config=libc++20 |
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.
why disable on macos? we have c++20 code already I think.
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.
clang: error: invalid linker name in argument '-fuse-ld=lld'
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.
you should use clang's lld on macos? what linker are you using?
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.
I think the default one setting xcode.
I won't encourage anyone use proxy on macos for production, all these lines make that easier to develop on macos.
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.
I have no problems with allowing macos development. Just want to make sure we're not breaking release on linux.
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.
I do my best to make it won't happen, and there's a long time before next release, so I think it's pretty safe.
@@ -25,7 +25,8 @@ build --define path_normalization_by_default=true | |||
|
|||
# Heap profiler is supported only with gperf tcmalloc, not google tcmalloc. | |||
# See: https://github.com/istio/istio/issues/28233 | |||
build --define tcmalloc=gperftools | |||
build:linux --define tcmalloc=gperftools | |||
build:macos --define tcmalloc=disabled |
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.
Same - why disable gperftools?
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.
always fails with following error:
configure: error: in `/private/var/tmp/_bazel_zirain/351f889f26744009d08525dc5ecb1daa/sandbox/darwin-sandbox/371/execroot/io_istio_proxy/bazel-out/darwin_arm64-fastbuild/bin/external/envoy/bazel/foreign_cc/gperftools_build.build_tmpdir':
configure: error: C compiler cannot create executables
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.
ok, it's fine but you won't get heap profile and some tools. what does tcmalloc disabled mean? what malloc is it using?
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.
envoy has same line, this's a known limitation. https://github.com/envoyproxy/envoy/blob/05457bb047b87f4cc1a25635400ddcaa7fccc923/.bazelrc#L138
I won't encourage anyone use proxy on macos for production, all these line make that easier to develop on macos.
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.
I don't recall, does linux
configuration automatically kick-in?
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.
if not, there must be huge problem.
/retest |
@zirain the mac build is failing for me with
seems to be related to bazel-contrib/rules_foreign_cc#859, however I'm not very proficient neither with bazel nor with c, would you have any tips how to work around this? Seems to be some fairly recent change (bazel version change?) as I was able to build the proxy @ 1.17.8, but it's failing at HEAD as well as @1.19.4 tag. Thank you! |
I test these only for master on m1 mac pro, I will give a try when I have bandwidth. |
thanks! this is also m1 mac pro (ventura 13.6) |
@jcetkov I can build release-1.19 on m1 macpro(Sonoma 14.1.1) with following change:
for dlb issue, please take a look at envoyproxy/envoy#30951, which didn't backport. |
this PR aim to make it possible to run
make build
on m1 mac pro