Re: Bug Report: Regression in Cygwin 2.11.0-1

[Corinna Vinschen <corinna-cygwin at cygwin dot com>]

On Sep  1 16:41, David Allsopp wrote:
> Corinna Vinschen wrote:
> > Some of the path handling is seriously crippled as soon as you start using
> > backslashes, and that's a delipberate decision and won't change, even after
> > fixing the aforementioned bug.
> 
> I don't quite follow this - does that mean that that path definitely
> work even with a new Cygwin? i.e. our existing build system is
> permanently broken for Cygwin 2.11+?

No.  The problem we're talking about here is a regression and needs
fixing, no doubt about it.

I was just saying that win32 paths *in general* get a less complete
treatment than POSIX paths for hopefully obvious reasons.  Just be
aware that \foo\bar is not the same as /foo/bar and may even point
to another file.

As for the bug in question:  I pushed a patch which should fix this
issue.  I created new developer snapshots and uploaded them to
https://cygwin.com/snapshots/.  Please give them a try.


Thanks,
Corinna

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

Attachment: signature.asc
Description: PGP signature