Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Reply-To: Cygwin List <cygwin AT cygwin DOT com>
Message-Id: <6.2.0.14.0.20050324141914.03d351d8@pop.prospeed.net>
Date: Thu, 24 Mar 2005 14:29:16 -0500
To: Jim Kleckner <jek-cygwin1 AT kleckner DOT net>, cygwin AT cygwin DOT com
From: Larry Hall <lh-no-personal-replies-please AT cygwin DOT com>
Subject: Re: clamwin installs incompatible copy of cygwin1.dll
In-Reply-To: <42430BDF.90808@kleckner.net>
References: <42430BDF DOT 90808 AT kleckner DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 01:50 PM 3/24/2005, you wrote:
>I had a user install clamwin and as discussed on the list here:
> http://www.cygwin.com/ml/cygwin-apps/2004-09/msg00288.html
>it blithely installs cygwin1.dll regardless of any installation
>of cygwin.  This predictably causes problems.
>
>Searching through the user guide and faq doesn't yield
>a suggestion for solutions or workarounds and searching
>the list archives yields so much material that it is
>hard to focus in on what specifically to do.  Obviously,
>I can have the person uninstall clamwin.  Is there anything
>else that makes sense (and, no, uninstalling cygwin doesn't
>make sense)?  


The "standard" solution in these cases is to remove the cygwin1.dll 
from the offending 3rd party package after installing and make sure 
that the 3rd party package can find the already existing cygwin1.dll
in the Cygwin installation (C:\cygwin\bin by default).  The easiest 
way to do this is to put the Cygwin installation path/bin in your
Windows path.  As Chris points out, this could all be automated with 
some minor effort on the part of the 3rd party providers but in the
absence of such support, you have to do it manually. :-(  A better 
question might be to ask the clamwin folks why they can't augment
their installer to accommodate an existing Cygwin installation.  If
their package breaks a Cygwin installation, it's really not a Cygwin
problem per-se.




--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


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