Open MarkShark99 opened 2 months ago
I can reproduce this issue locally. fruit
does have a bit strange Bazel setup with symlinks https://github.com/google/fruit/tree/master/extras/bazel_root/third_party/fruit, I wonder if that's related.
But it's strange building a target directly would succeed but as a dependency would fail. /cc @pzembrod @comius
Was looking into this a bit more last night and found that the library file referenced within libfruit-config-base_link.a-2.params
doesn't actually exist which is what causes that specific error message. Not sure why it's not being created as expected.
Description of the bug:
I'm attempting to build the
//main
target of my example project (https://github.com/MarkShark99/bazel-test), which just compiles a simplecc_binary
that depends on fruit. On Linux it compiles and runs correctly, but on MacOS (Apple Silicon) runningbazel build -s //main
results in the following error:Compiling
@fruit//third_party/fruit
works as intended.Which category does this issue belong to?
C++ Rules, External Dependency
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Perform the following on MacOS (Apple Silicon):
bazel build //main
Which operating system are you running Bazel on?
MacOS Sonoma 14.6.1
What is the output of
bazel info release
?release 7.3.1
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.N/A
What's the output of
git remote get-url origin; git rev-parse HEAD
?If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
N/A
Have you found anything relevant by searching the web?
rules_foreign_cc
for this project.Any other information, logs, or outputs that you want to share?
Xcode Command Line Tools version:
15.3.0.0.1.1708646388