| delorie.com/archives/browse.cgi | search |
| 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: | <20021212001139.38183.qmail@web20506.mail.yahoo.com> |
| Date: | Wed, 11 Dec 2002 16:11:39 -0800 (PST) |
| From: | C Wells <s2audi AT yahoo DOT com> |
| Subject: | Dueling cygwin DLLs |
| To: | cygwin AT cygwin DOT com |
| MIME-Version: | 1.0 |
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 ? Thanks __________________________________________________ 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/
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |