Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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:31:42 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygipc (and PostgreSQL) XP problem resolved!
Message-ID: <20030510173142.GC11448@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3EB84F52 DOT 3020608 AT ece DOT gatech DOT edu> <20030507133326 DOT GA1824 AT tishler DOT net> <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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030510172231.GN19367@cygbert.vinschen.de>
User-Agent: Mutt/1.4.1i

On Sat, May 10, 2003 at 07:22:31PM +0200, Corinna Vinschen wrote:
>On Sat, May 10, 2003 at 09:56:11AM -0700, Dario Alcocer wrote:
>> But what if the data types used by the existing functions are changed?
>> In other words, the old library has void FooFunc(off_t) where off_t is a
>> 4-byte quantity, but the new library uses an 8-byte off_t?
>
>So what?  If we change the name, we don't have anything like a
>transition period.  It's just a new DLL which requires to rebuild
>all tools to work with.  It's a whole new release.
>
>My old 16/32 bit apps are still working fine under a new 32/64 Cygwin
>DLL.  Your below example is a bad coincidence.
>
>> For instance, the PowerTV tool chain uses GNUPro 99, which has an
>
>Urgh, that's pretty old...
>
>> ancient cygwin1.dll included. As long as I don't install the latest
>> Cygwin stuff, everything is ok. However, as soon as I install the
>
>Are you talking about 1.3.22 or the current stuff from CVS?
>
>> They way I've gotten around this issue is to binary edit the PowerTV
>> tool chain and change references to the cygwin1.dll to refer to
>> cygwin0.dll; this is a very ugly hack.
>
>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

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/