Open michael-projectx opened 3 months ago
I'm having trouble to repro (assuming @//:third_party/folly/build_file.bazel
the file containing the cc_library
, and the build command is bazel build @folly//:header_only
). Maybe something else in your workspace is required to trigger the issue (e.g. a .bazelrc
file)? It might help to share the complete repro as a GitHub repository anyone can check out.
Let me try to put something together
Does this also happen to a build
folder under your source tree instead of an external repo?
I also run into this issue occasionally, although it seems to be non deterministic. I'm not 100% sure how to reproduce it.
@meteorcloudy, in my case it actually does throw the error for a folder in the source tree:
/srv/phantom/bazel/BUILD:117:10: no such package 'illusions': error globbing [inc/**] - [inc/build/**, inc/react/**] op=FILES: /srv/phantom/illusions/inc/phantom/scss/build (No such file or directory) and referenced by '//bazel:soar-tars'
Description of the bug:
I'm seeing the following failure:
When I check the output of
ls -al /home/vscode/.cache/bazel/_bazel_vscode/d9fd8dd9485b3d1d1994c3846baefa35/external/folly/folly/build
The directory does indeed exist:
Attempting to add an
exclude = ["folly/build/**"]
to theglob
rule doesn't seem to help.My complete build rule is as follows:
And the library is fetched using (in my
WORKSPACE
file):I'm on bazel version 7.0.2 on Mac OS
I have the same issue with another external dependency that also has a
build
folder. If I manually delete thebuild
folder or rename it to something else, then the build succeeds.It appears this has something to do with the case-insensitive filesystem on Mac OS because the same build works fine on Ubuntu. I've even attempted to create a new case-sensitive volume that I've symlinked my
.cache/bazel
directory to and the problem still persists.Which category does this issue belong to?
External Dependency
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
No response
Which operating system are you running Bazel on?
mac os
What is the output of
bazel info release
?release 7.0.2
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse HEAD
?No response
Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.
No response
Have you found anything relevant by searching the web?
No
Any other information, logs, or outputs that you want to share?
No response