-
Notifications
You must be signed in to change notification settings - Fork 104
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
macos: ld: library not found for -lstdc++
when compiling no_deps
example
#247
Comments
pandas-dev/pandas#23424 (comment) may be relevant. |
https://developer.apple.com/documentation/xcode-release-notes/xcode-10-release-notes?preferredLanguage=occ suggests that on recent OSX libstd++ is no longer supported and libc++ should be used instead. |
bazelbuild/rules_rust#226 is probably the real bug here. |
Add this to the bottom of the
and create
Then everything works for the |
|
It builds, but running it produces no output.
However, running it with Cargo has the same problem:
so I'm not sure what's going on there. |
Without digging too deeply, is this a bug in |
The primary bug is in I think there's probably two bugs in the
The most version I have of those additions is:
|
Odd, I'm able to build the examples on MacOS just fine. Perhaps the rust rules are relying on some specific machine setup. It might be good to open a pull request to
Interesting, seems to me like if !log_enabled!(log::Level::Info) {
panic!("uh-oh");
} This should definitely be looked at and updated. I may take a stab at it when I can find the time. Sorry this isn't much help. But it's good to know where the issue is. You should chime in on bazelbuild/rules_rust#226 and let the owners know users are still running into that issue 😄 |
For folks experiencing |
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
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 <keithbsmiley@gmail.com>
with the landing of bazelbuild/bazel#14750 I believe this issue can be closed |
Building a fresh checkout of
examples/remote/no_deps
with Bazel 3.6.0 fails on MacOS with the error:Reproduction recipe:
cargo-raze
repository.The text was updated successfully, but these errors were encountered: