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
From: ericblake AT comcast DOT net (Eric Blake)
To: Joe Krahn <jkrahn AT nc DOT rr DOT com>, cygwin AT cygwin DOT com
Subject: Re: Path processing bug
Date: Sun, 21 Aug 2005 22:31:47 +0000
Message-Id: <082120052231.12264.430900D300063BF300002FE822007601800A050E040D0C079D0A@comcast.net>
X-Authenticated-Sender: ZXJpY2JsYWtlQGNvbWNhc3QubmV0

> Cygwin will accept the path "dir/../file" as being the same as "file", 
> regardless of whether "dir" exists. Apprently, someone decided that a 
> simple path-trimming rule would speed things up, but it is wrong. For 
> example, it breaks building of xedit/lisp, where "lisp/../xedit.h" is 
> not the same as "xedit.h".
> 
> This occurs from bash and tcsh, so it must be in some low-level 
> unix-to-win32 path name processing.

I've raised the issue of this bug in the past, and the response
was that fixing it would likely slow down the normal case.  I too
would like to see it fixed, because it is contrary to POSIX.

--
Eric Blake



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