-
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
Remove uses of -lstdc++ on darwin #14542
Conversation
This flag has been invalid seemingly since macOS 10.9 from 2013. By default clang remaps this back to -lc++, but if your linkopts pass -nodefaultlibs this is not the case, in which case this invalid flag fails the link. This happened for rust builds where the rust driver passes this flag intentionally. For more info see bazelbuild#14395 (comment)
Does this also fix bazelbuild/rules_rust#978? |
I don't think so, I think we'd also have to change bazel/tools/cpp/cc_toolchain_config.bzl Line 374 in 26d4aad
|
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
I agree, that sounds like the best thing to do. For now, is it possible to get this change merged? We're essentially stuck on Bazel 4.2.1 until then. |
@Wyverald This would be nice to get into 5.0.1. |
This fix is the same as bazelbuild#14542 but for freebsd and openbsd
I submitted #14668 for the bsds |
@bazel-io fork 5.1 |
This flag has been invalid seemingly since macOS 10.9 from 2013. By default clang remaps this back to -lc++, but if your linkopts pass -nodefaultlibs this is not the case, in which case this invalid flag fails the link. This happened for rust builds where the rust driver passes this flag intentionally. For more info see bazelbuild#14395 (comment) Fixes google/cargo-raze#247 bazelbuild#14395 bazelbuild/rules_rust#226 Closes bazelbuild#14542. PiperOrigin-RevId: 424588734 (cherry picked from commit 8b60c90)
This flag has been invalid seemingly since macOS 10.9 from 2013. By default clang remaps this back to -lc++, but if your linkopts pass -nodefaultlibs this is not the case, in which case this invalid flag fails the link. This happened for rust builds where the rust driver passes this flag intentionally. For more info see #14395 (comment) Fixes google/cargo-raze#247 #14395 bazelbuild/rules_rust#226 Closes #14542. PiperOrigin-RevId: 424588734 (cherry picked from commit 8b60c90) Co-authored-by: Keith Smiley <[email protected]>
This fix is the same as #14542 but for freebsd and openbsd Hopefully fixes bazelbuild/rules_rust#978 Closes #14668. PiperOrigin-RevId: 429354084
This fix is the same as bazelbuild#14542 but for freebsd and openbsd Hopefully fixes bazelbuild/rules_rust#978 Closes bazelbuild#14668. PiperOrigin-RevId: 429354084 (cherry picked from commit a987b98)
This fix is the same as #14542 but for freebsd and openbsd Hopefully fixes bazelbuild/rules_rust#978 Closes #14668. PiperOrigin-RevId: 429354084 (cherry picked from commit a987b98) Co-authored-by: Keith Smiley <[email protected]>
This flag has been invalid seemingly since macOS 10.9 from 2013. By
default clang remaps this back to -lc++, but if your linkopts pass
-nodefaultlibs this is not the case, in which case this invalid flag
fails the link. This happened for rust builds where the rust driver
passes this flag intentionally.
For more info see #14395 (comment)
Fixes google/cargo-raze#247 #14395 bazelbuild/rules_rust#226