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: <005c01c2a174$47a7c210$a790883e@pomello>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: "C Wells" <s2audi AT yahoo DOT com>, <cygwin AT cygwin DOT com>
References: <20021212001139 DOT 38183 DOT qmail AT web20506 DOT mail DOT yahoo DOT com>
Subject: Re: Dueling cygwin DLLs
Date: Thu, 12 Dec 2002 00:20:26 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

C Wells <s2audi AT yahoo DOT com> wrote:

> I needed a new newer cygwin1.dll in order to run the
> top utility in procps, but its replacement of an older
> DLL caused many other scripts to fail. I can't debug
> the ones it affected. Is there a way to have the top
> executeable call the new cygwin1.dll called
> cygwin2.dll so it can "find an entry point" and run ?

No. (Yes, but far from simple, and harder than just doing as I recommend
below.)

Install the latest cygwin package, then fix your scripts.

Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/