Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Fri, 16 Jun 2000 12:03:04 -0400 To: "'cygwin'" Subject: Re: symlink created on Samba (Final Resolution) Message-ID: <20000616120304.I1165@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: 'cygwin' References: <45BA125AAE48D311B03D00508B0CA96AA3D766@itsmail.tutsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <45BA125AAE48D311B03D00508B0CA96AA3D766@itsmail.tutsys.com>; from stv@tutsys.com on Fri, Jun 16, 2000 at 08:41:13AM -0700 On Fri, Jun 16, 2000 at 08:41:13AM -0700, Stephen Iribarne wrote: >Ok.. After further digging here's what I find. > >So symlinks work. I ran cat on the file and found that it was working >perfectly. Thanks to everyone for the posts. >However, when Metawares hcppc runs it doesn't deal with the symlink >created! DUH! > >So.. I just wanted to let everyone else know what I found. I was thinking >that Make was the problem but it wasn't. > >I will send something to Metaware to see if they will fix this (yeah right!, >won't hold my breath for that one.) In the meantime, it's delete and copy >for me. I wouldn't expect Metaware to fix a problem with Cygwin symlinks. Cygwin symlinks are entirely a cygwin invention. Unless Metware is using cygwin they will not, and shouldn't be expected to, understand symlinks cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com