From: Ray D. <min...@gm...> - 2014-04-27 21:20:46
|
> I'm running c:/MinGW64/msys64/bin/bash.exe, with c:/MinGW64/msys64/bin first in PATH. Please read and follow the instructions on this wiki page: http://sourceforge.net/p/msys2/wiki/MSYS2%20installation/ You should run one of mingw32_shell.bat, mingw64_shell.bat or msys2_shell.bat, or at least do everything important that those batch files do (setting MSYSTEM, running sh.exe with --login -i). Also, mintty works better than cmd.exe at present due to xterm emulation, this is something that we are keen to fix. > Ah; that says /mingw64/* but it did _not_ put them there. Are you sure about that? It definitely should have put them there. Obviously discussion of paths is trickier since MSYS has it's own version of each Windows path. For me: pacman -Ql mingw-w64-x86_64-make .. mingw-w64-x86_64-make /mingw64/bin/mingw32-make.exe .. and: ls -l /mingw64/bin/mingw32-make.exe -rwxr-xr-x 1 ray None 222723 Jan 13 04:37 /mingw64/bin/mingw32-make.exe > Msys2 seems to be very confused about what "/" means. 'mount' says: It's not 'confused' as such there are just two versions, the same as a bind mount in Linux. This is an unfortunate layout that we inherited from the original msys and it's a shame that we didn't correct it, but it can be lived with generally. Fixing it would mean rebuilding every MSYS2 package. > c:/MinGW64/msys64/mingw64; that doesn't exist. This indicates that you didn't run the startup scripts because you didn't run "sh.exe --login -i". |