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: <4.3.1.2.20020424095245.02ba9de8@pop.ma.ultranet.com> X-Sender: lhall AT pop DOT ma DOT ultranet DOT com Date: Wed, 24 Apr 2002 09:56:51 -0400 To: "Gareth Pearce" , cygwin AT cygwin DOT com From: "Larry Hall (RFK Partners, Inc)" Subject: Re: hmmm possible gpl problem? In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 01:05 AM 4/24/2002, Gareth Pearce wrote: >>In the case of the vcdimager issue recently discussed on this list, I >>was downloading it *because I wanted to used it*, and when I installed >>it, it didn't work: cygwin DLL conflicts. This clued me that the >>program (a) used cygwin [Cool!!] and (b) distributed cygwin1.dll >>[conflicted with my "real" cygwin installation; not cool.] I was > >maybe this is what caused the program to crash when i ran it, but i suspect not, since its linked against cygwin.dll - not cygwin1.dll, which i wouldnt expect to conflict with my cygwin1.dll (Although maybe i am just plain wrong:P). It's the latter. ;-) It doesn't matter what the name of the DLL is. Special steps need to be taken to avoid the internals of 2 Cygwin DLLs from conflicting with each other. While this may have been done in this case, it's some effort so it's unlikely. Larry Hall lhall AT rfk DOT com RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- 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/