Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Date: Fri, 20 Aug 1999 19:01:16 -0400 Message-Id: <199908202301.TAA28345@envy.delorie.com> From: DJ Delorie To: cgf AT cygnus DOT com CC: cygwin-developers AT sourceware DOT cygnus DOT com In-reply-to: <19990820185820.F7062@cygnus.com> (message from Chris Faylor on Fri, 20 Aug 1999 18:58:20 -0400) Subject: Re: libcygwin.a as a symbolic link to lib{c,m}.a -- need insight References: <19990820133204 DOT A5087 AT cygnus DOT com> <199908202229 DOT RAA28257 AT mercury DOT xraylith DOT wisc DOT edu> <19990820184852 DOT B7062 AT cygnus DOT com> <199908202253 DOT SAA28267 AT envy DOT delorie DOT com> <19990820185820 DOT F7062 AT cygnus DOT com> > But that was the only thing you *could* do with DJGPP, right? It > doesn't have symbolic links, does it? Well, it does, but only for executables. The choice was between dummy libs and *no* libs for us. Plus, symlinks on samba is a FAQ already.