Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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" To: "C Wells" , 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 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 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/