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: Sun, 21 Aug 2005 20:24:13 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Path processing bug Message-ID: <20050822002413.GE12465@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <082120052231 DOT 12264 DOT 430900D300063BF300002FE822007601800A050E040D0C079D0A AT comcast DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <082120052231.12264.430900D300063BF300002FE822007601800A050E040D0C079D0A@comcast.net> User-Agent: Mutt/1.5.8i On Sun, Aug 21, 2005 at 10:31:47PM +0000, Eric Blake wrote: >>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. As always, I can't speak for Corinna, but I suspect that she would be as thrilled as I would be if you fixed this contrary-to-POSIX problem without impacting the speed of cygwin's already slow path handling code. I think it's a pretty hard problem and I really don't care about POSIX but if this is really that important then maybe someone will step forward to fix it. The code in question is in path.cc. cgf -- 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/