-
-
Notifications
You must be signed in to change notification settings - Fork 667
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
Warning with bazel 0.3.1 #104
Comments
Thanks! |
I'm still getting this error with bazel 0.3.2 and 2e6cbd8.
Can this issue be reopened? |
Hmm. WARNING: Apparently a better solution is needed. On Sat, Oct 8, 2016 at 9:00 PM, Andy Hochhaus notifications@github.com
|
- Captures the absolute path of GOROOT at the time of toolchain configuration. This becomes necessary for cross-compile support (bazel-contrib#70). - Symlinks @io_bazel_rules_go_toolchain{src, bin, pkg} to platform toolchain paths to avoid workspace name mismatch warnings (closes bazel-contrib#104). - Introduces the RULES_GOROOT environment variable to allow use of a pre-existing go toolchain.
When using
rules_go
with bazel 0.3.1 I receive the following WARNING. This isn't a large issue for now, but it will cause an error in future versions.WARNING: /home/ahochhaus/.cache/bazel/_bazel_ahochhaus/9b0316414c69160d24362f2991b802bb/external/io_bazel_rules_go_toolchain/WORKSPACE:1: Workspace name in /home/ahochhaus/.cache/bazel/_bazel_ahochhaus/9b0316414c69160d24362f2991b802bb/external/io_bazel_rules_go_toolchain/WORKSPACE (@golang_linux_amd64) does not match the name given in the repository's definition (@io_bazel_rules_go_toolchain); this will cause a build error in future versions.
The text was updated successfully, but these errors were encountered: