DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=DCSsgR7k4Y9d+m1hVSO4JTqgYn/ox
	gIYNdGBPn+Hlx5Mri4GvWSg1COd3DUcFh7zesvin5TDYs2YP54HQZrwslnq8dnRj
	UUMvg9+VTQb/1dvryCYVPow9Qu6qSfWrgZRpOLKNW4kl/M/O5RsV1hq4uzglRP2m
	P3T+7Sj6HvHBm0=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: David Allsopp <David.Allsopp@cl.cam.ac.uk>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Bug Report: Regression in Cygwin 2.11.0-1
Date: Sun, 2 Sep 2018 08:37:44 +0000
Message-ID: <E51C5B015DBD1348A1D85763337FB6D901ADFF74F4@Remus.metastack.local>
References: <BL2PR16MB096125DC7F302700C5DE88C0C80E0@BL2PR16MB0961.namprd16.prod.outlook.com> <pmdgjr$9q9$1@blaine.gmane.org> <20180901155435.GL6350@calimero.vinschen.de> <E51C5B015DBD1348A1D85763337FB6D901ADFF2257@Remus.metastack.local> <20180901192206.GM6350@calimero.vinschen.de>
In-Reply-To: <20180901192206.GM6350@calimero.vinschen.de>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

Corinna Vinschen wrote:
> 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! That snapshot does indeed fix our build.

How feasible would it be to generate an alternate setup.ini (setup-snapshots.ini or something) and include the snapshots in the actual mirror with a switch to setup to select the alternate file? When we finally get to it with OCaml's CI, that is probably how I would configure our CI to operate (i.e. synchronise with a mirror, download the latest snapshot and then patch setup.ini), but I imagine there might be other projects which would set jobs running if it were very simple from upstream to do. 


David

--
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