On 2/2/2011 3:51 PM, marco atzeri wrote:
> On Wed, Feb 2, 2011 at 9:45 PM, Corinna Vinschen wrote:
>> On Feb 1 19:37, Ralf Wildenhues wrote:
>>> The following fails for me (and web and list search haven't been
helpful):
>>> $ mkdir ...
>>> $ cd ...
>>> $ cp /usr/bin/ls.exe .
>>> $ ./ls.exe
>>> bash: ./ls.exe: No such file or directory
>>> Same with code compiled in this directory.
>>> Is this a bug or by design?
>> Works fine for me:
>> $ uname -a
>> CYGWIN_NT-6.1 vmbert7 1.7.7(0.230/5/3) 2010-08-31 09:58 i686 Cygwin
>> $ cd tmp
>> $ mkdir ...
>> $ cd ...
>> $ cp /usr/bin/ls.exe .
>> $ ./ls
>> ls.exe
>> I tried on NTFS, Samba and NFS.
>> Corinna
> not working also here:
> $ uname -a
> CYGWIN_NT-5.1 1.7.8s(0.235/5/3) 20110130 23:04:08 i686 Cygwin
> $ ./ls.exe
> bash: ./ls.exe: No such file or directory
> $ ./ls
> bash: ./ls: No such file or directory
> $ ls -l
> total 128
> -rwxr-xr-x+ 1 Marco Administrators 129550 Feb 2 20:55 ls.exe
Works for me on NTFS.
$ uname -a
CYGWIN_NT-6.0-WOW64 GW2 1.7.7(0.230/5/3) 2010-08-31 09:58 i686 Cygwin
Conceivably, this could be a bug that might be important, but I
have to ask:
How good an idea is it to name a directory '...'?
Let me take a crack at an answer:
About as good an idea as embedding spaces in PATH names!
I.e, don't do it unless Mr. Bill holds a gun to your head!
Lee
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
