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, 12 Oct 2005 10:36:46 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Bug: 1.5.18: 'This application has failed to start because cygwin1.dll was not found. Re-installing the application may fix this problem' Message-ID: <20051012083646.GW12938@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Oct 10 21:29, Igor Pechtchanski wrote: > On Mon, 10 Oct 2005, Glen A Coakley wrote: > I believe this may be an instance of the error I reported in > . Basically, the > PATH conversion code stops whenever it encounters an invalid element in > the PATH. In my case it was due to strict case checking, but it seems to > be a more general problem. Basically, the Cygwin path conversion code > stops when it encounters a non-existent directory, and only returns the > part of the path it's converted so far. Since in your case the invalid > directory comes first, you get an empty PATH. > > A patch to turn off this behavior altogether is reasonably simple, but I'm > not sure it'll be accepted. The main question is whether this behavior is > desired. Corinna or Chris, care to comment? This should be solved in current CVS (the general problem with non-existant directories, not the case_check stuff). Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat, Inc. -- 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/