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 Date: Wed, 03 Apr 2002 11:39:00 -0500 From: Alan Dobkin To: cygwin AT cygwin DOT com Subject: Re: ncftp current release won't run - missing CYGREADLINE5.DLL Message-ID: <2570919046.1017833940@[192.168.70.5]> In-Reply-To: <20020403160028.GL4053@redhat.com> References: <20020403160028 DOT GL4053 AT redhat DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline --On Wednesday, April 03, 2002 11:00 AM -0500 Christopher Faylor wrote: > On Wed, Apr 03, 2002 at 07:48:29AM -0800, Gord Wait wrote: >> It turns out, no you can't just re run setup.exe on an already >> installed cygwin and expect it to work. It might delete a dll >> or two for you due to an install bug. > > That is just not true. Please don't spread misinformation. In my experience, Gord's first statement above *is* true. Even though the current setup has been fixed so this problem does not happen with new installations, it does not go back and fix the problem for people who used the old setup. The user must manually find the missing DLLs, or use a command like this: cd / && ls `zcat /etc/setup/*.gz | grep -v etc/postinstall` >/dev/null Then setup must be forced to reinstall the appropriate packages; it does not automatically recognize that they need to be updated. Incidentally, IMO Gord's solution to completely reinstall Cygwin from scratch is overkill. Finding the missing DLLs and having setup reinstall them is much easier and should be just as clean. Alan -- 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/