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: Sat, 10 May 2003 13:45:40 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygipc (and PostgreSQL) XP problem resolved! Message-ID: <20030510174540.GC12325@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3EB9A54B DOT 8060500 AT ece DOT gatech DOT edu> <20030508135217 DOT GD512 AT tishler DOT net> <3EBB22F5 DOT 4000801 AT ece DOT gatech DOT edu> <1052541657 DOT 1675 DOT 5 DOT camel AT localhost> <20030510072110 DOT B12261 AT ns DOT helixdigital DOT com> <20030510155401 DOT GI19367 AT cygbert DOT vinschen DOT de> <20030510095611 DOT A20781 AT ns DOT helixdigital DOT com> <20030510172231 DOT GN19367 AT cygbert DOT vinschen DOT de> <20030510173142 DOT GC11448 AT redhat DOT com> <20030510173747 DOT GP19367 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030510173747.GP19367@cygbert.vinschen.de> User-Agent: Mutt/1.4.1i On Sat, May 10, 2003 at 07:37:47PM +0200, Corinna Vinschen wrote: >On Sat, May 10, 2003 at 01:31:42PM -0400, Christopher Faylor wrote: >> On Sat, May 10, 2003 at 07:22:31PM +0200, Corinna Vinschen wrote: >> >But it works. I recall having to do the same with a couple of tools >> >when Cygwin changed from cygwinb20.dll to cygwin1.dll. >> >> And even for cygwinb19, for that matter. From include/cygwin/version.h: >> >> /* Major numbers before CYGWIN_VERSION_DLL_EPOCH are >> incompatible. */ >> >> #define CYGWIN_VERSION_DLL_EPOCH 19 > >Ah, those times... Yeah, you think things were better back in B20 days? B19 rulez! 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/