This is the mail archive of the
cygwin
mailing list for the Cygwin project.
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'
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 12 Oct 2005 10:36:46 +0200
- 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'
- References: <dieuni$h2o$1@sea.gmane.org> <Pine.GSO.4.63.0510102054500.25364@slinky.cs.nyu.edu>
- Reply-to: cygwin at cygwin dot com
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
> <http://www.cygwin.com/ml/cygwin/2004-09/msg00552.html>. 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/