symbolic link curiousity in 3.6.0

[Corinna Vinschen]

On Mar 25 02:25, Mark Geisert via Cygwin wrote:
> This occurs on the released 3.6.0 but not in 3.6.0 test build 327.
> 
> /tmp ls foo bar
> ls: cannot access 'foo': No such file or directory
> ls: cannot access 'bar': No such file or directory
> 
> /tmp ln -s foo bar
> 
> /tmp ls foo bar
> ls: cannot access 'foo': No such file or directory
> bar@
> 
> /tmp ls -l foo bar
> ls: cannot access 'foo': No such file or directory
> ls: bar: Not supported
> lrwxrwxrwx 1 Mark None 3 Mar 25 02:08 bar -> foo
> 
> The spurious "Not supported" message is new and curious.
> I could not see anything obvious in an strace of the command.

This is weird.  I just tried the same with 3.6.0-1:

  $ cd /tmp
  $ ls -l foo bar
  ls: cannot access 'foo': No such file or directory
  ls: cannot access 'bar': No such file or directory
  $ ln -s foo bar
  $ ls foo bar
  ls: cannot access 'foo': No such file or directory
  bar
  $ ls -l foo bar
  ls: cannot access 'foo': No such file or directory
  lrwxrwxrwx 1 corinna vinschen 3 Mar 25 10:46 bar -> foo

That's the expected output.

Your ls output shows an at-sign after the name "bar".  You're
probably using an alias for ls including the -F option.  Can you
paste your alias here?

Are you using a specific setting of the CYGWIN env var including
a symlink type?

Can you try intermediate test release between 327 and -1?


Corinna