This is the mail archive of the
mailing list for the Cygwin project.
Re: Native symbolic links to non-existent targets (possible bug?)
- From: Brian Ericson <bericson at ptc dot com>
- To: <cygwin at cygwin dot com>
- Date: Tue, 30 Sep 2014 16:20:23 -0500
- Subject: Re: Native symbolic links to non-existent targets (possible bug?)
- Authentication-results: sourceware.org; auth=none
- References: <542A219C dot 6070402 at ptc dot com>
Looking at the source, I may be able to address my own questions/points.
On 09/29/2014 10:21 PM, Brian Ericson wrote:
Cygwin appears to ignore "winsymlinks:native" when asked to create a
symbolic link to a non-existent target, reverting to its "magic header"
This is true...
According to the following comment at line 1646 of path.cc (see
Shouldn't Cygwin honor "winsymlinks:native" even with the target does
/* If the symlink target doesn't exist, don't create native symlink.
Otherwise the directory flag in the symlink is potentially wrong
when the target comes into existence, and native tools will fail.
This is so screwball. This is no problem on AFS, fortunately. */
no, it can't/shouldn't honor the "native" designation when the target
doesn't exist, because it can't be assume the to-be-born target will be
born as a file or a directory, and this matters to Windows.
I wonder... Is there a way to determine in Cygwin (in the (bash) shell)
if the symbolic link is native or not?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple