-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Enable user_link_flags_feature for macosx cc_toolchain_config #14275
Conversation
This will cause the values passed in the link_libs parameters to not get silently dropped on macOS 12 Monterey, and fix the problem where the command line dev tools toolchain will output C++ binaries fails to start with a segmentation fault error. Fixes: bazelbuild#14273
@nresare looks like you need to sign the CLA here |
@googlebot I signed it! |
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 can't reproduce this, I assume because I installed Xcode which altered the system some way. But This not being here seems like an oversight anyways so it seems like a good fix
@google-cla I signed it! |
@gregestren since you were triaging related issues maybe you can help get this merged? It should fix #14216 // @oquenchil |
Maybe worth cherry-picking this onto the 4.2 branch and releasing a 4.2.2? Seems pretty serious if you ask me. |
@keith happy to but since I'm not a domain expert here my main role is going to be routing. I assigned to the Rules / CPP team and @comius team lead according to triage policy. Also CC'ing @meteorcloudy and @Wyverald who are listed at #14013 re: qualifying for a 4.2 branch. |
This will cause the values passed in the link_libs parameters to not get silently dropped on macOS 12 Monterey, and fix the problem where the command line dev tools toolchain will output C++ binaries fails to start with a segmentation fault error. Fixes: bazelbuild#14273 Closes bazelbuild#14275. PiperOrigin-RevId: 411840375
This was fixed by enabling the user_link_flags_feature for macosx cc_toolchain_config. References: - bazelbuild/bazel#14216 - bazelbuild/bazel#14275
This will cause the values passed in the link_libs parameters to not get silently dropped on macOS 12 Monterey, and fix the problem where the command line dev tools toolchain will output C++ binaries fails to start with a segmentation fault error. Fixes: #14273 Closes #14275. PiperOrigin-RevId: 411840375
This will cause the values passed in the link_libs parameters to not get silently dropped on macOS 12 Monterey, and fix the problem where the command line dev tools toolchain will output C++ binaries fails to start with a segmentation fault error. Fixes: bazelbuild#14273 Closes bazelbuild#14275. PiperOrigin-RevId: 411840375
This will cause the values passed in the link_libs parameters to not get silently dropped on macOS 12 Monterey, and fix the problem where the command line dev tools toolchain will output C++ binaries fails to start with a segmentation fault error. Fixes: #14273 Closes #14275. PiperOrigin-RevId: 411840375
This was fixed by enabling the user_link_flags_feature for macosx cc_toolchain_config. References: - bazelbuild/bazel#14216 - bazelbuild/bazel#14275
This was fixed by enabling the user_link_flags_feature for macosx cc_toolchain_config. References: - bazelbuild/bazel#14216 - bazelbuild/bazel#14275 (cherry picked from commit dc8d4f3)
This was fixed by enabling the user_link_flags_feature for macosx cc_toolchain_config. References: - bazelbuild/bazel#14216 - bazelbuild/bazel#14275 (cherry picked from commit dc8d4f3)
) This was fixed by enabling the user_link_flags_feature for macosx cc_toolchain_config. References: - bazelbuild/bazel#14216 - bazelbuild/bazel#14275
This will cause the values passed in the link_libs parameters to not get silently dropped on macOS 12 Monterey, and fix the problem where the command line dev tools toolchain will output C++ binaries fails to start with a segmentation fault error. Fixes: bazelbuild#14273 Closes bazelbuild#14275. PiperOrigin-RevId: 411840375
bazel 4.2.1 has a problem on MacOS Monterey that was fixed in 4.2.2: bazelbuild/bazel#14275 PiperOrigin-RevId: 425548083
fix protoc crash on macos 12.x see bazelbuild#14275
This will cause the values passed in the link_libs parameters
to not get silently dropped on macOS 12 Monterey, and fix
the problem where the command line dev tools toolchain
will output C++ binaries fails to start with a segmentation
fault error.
Fixes: #14273