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/
