-
Notifications
You must be signed in to change notification settings - Fork 101
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
Bazel builds using rules_cc on recent (Ventura, Sonoma) MacOS fail due to -undefined dynamic_lookup #229
Comments
This is equivalent to bazelbuild/bazel#16414. Fixes bazelbuild#229
Probably already fixed by commit c2549f6 |
if not this should be fixed in rules_foreign_cc not here |
@keith I looked again - if I understand @AIWintermuteAI correctly, this is about -undefined dynamic_lookup still being present in rules_cc, namely in https://github.com/bazelbuild/rules_cc/blob/main/cc/private/toolchain/cc_toolchain_config.bzl#L388. Should we remove that here, in the wake of bazelbuild/bazel#16414? |
My understanding is that toolchain you linked should be deleted. it was always meant to be in sync with bazel's cc toolchain, but it wasn't kept up to sync. and now that bazel's has moved here in c2549f6, users should use that instead. But yes if we keep it we should remove it (but also would have to change tons more stuff) |
My understanding is that that file is unused and should be deleted, cf. #287 |
Description of the problem / feature request:
Bazel builds using rules_cc on recent (Ventura, Sonoma) MacOS fail with
The root cause of this issue was that bazelbuild/bazel#16414 was not merged to rules_cc, but only to rules_llvm and apple_support. Which removed the culprit -undefined dynamic_lookup.
This issue gives more insight in the problem:
bazel-contrib/rules_foreign_cc#859 (comment)
What operating system are you running Bazel on?
What's the output of
bazel info release
?release 6.0.0- (@non-git)
If
bazel info release
returns "development version" or "(@non-git)", tell us how you built Bazel.Conda forge
What version of rules_cc do you use? Can you paste the workspace rule used to fetch rules_cc? What other relevant dependencies does your project have?
What Bazel options do you use to trigger the issue? What C++ toolchain do you use?
The text was updated successfully, but these errors were encountered: