-
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
new_git_repository fails if repo already contains a BUILD directory entry #2226
Comments
We have the same problem and mostly only purge the |
@gjasny Can you please comment back with a clearer way to reproduce the issue, possibly via a repository I can clone and try to build? It'll really simplify figuring out what the issue is and how to address it. Thanks! |
Use macOS and make sure the current file system is not case-insensitive:
Use bazel 0.4.2
Clone
Fetch modular boost
If you look into
Hope that help and thanks for looking into it! -Gregor |
Awesome, thanks, I'll look into it. |
Sent https://bazel-review.googlesource.com/7850 to address this. |
…linked/new build file, which has less changes of causing conflicts. Fixes #2226." This reverts commit 2f31d60. Re-open #2226. -- Change-Id: I7f223df4bb239daf8c306955e92f817310e6cd4f Reviewed-on: https://cr.bazel.build/7950 PiperOrigin-RevId: 142257579 MOS_MIGRATED_REVID=142257579
Re-opening until I can fix rules_go, release that, update rules_webtesting and buildifier, and then re-submit this. |
Hello,
While running the fetch common in a checkout of bazel-boost I get the same error as described here: new_git_repository. This is because my macOS home directory is case-insensitive by default and the modular boost repos all contain a
build
directory in their root. Therefore placing aBUILD
symlink in the repository root fails.How could I work-around that problem? Imagine a 3rd party repository contains a broken or unsuitable BUILD file that needs to be replaced.
Thanks,
Gregor
The text was updated successfully, but these errors were encountered: