From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30823 invoked by alias); 24 Apr 2013 12:06:31 -0000 Mailing-List: contact cygwin-developers-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner@cygwin.com Mail-Followup-To: cygwin-developers@cygwin.com Received: (qmail 30807 invoked by uid 89); 24 Apr 2013 12:06:30 -0000 X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED autolearn=ham version=3.3.1 Received: from sequoia-grove.ad.secure-endpoints.com (HELO mail.secure-endpoints.com) (208.125.0.235) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Wed, 24 Apr 2013 12:06:30 +0000 X-MDAV-Result: clean X-MDAV-Processed: mail.secure-endpoints.com, Wed, 24 Apr 2013 08:06:28 -0400 Received: from [172.16.16.54] by secure-endpoints.com (Cipher TLSv1:-SHA:128) (MDaemon PRO v13.0.5) with ESMTP id md50000428952.msg for ; Wed, 24 Apr 2013 08:06:27 -0400 X-Spam-Processed: mail.secure-endpoints.com, Wed, 24 Apr 2013 08:06:27 -0400 (not processed: message from trusted or authenticated source) X-Return-Path: jaltman@openafs.org X-Envelope-From: jaltman@openafs.org X-MDaemon-Deliver-To: cygwin-developers@cygwin.com Message-ID: <5177CABF.8040406@openafs.org> Date: Wed, 24 Apr 2013 12:06:00 -0000 From: Jeffrey Altman User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: cygwin-developers@cygwin.com Subject: Re: native symlink References: <5153759A.7080307@cygwin.com> <79518574-72AB-451F-ACE3-3277981987D5@mac.com> <20130401195216.GA7174@ednor.casa.cgf.cx> <9A868E84-96C2-486C-98DF-3FF5079ACD50@mac.com> <20130402000633.GA3977@ednor.casa.cgf.cx> <9362C76C-DB6B-4DA8-B61E-7980CFDF7A8A@mac.com> <20130403014056.GA3383@ednor.casa.cgf.cx> <2EC5409B-C507-4B41-862C-D42D69CE3741@mac.com> <515BB10C.9080101@openafs.org> <20130403152907.GD2468@calimero.vinschen.de> <20130424103450.GM26397@calimero.vinschen.de> In-Reply-To: <20130424103450.GM26397@calimero.vinschen.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Reply-To: jaltman@openafs.org X-SW-Source: 2013-04/txt/msg00066.txt.bz2 On 4/24/2013 6:34 AM, Corinna Vinschen wrote: > On Apr 3 17:29, Corinna Vinschen wrote: >> Cygwin is a POSIX environment in the first place. Interop is fine, >> but if it collides with POSIX, we're clearly favoring POSIX. >> >> Having said that. >> >> Chris and I had a private discussion (not the first one on the subject!) >> and we're willing to revisit the use of native symlinks in Cygwin but >> it will be a while before that happens. A change to the path handling >> code like this is not something that we'd consider for 1.7.18 which is >> long overdue anyway. >> >> What I will do is to add a new CYGWIN environment variable option, along >> the lines of the winsymlinks option(*), or, which is very likely the >> more elegant solution, a mount option, which will result in trying to >> create native symlinks first, and a Cygwin symlink only if creating >> a native symlink failed. That should help you along. > > I just applied a patch to CVS which adds AFS support as well as native > symlink support. On AFS, native symlinks are used exclusively, on any > other filesystem supporting native symlinks Cygwin will try to create > them if you specify "winsymlinks:native" in the $CYGWIN environment > variable. > > After mulling over this problem I found that using an environment > solution is better than the mount point solution, because this allows > on-the-fly creating of native symlinks in certain scenarios, while the > default can be kept at using Cygwin sysfile symlinks, which are still > better suited for a POSIX environment. > > For completeness, you can also specify "winsymlinks:lnk" or just > "winsymlinks". This will result in trying to generate shortcut > type symlinks, as before. > > Jeffrey, please give especially AFS at try here. > > > HTH, > Corinna Hi Corinna, I've confirmed that the unrecognized reparse point fix in 1.7.18-1 does work. Unfortunately, I'm still unable to get gcc (actually cc1) to build even a simple hello world c program. Is there is a nightly binary distribution I can use to test from? Jeffrey Altman