Sorry, it's attached.
Another data point: These problems happen when running make or rsync
from a Windows console running cmd.exe. If I start a bash session (just
by running bash in my Windows console), then run "make clean", it works
fine. Same for rsync: run it from cmd.exe, ssh is not fou
On 01 January 2007 22:24, Ned Batchelder wrote:
> Sorry, it's attached.
>
> Another data point: These problems happen when running make or rsync
> from a Windows console running cmd.exe. If I start a bash session (just
> by running bash in my Windows console), then run "make clean", it works
> f
That sounds like a good theory, but I don't think it's it. First, I
don't have a .bashrc or .bash_profile (I don't actually use bash on
Windows, it was a diagnostic technique). Second, from the cmd.exe
window, the commands make and rsync are looking for work fine. The path
in cmd.exe and bash
Right after sending my last message, I finally noticed what was
different about the cmd.exe path and the bash path. It wasn't the
spaces, but the Windows path has an empty element in it:
...;C:\Program Files\Common Files\GTK\2.0\bin;;C:\Program
Files\Common Files\Adobe\AGL;...
That seems
4 matches
Mail list logo
