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:	<20021212002942.12208.qmail@web20501.mail.yahoo.com>
Date:	Wed, 11 Dec 2002 16:29:42 -0800 (PST)
From:	C Wells <s2audi AT yahoo DOT com>
Subject:	Re: Dueling cygwin DLLs
To:	cygwin AT cygwin DOT com
In-Reply-To:	<005c01c2a174$47a7c210$a790883e@pomello>
MIME-Version:	1.0

I knew that solution, but I have inherited 40 scripts
clocking in at 5 meg by departed staff. Tell me the
hard way. I wish it were easier to run a cmdline util
cygwin or other to yield cpu mem stats on win.
Thanks


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


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

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

- Raw text -