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
Message-ID: <3F570BCC.4114A95F@dessent.net>
Date: Thu, 04 Sep 2003 02:54:20 -0700
From: Brian Dessent <brian AT dessent DOT net>
Organization: My own little world...
X-Accept-Language: en,en-US
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: cygwinb19.dll
References: <OFACDEA1F1 DOT 634A6952-ONC1256D97 DOT 00322748-C1256D97 DOT 0032FAEE AT diamond DOT philips DOT com> <3F570A53 DOT 90502 AT lapo DOT it>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Note-from-DJ: This may be spam

Lapo Luchini wrote:

> Let's just say that version b19 is "very very very very old" and,
> indeed, obsolete...
> But anyway the new tools shouldn't have problems if a DLL *with a
> different name* is found in the system.
> 
> BT:W notcie that my answer is not authoritative, only CGF and a few of
> other can give those...

If they both try to use some other resource (such as shared memory or a
named pipe or something) that have the same name it'll die a horrible
death.  

The obvious thing would be to try to recompile the app with a recent
build of Cygwin... it should be open source unless they bought a buy-out
license from Redhat, right?

Brian

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