Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Wed, 23 May 2001 16:32:37 -0400 From: Christopher Faylor To: Cygwin Users Subject: Re: CAUTION: A word about replacing the Cygwin1.dll Message-ID: <20010523163237.C13499@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: Cygwin Users References: <3B0BF143 DOT AD39C7FF AT yahoo DOT com> <3B0C121C DOT 4C22A7FB AT etr-usa DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3B0C121C.4C22A7FB@etr-usa.com>; from warren@etr-usa.com on Wed, May 23, 2001 at 01:40:12PM -0600 On Wed, May 23, 2001 at 01:40:12PM -0600, Warren Young wrote: >Earnie Boyd wrote: >> >> I've noticed several occurrences of "After I replaced cygwin1.dll by the >> old version everything was worked again." >> >> I just want to caution you that just replacing the cygwin1.dll may cause >> you problems when building other packages as the glue that supports the >> cygwin1.dll API may have also changed. > >Why doesn't the DLL name change when the ABI breaks? The ABI has never changed except for the addition of new functions. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple