Open mmdriley opened 3 years ago
for posterity: we noticed this when a developer ran
bazelisk build //executable_semantics:*
because the *
picks up all file targets, which includes the implicit .stripped
target of the executable_semantics
binary. Building //executable_semantics/...
or //executable_semantics:all
wouldn't reproduce the issue.
/cc @chandlerc for interest
We triage inactive PRs and issues in order to make it easier to find active work. If this issue should remain active or becomes active again, please comment or remove the inactive
label. The long term
label can also be added for issues which are expected to take time.
This issue is labeled inactive
because the last activity was over 90 days ago.
On macOS, at 9ed1c5cee9c3326178b80a35a8f217257971b410, with or without
.bazeliskrc
wired to4.0.0
:We can confirm with
aquery
that Bazel is invokingllvm-strip
with no arguments:By comparison, if I create another Bazel workspace elsewhere and let it pick up the local toolchain, we see:
that configuration appears to come from: https://github.com/bazelbuild/bazel/blob/073ae810e4f61f56f68a31d5ee95f18633d176cc/tools/osx/crosstool/cc_toolchain_config.bzl#L296-L311
meanwhile, we configure the
strip
action but don't attach anyflag_sets
, so I guess Bazel just thinks it can run it with no flags. https://github.com/carbon-language/carbon-lang/blob/2111b859da527d02c7eda7bcc1558b25a57f20f3/bazel/cc_toolchains/clang_cc_toolchain_config.bzl#L97-L100