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 of c:\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 get
127 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).
@meteorcloudy can you help with this? Thanks.
On Mon, Oct 10, 2016 at 11:39 AM, Peter Mounce [email protected]
wrote:
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 of c:\windows\system32
(so it's not bash-on-windows interference). The exe has the +x permission
in msys2.When I try
/bazel version in msys2 and powershell, I get
- no output to the console,
- exit code 127 in msys2, -1073741511 in powershell.
Can you try in cmd.exe?
(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
https://github.com/userzimmermann/choco-packages/issues/7).—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/bazel/issues/1919, or mute the thread
https://github.com/notifications/unsubscribe-auth/AExrX6Efizms3WTM0sASBwAL43HdcuScks5qygfmgaJpZM4KSYoC
.
Google Germany GmbH
_Erika-Mann-Straße 33, 80636 München, Germany_
In cmd I get output:
C:\Users\Pete\bazel {git}{hg}
{lamb} c:\Users\Pete\Downloads\bazel-0.3.2.exe info
Error: mkdir('/var/tmp/_bazel_Pete'): Permission denied
My TMP (and TEMP) environment variables are set to C:\Users\Pete\AppData\Local\Temp.
Very strange. I cannot repro this. Can you share your environment variables? (output of set in cmd.exe)?
Sure. Below.
I'm on Windows 10, I have Bash-on-Windows installed, I'm up to date with updates.
c:\src\s\e {git}{hg}
{lamb} set
ALLUSERSPROFILE=C:\ProgramData
ANDROID_SDK_HOME=C:\Android
ANSICON=117x10000 (117x60)
ANSICON_DEF=7
APPDATA=C:\Users\Pete\AppData\Roaming
AppsRoot=D
architecture=64
ATLAS_HOME=C:\Applications\Atlassian\atlassian-plugin-sdk-6.2.9
BAZEL_PYTHON=c:\tools\python2\python.exe
BAZEL_SH=c:/tools/msys64/usr/bin/bash.exe
ChocolateyBinRoot=\bin
ChocolateyInstall=C:\ProgramData\chocolatey
ChocolateyLastPathUpdate=Thu Oct 6 09:41:00 2016
ChocolateyToolsLocation=C:\tools
chocolatey_bin_root=\bin
CLASSPATH=.;
CLINK_DIR=C:\Program Files (x86)\clink\0.4.7
CMDER_ROOT=C:\tools\cmder
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
COMPUTERNAME=PETEMOUNCE-WIN-
ComSpec=C:\WINDOWS\system32\cmd.exe
ConEmuANSI=ON
ConEmuAnsiLog=
ConEmuBackHWND=0x003105FA
ConEmuBaseDir=C:\tools\cmder\vendor\conemu-maximus5\ConEmu
ConEmuBuild=161002
ConEmuDir=C:\tools\cmder\vendor\conemu-maximus5
ConEmuDrawHWND=0x001B05BA
ConEmuDrive=C:
ConEmuHooks=Enabled
ConEmuHWND=0x000D04FC
ConEmuIsAdmin=ADMIN
ConEmuPalette=Monokai
ConEmuPID=3036
ConEmuServerPID=1876
ConEmuTask={cmd::Cmder as Admin}
ConEmuWorkDir=C:\Users\Pete
ConEmuWorkDrive=C:
GIT_INSTALL_ROOT=C:\Program Files\Git
GOROOT=C:\tools\go
GRADLE_HOME=C:\ProgramData\chocolatey\lib\gradle\tools\gradle-3.0
GTK_BASEPATH=C:\Program Files (x86)\GtkSharp\2.12\
HOME=C:\Users\Pete
HOMEDRIVE=C:
HOMEPATH=\Users\Pete
IMPROBABLE_TOOLS=C:\improbable\tools
JAVA_HOME=C:\Program Files\Java\jdk1.8.0_102
LOCALAPPDATA=C:\Users\Pete\AppData\Local
LOGONSERVER=\\PETEMOUNCE-WIN-
M2=C:\tools\apache-maven-3.3.9\bin
M2_HOME=C:\tools\apache-maven-3.3.9
M2_REPO=C:\Users\Pete\.m2
MAVEN_OPTS=-Xms256m
NUMBER_OF_PROCESSORS=8
OS=Windows_NT
Path=C:\tools\cmder\bin;C:\Program Files\Git\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\usr\share\vim\vim74;C:\tools\cmder\vendor\conemu-maximus5\ConEmu\Scripts;C:\ProgramData\chocolatey\bin;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;c:\tools\msys64\usr\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\ATI
Technologies\ATI.ACE\Core-Static;C:\Program Files\Puppet Labs\Puppet\bin;C:\Program Files\Unity\Editor;C:\Program Files (x86)\MSBuild\14.0\Bin;C:\tools\spatial;C:\tools\protoc;C:\improbable\it\bin;C:\Program Files\7-Zip;C:\Program Files\OpenVPN\bin;C:\improbable\tools\latest\windows;C:\tools\python2;C:\tools\go\bin;C:\tools\python2\Scripts;C:\Program Files (x86)\CMake\bin;C:\Program Files (x86)\sbt\bin;C:\Program Files (x86)\GNU\GnuPG\pub;C:\tools\phabricator\arcanist\bin;C:\Android;C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance
Toolkit\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files (x86)\GtkSharp\2.12\bin;C:\Program Files\Amazon\AWSCLI\;C:\Users\Pete\AppData\Local\atom\bin;C:\Program Files (x86)\Microsoft VS Code\bin;C:\tools\php;C:\PROGRA~2\Oracle\VirtualBox;C:\tools\cmder;C:\tools\cmder\bin;C:\tools\cmder\vendor\conemu-maximus5\ConEmu\Scripts;C:\tools\cmder\vendor\conemu-maximus5;C:\tools\cmder\vendor\conemu-maximus5\ConEmu;C:\Users\Pete\.dnx\bin;C:\ProgramData\chocolatey\lib\Elixir/bin;C:\Program Files (x86)\GitExtensions\;C:\Program Files (x86)\scala\bin;C:\Program Files\dotnet\;C:\Program Files (x86)\Gow\bin;C:\Program Files (x86)\NUnit.org\nunit-console;C:\ProgramData\chocolatey\lib\Elixir/bin;C:\Program Files\Git\cmd;C:\Program Files\nodejs\;C:\HashiCorp\Vagrant\bin;C:\Program Files\Git\bin;C:\Applications\Atlassian\atlassian-plugin-sdk-6.2.9\bin;C:\Users\Pete\AppData\Roaming\npm;C:\tools\cmder\
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
PLINK_PROTOCOL=ssh
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 70 Stepping 1, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=4601
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
PROMPT=$E[1;32;40m$P$S{git}{hg}$S$_$E[1;30;40m{lamb}$S$E[0m
PSModulePath=C:\Users\Pete\Documents\WindowsPowerShell\Modules
PUBLIC=C:\Users\Public
SBT_HOME=C:\Program Files (x86)\sbt\
SVN_SSH=C:\\Program Files\\Git\\bin\\ssh.exe
SystemDrive=C:
SystemRoot=C:\WINDOWS
TEMP=C:\Users\Pete\AppData\Local\Temp
TERM=cygwin
TMP=c:\temp
USERDOMAIN=PETEMOUNCE-WIN-
USERDOMAIN_ROAMINGPROFILE=PETEMOUNCE-WIN-
USERNAME=Pete
USERPROFILE=C:\Users\Pete
VBOX_MSI_INSTALL_PATH=C:\Program Files\Oracle\VirtualBox\
VS140COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools\
VSSDK140Install=C:\Program Files (x86)\Microsoft Visual Studio 14.0\VSSDK\
windir=C:\WINDOWS
WIX=C:\Program Files (x86)\WiX Toolset v3.10\
Here is an idea: looks like in your PATH you have both C:\Program Files\Git\bin and c:\tools\msys64\usr\bin. Git-on-windows is an msys program too :(.
Can you try removing the first one from the PATH? (Welcome to dll hell)
I've trimmed various things from the PATH of cmd, and now I get a different error, in a modal popup.
error:
bazel-0.3.2.exe - Entry Point Not Found
---------------------------
The procedure entry point __locale_ctype_ptr could not be located in the dynamic link library C:\Users\Pete\Downloads\bazel-0.3.2.exe.
---------------------------
OK
---------------------------
shell:
C:\Users\Pete\bazel>echo %PATH%
c:\tools\msys64\usr\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\MSBuild\14.0\Bin;C:\tools\spatial;C:\tools\protoc;C:\improbable\it\bin;C:\improbable\tools\latest\windows;C:\tools\python2;C:\tools\go\bin;C:\tools\python2\Scripts;C:\Program Files (x86)\CMake\bin;C:\Program Files (x86)\sbt\bin;C:\Program Files (x86)\GNU\GnuPG\pub;C:\tools\phabricator\arcanist\bin;C:\Android;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;
C:\Users\Pete\bazel>..\Downloads\bazel-0.3.2.exe version
[error pops up]
Hmm ok, I've seen that happening with the old versions of msys2. Which one do you have?
Apparently I have msys2 20150916.0.1, but I'm not sure I believe that. I'm going to remove it and reinstall .
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 bazel version and bazel info work as expected from msys2.
# To the extent possible under law, the author(s) have dedicated all
# copyright and related and neighboring rights to this software to the
# public domain worldwide. This software is distributed without any warranty.
# You should have received a copy of the CC0 Public Domain Dedication along
# with this software.
# If not, see <http://creativecommons.org/publicdomain/zero/1.0/>.
# ~/.bash_profile: executed by bash(1) for login shells.
# The copy in your home directory (~/.bash_profile) is yours, please
# feel free to customise it to create a shell
# environment to your liking. If you feel a change
# would be benifitial to all, please feel free to send
# a patch to the msys2 mailing list.
# User dependent .bash_profile file
# source the users bashrc if it exists
if [ -f "${HOME}/.bashrc" ] ; then
source "${HOME}/.bashrc"
fi
# Set PATH so it includes user's private bin if it exists
# if [ -d "${HOME}/bin" ] ; then
# PATH="${HOME}/bin:${PATH}"
# fi
# Set MANPATH so it includes users' private man if it exists
# if [ -d "${HOME}/man" ]; then
# MANPATH="${HOME}/man:${MANPATH}"
# fi
# Set INFOPATH so it includes users' private info if it exists
# if [ -d "${HOME}/info" ]; then
# INFOPATH="${HOME}/info:${INFOPATH}"
# fi
export GIT_SSH=C:\\ProgramData\\chocolatey\\bin\\plink.EXE
export PATH=/c/tools/go/bin:$PATH
export PATH=/c/Program\ Files\ \(x86\)/CMake/bin:$PATH
export PATH=/c/Program\ Files\ \(x86\)/sbt/bin:$PATH
export PATH=/C/Program\ Files/Java/jdk1.8.0_102/bin:$PATH
export BAZEL_SH=c:/tools/msys64/usr/bin
export BAZEL_PYTHON=c:/tools/python2/python.exe
export BAZEL_VS="C:/Program Files (x86)/Microsoft Visual Studio 14.0"
In powershell, I get expected behaviour. In cmd, I get, still, Error: mkdir('/var/tmp/_bazel_Pete'): Permission denied
Check you PATH in cmd?
I've got success via the chocolatey-installed bazel, too, though I (unsurprisingly) had to add /c/ProgramData/chocolatey/bin to PATH over in msys2 .bash_profile.
In cmd, my PATH is:
C:\tools\cmder\bin;C:\Program Files\Git\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\usr\share\vim\vim74;C:\tools\cmder\vendor\conemu-maximus5\ConEmu\Scripts;C:\ProgramData\chocolatey\bin;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;c:\tools\msys64\usr\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\Puppet Labs\Puppet\bin;C:\Program Files\Unity\Editor;C:\Program Files (x86)\MSBuild\14.0\Bin;C:\tools\spatial;C:\tools\protoc;C:\improbable\it\bin;C:\Program Files\7-Zip;C:\Program Files\OpenVPN\bin;C:\improbable\tools\latest\windows;C:\tools\python2;C:\tools\go\bin;C:\tools\python2\Scripts;C:\Program Files (x86)\CMake\bin;C:\Program Files (x86)\sbt\bin;C:\Program Files (x86)\GNU\GnuPG\pub;C:\tools\phabricator\arcanist\bin;C:\Android;C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files (x86)\GtkSharp\2.12\bin;C:\Program Files\Amazon\AWSCLI\;C:\Users\Pete\AppData\Local\atom\bin;C:\Program Files (x86)\Microsoft VS Code\bin;C:\tools\php;C:\PROGRA~2\Oracle\VirtualBox;C:\tools\cmder;C:\tools\cmder\bin;C:\tools\cmder\vendor\conemu-maximus5\ConEmu\Scripts;C:\tools\cmder\vendor\conemu-maximus5;C:\tools\cmder\vendor\conemu-maximus5\ConEmu;C:\Users\Pete\.dnx\bin;C:\ProgramData\chocolatey\lib\Elixir/bin;C:\Program Files (x86)\scala\bin;C:\Program Files\dotnet\;C:\Program Files (x86)\NUnit.org\nunit-console;C:\ProgramData\chocolatey\lib\Elixir/bin;C:\Program Files\nodejs\;C:\HashiCorp\Vagrant\bin;C:\Program Files\Git\bin;C:\Applications\Atlassian\atlassian-plugin-sdk-6.2.9\bin;C:\Users\Pete\AppData\Roaming\npm;C:\tools\cmder\
I'll try again in a sec after trimming suspect entries out.
After doing that, I get expected behaviour. PATH that allowed success is:
c:\tools\msys64\usr\bin;C:\ProgramData\chocolatey\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Puppet Labs\Puppet\bin;C:\Program Files\Unity\Editor;C:\Program Files (x86)\MSBuild\14.0\Bin;C:\tools\spatial;C:\tools\protoc;C:\improbable\it\bin;C:\Program Files\7-Zip;C:\Program Files\OpenVPN\bin;C:\improbable\tools\latest\windows;C:\tools\python2;C:\tools\go\bin;C:\tools\python2\Scripts;C:\Program Files (x86)\CMake\bin;C:\Program Files (x86)\sbt\bin;C:\Program Files (x86)\GNU\GnuPG\pub;C:\tools\phabricator\arcanist\bin;C:\Android;C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files (x86)\GtkSharp\2.12\bin;C:\Program Files\Amazon\AWSCLI\;C:\Users\Pete\AppData\Local\atom\bin;C:\Program Files (x86)\Microsoft VS Code\bin;C:\tools\php;C:\PROGRA~2\Oracle\VirtualBox;C:\tools\cmder;C:\tools\cmder\bin;C:\tools\cmder\vendor\conemu-maximus5\ConEmu\Scripts;C:\tools\cmder\vendor\conemu-maximus5;C:\tools\cmder\vendor\conemu-maximus5\ConEmu;C:\Users\Pete\.dnx\bin;C:\ProgramData\chocolatey\lib\Elixir/bin;C:\Program Files (x86)\scala\bin;C:\Program Files\dotnet\;C:\Program Files (x86)\NUnit.org\nunit-console;C:\ProgramData\chocolatey\lib\Elixir/bin;C:\Program Files\nodejs\;C:\HashiCorp\Vagrant\bin;C:\Applications\Atlassian\atlassian-plugin-sdk-6.2.9\bin;C:\Users\Pete\AppData\Roaming\npm;C:\tools\cmder\
I'll revert, then remove entries one by one to see if I can confirm it being git's msys...
Again, C:\Program Files\Git\bin before c:\tools\msys64\usr\bin. So it loads the wrong msys-2.0.dll.
Yup, confirmed. I moved the entries involving git to the end of PATH and with that, I get expected behaviour.
C:\tools\cmder\bin;C:\tools\cmder\vendor\conemu-maximus5\ConEmu\Scripts;C:\ProgramData\chocolatey\bin;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;c:\tools\msys64\usr\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\Puppet Labs\Puppet\bin;C:\Program Files\Unity\Editor;C:\Program Files (x86)\MSBuild\14.0\Bin;C:\tools\spatial;C:\tools\protoc;C:\improbable\it\bin;C:\Program Files\7-Zip;C:\Program Files\OpenVPN\bin;C:\improbable\tools\latest\windows;C:\tools\python2;C:\tools\go\bin;C:\tools\python2\Scripts;C:\Program Files (x86)\CMake\bin;C:\Program Files (x86)\sbt\bin;C:\Program Files (x86)\GNU\GnuPG\pub;C:\tools\phabricator\arcanist\bin;C:\Android;C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files (x86)\GtkSharp\2.12\bin;C:\Program Files\Amazon\AWSCLI\;C:\Users\Pete\AppData\Local\atom\bin;C:\Program Files (x86)\Microsoft VS Code\bin;C:\tools\php;C:\PROGRA~2\Oracle\VirtualBox;C:\tools\cmder;C:\tools\cmder\bin;C:\tools\cmder\vendor\conemu-maximus5\ConEmu\Scripts;C:\tools\cmder\vendor\conemu-maximus5;C:\tools\cmder\vendor\conemu-maximus5\ConEmu;C:\Users\Pete\.dnx\bin;C:\ProgramData\chocolatey\lib\Elixir/bin;C:\Program Files (x86)\scala\bin;C:\Program Files\dotnet\;C:\Program Files (x86)\NUnit.org\nunit-console;C:\ProgramData\chocolatey\lib\Elixir/bin;C:\Program Files\nodejs\;C:\HashiCorp\Vagrant\bin;C:\Program Files\Git\bin;C:\Applications\Atlassian\atlassian-plugin-sdk-6.2.9\bin;C:\Users\Pete\AppData\Roaming\npm;C:\tools\cmder\;C:\Program Files\Git\bin;C:\Program Files\Git\usr\bin;C:\Program Files\Git\usr\share\vim\vim74
Closing this, landing a patch to update windows.md with these findings :)
Most helpful comment
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
bazel versionandbazel infowork as expected from msys2.