This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: `CYGWIN=winsymlinks:nativestrict`, `ln -s target link` fails if target doesn't exist
- From: Gene Pavlovsky <gene dot pavlovsky at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 29 Apr 2016 14:34:18 +0300
- Subject: Re: `CYGWIN=winsymlinks:nativestrict`, `ln -s target link` fails if target doesn't exist
- Authentication-results: sourceware.org; auth=none
- References: <CAPTiy3NUXprQL6V0+Njc2L7XfhpqtC7oWFwNMhOEFZ2OZmddoQ at mail dot gmail dot com> <1606116423 dot 20160429020650 at yandex dot ru>
> > POSIX says a symlink to a missing target is perfectly well-defined (you
> > can't stat() through it, but you can readlink() it). But Windows native
> > symlinks can't do that. So the problems you are encountering all stem
> > from the fact that you are trying to make Windows do something it can't.
>
> My initial reaction was that, too, but I tried mklink (CMD internal command)
>
> > mklink x y
>
> and it created the symlink in the empty directory just fine.
This is my point exactly. Windows dangling symlinks can be created as
easily as in UNIX.
At least this is the case on my Win7 x64.
--
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