Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Mon, 10 Feb 2003 17:15:07 EST To: cygwin AT cygwin DOT com Subject: Re: Problems compiling trivial C program. Message-Id: From: Brian Keener Reply-To: bkeener AT thesoftwaresource DOT com In-Reply-To: <02b801c2d12d$c585d0d0$78d96f83@pomello> References: <02b801c2d12d$c585d0d0$78d96f83 AT pomello> Max Bowsher wrote: > (no)winsymlinks - if set, Cygwin creates symlinks as Windows shortcuts with > a special header and the R/O attribute set. If not set, Cygwin creates > symlinks as plain files with a magic number, a path and the system attribute > set. Defaults to set. I've read the CYGWIN environment settings before but sure don't remember seeing this one. Learned something new. ;-) Now what happens if we change this in mid stream - also see below. > NB: setup creates the magic-number/system-attribute always. Three questions here - 1) call me stupid - what is NB. 2) Is this correct for setup - I see this default on a new install but shouldn't it handle based on CYGWIN environment if updating .... But .... then what happens if I change the setting - see question above and Question 3. 3) Can both methods work simultaneously. If setup does it one way and CYGWIN Environment default is the other - will I have broken symlinks. bk -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/