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:	<008201c2a178$53a19100$a790883e@pomello>
From:	"Max Bowsher" <maxb AT ukf DOT net>
To:	"C Wells" <s2audi AT yahoo DOT com>, <cygwin AT cygwin DOT com>
References:	<20021212002942 DOT 12208 DOT qmail AT web20501 DOT mail DOT yahoo DOT com>
Subject:	Re: Dueling cygwin DLLs
Date:	Thu, 12 Dec 2002 00:49:27 -0000
MIME-Version:	1.0
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 knew that solution, but I have inherited 40 scripts
> clocking in at 5 meg by departed staff. Tell me the
> hard way.

In the source code, change all the various IDs that cygwin uses (when time I
tried this, I must have missed one, because the resultant DLLs still
clashed), and recompile Cygwin. Then recompile everything you want to run on
your modified DLL.
Messy, messy, messy.

I suggest you post some more details about how your scripts fail.

Max.


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


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