-
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
bazel 0.3.2 gives no output on windows #1919
Comments
@meteorcloudy can you help with this? Thanks. |
On Mon, Oct 10, 2016 at 11:39 AM, Peter Mounce [email protected]
Google Germany GmbH |
In cmd I get output:
My |
Very strange. I cannot repro this. Can you share your environment variables? (output of |
Sure. Below. I'm on Windows 10, I have Bash-on-Windows installed, I'm up to date with updates.
|
Here is an idea: looks like in your PATH you have both |
I've trimmed various things from the error:
shell:
|
Hmm ok, I've seen that happening with the old versions of msys2. Which one do you have? |
Apparently I have |
Ok, that is old(-ish). We build against 20160205. |
I've just installed http://repo.msys2.org/distrib/x86_64/msys2-x86_64-20160921.exe cleanly, followed the windows setup for bazel (bash_profile below), and
|
In powershell, I get expected behaviour. In cmd, I get, still, |
Check you |
I've got success via the chocolatey-installed bazel, too, though I (unsurprisingly) had to add |
In cmd, my PATH is:
I'll try again in a sec after trimming suspect entries out. After doing that, I get expected behaviour. PATH that allowed success is:
I'll revert, then remove entries one by one to see if I can confirm it being git's msys... |
Again, |
Yup, confirmed. I moved the entries involving git to the end of PATH and with that, I get expected behaviour.
|
Closing this, landing a patch to update windows.md with these findings :) |
As discovered in #1919. -- MOS_MIGRATED_REVID=135677514
As discovered within bazelbuild#1919, the order of entries in the `PATH` matters, and is hard to diagnose when it's wrong.
As discovered within bazelbuild#1919, the order of entries in the `PATH` matters, and is hard to diagnose when it's wrong.
I'm trying out the bazel 0.3.2 release via both the chocolatey package and a naked download. I've checked the hashes of my downloaded binary, and they match. The msys2 DLL is in my Windows
PATH
ahead ofc:\windows\system32
(so it's not bash-on-windows interference). The exe has the +x permission in msys2.When I try
<full path>/bazel version
in msys2 and powershell, I get127
in msys2,-1073741511
in powershell.(I'm able to install via chocolatey despite the msys2 broken dependency because I built and installed a fixed version of that locally - the PR to fix that has been merged, but the resulting package has not been pushed yet, see userzimmermann/choco-packages#7).
The text was updated successfully, but these errors were encountered: