[Mingw-msys] Re: something wrong with my MSYS installation?

[wolfgang <ora...@we...>]

Earnie Boyd <earnie@...> writes:

> The value of your PATH variable looks suspiciously incorrect.  It 
> begins with c:/opt rather than /c/opt.

Yes, but - have a look at this session:

$ type cl
sh: type: cl: not found

geronimo@FRISCO ~
$ type -a find 
find is /bin/find
find is /c/WINDOWS/system32/find

geronimo@FRISCO ~
$ type -a grep 
grep is /bin/grep

$ echo $PATH
.:/usr/local/bin:/mingw/bin:/bin:/c/WINDOWS/system32:/c/WINDOWS:\
/c/WINDOWS/System32/Wbem

Ok, there's no C++ compiler (cl) around, and PATH does not contain 
blanks. Indeed there's a find, but it's behind /bin.

Then:
$ PATH='c:/opt/visual cxx/2003/bin':$PATH

$ echo $PATH | od -ta
0000000   c   :   /   o   p   t   /   v   i   s   u   a   l  sp   c   x
0000020   x   /   2   0   0   3   /   b   i   n   :   .   :   /   u   s
0000040   r   /   l   o   c   a   l   /   b   i   n   :   /   m   i   n
0000060   g   w   /   b   i   n   :   /   b   i   n   :   /   c   /   W
0000100   I   N   D   O   W   S   /   s   y   s   t   e   m   3   2   :
0000120   /   c   /   W   I   N   D   O   W   S   :   /   c   /   W   I
0000140   N   D   O   W   S   /   S   y   s   t   e   m   3   2   /   W
0000160   b   e   m  nl
0000164

$ type -a cl
cl is /opt/visual cxx/2003/bin/cl

MSYS is able to locate compiler cl because there's a mount from '/opt'
to "c:/opt" where compiler is installed.

$ type -a find
find is /bin/find
find is /c/WINDOWS/system32/find

Still the same "find" order.

$ grep
Usage: grep [OPTION]... PATTERN [FILE]...
Try `grep --help' for more information.

$ find -type f -exec grep x '{}' \;
find: grep: No such file or directory
[..]

The problem disappears setting the path like

 $ PATH='/opt/visual cxx/2003/bin':$PATH          ; or
 $ PATH='/c/opt/visual cxx/2003/bin':$PATH        ; or
 $ PATH=$PATH:'c:/opt/visual cxx/2003/bin'
 
I agree that the path's value looks incorrect. On the other side,
a path like 'c:/opt/visual cxx/2003/bin:.:/usr/local/bin:[..]' is
nothing more than

  c
  /opt/visual cxx/2003/bin
  .
  /usr/local/bin
  [..]

which appears perfectly legal ("c" does not need to exist).

I made some further tests and I noticed that the space is not the
problem. It's a problem with the "c:/opt" ..

I removed my /opt mount from /etc/fstab (actually I removed 
/etc/fstab).

Then I have:
$ find -type f -exec grep x '{}' \;
=> works

PATH=c:/opt/python/240:$PATH

$ echo $PATH | od -ta
0000000   c   :   /   o   p   t   /   p   y   t   h   o   n   /   2   4
0000020   0   :   .   :   /   u   s   r   /   l   o   c   a   l   /   b
0000040   i   n   :   /   m   i   n   g   w   /   b   i   n   :   /   b
0000060   i   n   :   /   c   /   W   I   N   D   O   W   S   /   s   y
0000100   s   t   e   m   3   2   :   /   c   /   W   I   N   D   O   W
0000120   S   :   /   c   /   W   I   N   D   O   W   S   /   S   y   s
0000140   t   e   m   3   2   /   W   b   e   m  nl
0000153

$ find -type f -exec grep x '{}' \;
find: grep: No such file or directory

$  type -a find
find is /bin/find
find is /c/WINDOWS/system32/find

geronimo@FRISCO ~
$  type -a grep
grep is /bin/grep



(Btw, does someone know how to get rid of /c/WINDOWS/system32/find? It
gets magically created again after I deleted it????)

Cheers,
Wolfgang.