This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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

Corinna Vinschen <corinna-cygwin <at>> 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.



Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]