Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 24 Mar 2005 21:20:41 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: clamwin installs incompatible copy of cygwin1.dll Message-ID: <20050325022041.GA3231@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <42430BDF.90808@kleckner.net> <6.2.0.14.0.20050324141914.03d351d8@pop.prospeed.net> <424373E3.8060901@kleckner.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <424373E3.8060901@kleckner.net> User-Agent: Mutt/1.5.6i On Thu, Mar 24, 2005 at 06:13:55PM -0800, Jim Kleckner wrote: >My question now is, can "ln" be used to work around this issue or is >that a "bad idea"? It's a bad idea. Just delete the spurious DLL. No special action is required if the cygwin dll is in the PATH. >PS. Since cgf is steadfast, perhaps this explanation could be added to >the FAQ entry located here that partially explains why multiple dlls is >a problem: http://cygwin.com/faq/faq_3.html#SEC50 No. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/