Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Sat, 10 May 2003 19:22:31 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cygipc (and PostgreSQL) XP problem resolved!
Message-ID: <20030510172231.GN19367@cygbert.vinschen.de>
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:
> 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.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
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/

