On Nov 19 22:17, David Macek wrote:
> On 19. 11. 2015 20:36, Nellis, Kenneth wrote:
> > FWIW, my results are different:
> > 
> > $ printenv CYGWIN
> > winsymlinks:nativestrict
> > $ touch XXX
> > $ ln -s XXX YYY
> > $ ln -s YYY ZZZ
> > $ ls -l
> > total 0
> > -rw-r----- 1 knellis Domain Users 0 Nov 19 14:28 XXX
> > lrwxrwxrwx 1 knellis Domain Users 3 Nov 19 14:28 YYY -> XXX
> > lrwxrwxrwx 1 knellis Domain Users 3 Nov 19 14:28 ZZZ -> YYY
> > $ uname -svr
> > CYGWIN_NT-6.1 2.3.1(0.291/5/3) 2015-11-14 12:44
> > $
> 
> Weird. I also tried in the virtual root directory, in case cygdrive affects it, but no luck, still absolute paths.
> 
> I'm on Windows 10, if it makes any difference.

No, I'm on W10 either and it works for me as for Kenneth.  The path
evaluation in the function creating native symlinks tries to create
relative Windows paths if the incoming target path is relative, too.
Basically it compares the path prefixes, eliminates as much of
the path as possible and prepends "..\\" as required.

I don't see a reason why this shouldn't work for you, unless the
shell mangles the paths before passing them to the ln command (yes,
this really may happen with some shells depending on settings)


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat