-
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
Windows: Bazel requires MSYS for every command #6462
Comments
This is a bad first-time experience. See #5254 |
Fixes bazelbuild#6462 Change-Id: I6792b6d3be7ea0d31154a4c3cb9983c601689301
I get the same error: So the only way to run Bazel on Windows is to install MSYS2 bash and disable the path conversion? The doc says to prefer Command Prompt or PowerShell: https://docs.bazel.build/versions/master/windows.html#running-bazel-msys2-shell-vs-command-prompt-vs-powershell |
@robisim74 : try Bazel 0.21, that should no longer complain about a missing MSYS2 Bash. Please let me know if you still find problems with it! |
Ok, thanks! I will try to install v0.21 (still not published on npm) and let you know. |
@laszlocsomor I tried to download version 0.21 directly on my machine in For the moment, I installed MSYS2 bash to work. |
@robisim74 : You're right. I never merged the corresponding PR (#6582) because it broke some tests. Installing MSYS2 is the best "workaround" for now. Sorry about that. |
Bazel 0.23 still complains about missing MSYS2:
|
Bazel no longer reports an error if it fails to locate Bash. This allows "bazel info release" to work even in absence of Bash. To clarify, Bazel still requires Bash to build rules that depend on Bash. This PR simply removes the fatal error Bazel used to display if Bash was missing even when Bash was not required. Fixes bazelbuild#6462
Description of the problem / feature request:
On a fresh Windows 10 installation with only Bazel 0.18.0 and MSVC redistributable DLLs [1] and without MSYS, running any command in a minimal workspace (just an empty WORKSPACE file) requires MSYS bash.
[1] https://download.microsoft.com/download/9/3/F/93FCF1E7-E6A4-478B-96E7-D4B285925B00/vc_redist.x64.exe
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
On a fresh Windows 10:
What operating system are you running Bazel on?
Windows Server 2016 (v1607)
The text was updated successfully, but these errors were encountered: