[PATCH] normalize_posix_path and c:/foo/bar

Corinna Vinschen corinna-cygwin@cygwin.com
Sun Mar 16 16:08:00 GMT 2008

On Mar 16 08:51, Brian Dessent wrote:
> Corinna Vinschen wrote:
> > Actually that was intended, but unfortunately the current path handling
> > deliberately creates DOS paths with slashes (in find_exec) right now,
> > so that doesn't work ATM.
> I guess what I don't understand is how it's both possible for
> open("c:/foo/bar.exe") to succeed and for this code to treat it as a
> relative posix path instead of absolute win32.  Or is that the point,
> that forward-slash win32 paths are intended not to work?

That was my point originally but I gave up on it.  I thought it might
be a good idea to recognize a path as Win32 path only if it starts
with x:\ or \, because "a:" could be a perfectly valid POSIX file or
directory name.  In the latter case a:/foo could be the file foo in
$cwd/a:/foo.  I'd still like to see it hanbdled that way, but that's
probably taking it a step too far...

> is going to be quite a lot of affected code unfortunately... as I said
> the only real reason I went looking here is I updated my tree to current
> CVS and insight stopped functioning.

I found it by calling `make x':

  $ make x
  make: cc: Nosuch file or directory.



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

More information about the Cygwin-patches mailing list