On Tuesday 02 June 2009 07:43:30 Peter wrote:
> I noticed that if I run from c:\windows\syswow64\cmd,
IIRC, this is precisely what msys.bat *ensures* that you do, so...
> bash followed by ls. it will work.
...we would expect this to be the case.
> for microsoft xp 64, the default cmd runs from
And, this is *known* to not support MSYS, when running on w64;
furthermore, the symptoms of failure were already known to be those
which you described for your failure case.
Sorry to be brutally frank here, but it seems that you were trying
to be too clever for your own good, by bypassing msys.bat for MSYS
startup. That may be ok, when you understand what it is that you
are bypassing. When you do it without that understanding, you
really shouldn't be surprised when you break it.
Do please note that msys.bat is the *only* officially supported
method of starting an MSYS shell session. If you must bypass it,
(and I do so myself, when I start my MSYS sessions from within a
Console-2 container on w32), then you really should ensure that
your alternative startup method does exactly the same as msys.bat
would have done. FWIW, your postings to date suggest that you are
also omitting the `--login' and `-i' flags, which really should be
considered mandatory for the top level shell in the session,
regardless of whether that is invoked as
/path/to/sh.exe --login -i
/path/to/bash.exe --login -i
Failure to specify these flags will likely result in your shell
environment being improperly configured, potentially leading to
more unexpected behaviour; (I also seem to recall some quirky
effect, if the order of the flags is reversed, but I may be
mistaken, and I do not feel inclined to reinvestigate now).