This is the mail archive of the cygwin-developers mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: native symlink


On 4/24/2013 8:50 AM, Corinna Vinschen wrote:
> On Apr 24 08:06, Jeffrey Altman wrote:
>> On 4/24/2013 6:34 AM, Corinna Vinschen wrote:
>>> 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.
>>
>> 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?
> 
> i686:
> 
>   http://cygwin.com/snapshots/

I have confirmed that the change works on AFS without the environment
setting.

Thanks.

Jeffrey Altman




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]