-
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
bazel coverage link error for C targets on macOS #5128
Comments
|
Looks like it is still broken in 0.14.1:
|
`-lgcov` is not supported on macOS. See #5128
in Bazel osx CROSSTOOL. -lgcov is not supported on macOS. See #5128. RELNOTES: None. PiperOrigin-RevId: 200691758
in Bazel osx CROSSTOOL. -lgcov is not supported on macOS. See bazelbuild#5128. RELNOTES: None. PiperOrigin-RevId: 200691758
Can someone verify if this is still happening with the latest Bazel release? |
This is still happening in 0.15.2, but I can't reproduce anymore in 0.16.0-rc3. Thanks for fixing it! |
Thanks for checking! |
in Bazel osx CROSSTOOL. -lgcov is not supported on macOS. See bazelbuild#5128. RELNOTES: None. PiperOrigin-RevId: 200691758
Description of the problem / feature request:
When building any
cc_test
target orcc_binary
target with coverage instrumentation on macOS,bazel coverage
fails with an error like this:Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
What operating system are you running Bazel on?
macOS High Sierra 10.13.4
What's the output of
bazel info release
?release 0.13.0
Any other information, logs, or outputs that you want to share?
It looks like
-lgcov
is being passed on the command line to the linker. macOS doesn't seem to have this library. Maybe passing--coverage
would be better? That works for me in small examples on both macOS and Linux, both gcc and clang.The text was updated successfully, but these errors were encountered: