Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Sat, 10 May 2003 13:15:26 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygipc (and PostgreSQL) XP problem resolved! Message-ID: <20030510171526.GA11448@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20030506174725.GE1652@tishler.net> <3EB84F52.3020608@ece.gatech.edu> <20030507133326.GA1824@tishler.net> <3EB9A54B.8060500@ece.gatech.edu> <20030508135217.GD512@tishler.net> <3EBB22F5.4000801@ece.gatech.edu> <1052541657.1675.5.camel@localhost> <20030510072110.B12261@ns.helixdigital.com> <20030510155401.GI19367@cygbert.vinschen.de> <20030510095611.A20781@ns.helixdigital.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030510095611.A20781@ns.helixdigital.com> User-Agent: Mutt/1.4.1i On Sat, May 10, 2003 at 09:56:11AM -0700, Dario Alcocer wrote: >The reason I ask is that I've seen binaries compiled for an older >cygwin1.dll run incorrectly or crash when dynamically linking against a >new cygwin1.dll. Then that is what we the computer biz call "a bug". I don't recall anyone making the claim that we were perfect or that we don't screw up. However, we do try hard to maintain backwards compatibility. The 32->64 bit conversion is no exception. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/