Bug with paths containing double slashes after double dot after a mount point

[Corinna Vinschen]

On Jun 18 11:18, Vadim Zeitlin wrote:
> Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
> 
> > On Jun 17 16:29, Fahlgren, Eric wrote:
> > > Vadim Zeitlin wrote:
> > > >  Could someone else please test this under Windows 7 to confirm the bug?
> > > 
> > > Windows 7 Pro 64-bit
> > > 
> > > $ ls C:/cygwin/lib/X11/../libc.a
> > > C:/cygwin/lib/X11/../libc.a
> > > $ ls C:/cygwin/lib/X11/..//libc.a
> > > ls: cannot access C:/cygwin/lib/X11/..//libc.a: No such file or directory
> > > 
> > > $ uname -a
> > > CYGWIN_NT-6.1-WOW64 LM-XERXES 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin
> > 
> > Don't use Windows paths, use POSIX paths:
> 
>  As I wrote in my first message[*], I unfortunately can't avoid using
> Windows paths because the original path comes from "g++ -print-search-dirs"
> output of a MinGW compiler. This explains its format and also the trailing
> slash that I can't easily remove neither because the path is processed by
> libtool. And while in the future I might try switching to Cygwin MinGW
> cross-compiler, this can't be done right now so I'd really like to find
> some way of making Windows paths with "..//" in them work with Cygwin.

cygpath -pm `some-mingw-g++ -print-search-dirs`

Other than that, I fixed that in CVS.  It's a Win32 path coversion problem
which only occurs if there are multiple backslashes trailing a ".." path
component.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple