From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 80271 invoked by alias); 29 Apr 2016 11:34:23 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 79567 invoked by uid 89); 29 Apr 2016 11:34:22 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=reaction, CMD X-HELO: mail-ig0-f177.google.com Received: from mail-ig0-f177.google.com (HELO mail-ig0-f177.google.com) (209.85.213.177) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Fri, 29 Apr 2016 11:34:21 +0000 Received: by mail-ig0-f177.google.com with SMTP id s8so16995696ign.0 for ; Fri, 29 Apr 2016 04:34:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=XfFA+gGJrs9osEKHpaA9vp1pqbGZGDswbsbU24eOp+I=; b=PDDOR+CPlLZPMumugIFD7CpqddhvQ4qgS2tIswwDGGp6ck5l4wOTYQLFBtOy0+fxOh Zl6YMrVziQWmxR+TeVpTPObc+b4RC3uHgnP4/lt45MssKB4r+1T9BCvv4tj74GpS2Y5l 7cbcUkwxzBtYQ7iQ/LXrQj0jQr2zaEFV3SXuDzZcQ8Qm4eIQXn+OKYeGhs3B2Pg7zF4b Q5Yy+bFQe+22tumH5arjRg7M2l7iuRX1sWhKn5b78uoxdhLzg0Z35N/mb54o3nAIiqpY YhER7QhZNnzgxozzUkpkPn4nf7T8JBElTjygn7RKCPYJGBMJJ0O7T4eOqt5gasB4KCa4 2+8w== X-Gm-Message-State: AOPr4FWJNEXXKOAF3IeNDYoZbZrRpF8Xn6mwLexxz8BzgSLXPL10KbohSVesNdlLGD/X6urcuCKhY07H2L99Vg== MIME-Version: 1.0 X-Received: by 10.50.60.68 with SMTP id f4mr4019858igr.34.1461929659032; Fri, 29 Apr 2016 04:34:19 -0700 (PDT) Received: by 10.79.22.134 with HTTP; Fri, 29 Apr 2016 04:34:18 -0700 (PDT) In-Reply-To: <1606116423.20160429020650@yandex.ru> References: <1606116423.20160429020650@yandex.ru> Date: Fri, 29 Apr 2016 12:03:00 -0000 Message-ID: Subject: Re: `CYGWIN=winsymlinks:nativestrict`, `ln -s target link` fails if target doesn't exist From: Gene Pavlovsky To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2016-04/txt/msg00642.txt.bz2 > > 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