Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-Id: <4.3.1.2.20001221132429.027ac130@pop.ma.ultranet.com> X-Sender: lhall AT pop DOT ma DOT ultranet DOT com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Thu, 21 Dec 2000 13:28:38 -0500 To: Martin Oberhuber , "'cygwin AT sources DOT redhat DOT com'" From: "Larry Hall (RFK Partners, Inc)" Subject: Re: Running cygwinb19 and cygwin-1.1 based programs in parallel In-Reply-To: <549191FE7B71D311BC5900104B2921321682BD@kirk.takefive.co.at > Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 11:50 AM 12/21/2000, Martin Oberhuber wrote: >Hello, > >I need to run some cygwinb19 based compilers (which I have only in >binary form) with my cygwin-1.1 based make system (make, bash etc.). > >Since in that case, cywinb19.dll and cygwin1.dll are in memory at >the same time, can I expect the two DLL versions to work together >correctly? - So far, I have not found any problems but I was only >able to do a quick test and I'd like to be really sure. > >Thanks for your answer, > >Martin Keep going and you'll find problems. If you really need to work with the old compiler toolset (why's that?), remove cygwinb19.dll and copy cygwin1.dll in its place (i.e. rename it to cygwinb19.dll). Or, better yet, pull out your favorite binary editor and edit the executables that use cygwinb19.dll to use cygwin1.dll. Mind you, fill in the extra characters left over in this operation with spaces, otherwise you'll nuke your executable. Still, I think we'd all like to see you use current tools, compiler et al.!:-) Larry Hall lhall AT rfk DOT com RFK Partners, Inc. http://www.rfk.com 118 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple