X-Recipient: archive-cygwin AT delorie DOT com
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=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=lQEQMc7W/kYsksOg23OcmM+bDgE=; b=PI5
	qKD2E1+MGAF9icv6vgxNTcJ3ie5HgXqKJWecZCA3s3ON3IaZq61acuNhQeoOlSRn
	ZI6Pcq1sA0im/xwZUrq5qXQAYvKVLaNL3MJyMHScqUS7Nor08dZjO3Sri5O88Nqt
	uy5jF0JF7/b77MttaO/P5VKverJ+oFLnaiCMPF7Y=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=0.8 required=5.0 tests=BAYES_20,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT,MIME_BASE64_BLANKS,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=H*MI:sk:2018090, H*i:sk:2018090, H*r:172.16.0, Hx-spam-relays-external:172.16.0.1
X-HELO: outmail149080.authsmtp.com
From: David Allsopp <David DOT Allsopp AT cl DOT cam DOT ac DOT uk>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT 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 AT BL2PR16MB0961 DOT namprd16 DOT prod DOT outlook DOT com> <pmdgjr$9q9$1 AT blaine DOT gmane DOT org> <20180901155435 DOT GL6350 AT calimero DOT vinschen DOT de> <E51C5B015DBD1348A1D85763337FB6D901ADFF2257 AT Remus DOT metastack DOT local> <20180901192206 DOT GM6350 AT calimero DOT vinschen DOT de>
In-Reply-To: <20180901192206.GM6350@calimero.vinschen.de>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
X-Server-Quench: 782932e7-ae8b-11e8-9efd-0015176ca198
X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse
X-AuthRoute: OCd1ZAARAlZ5RRob BmUtCCtbTh09DhZI RxQKKE1TKxwUVhJa I0lFL1x7O0wTWlBf HTVUBhpUUkISDCNq aQpQZRVda0BNWA9u VwZLQ1FMFQVtHx4A BAAfUx1tdQBZeTA3 bURqDCsiXUR8dUZ9 SgBXEGkBK2Boamkc UhVfalIBeFFXfx4Q Yk12ASVZfGUHZ39h QFE4NmlgbSNlBXYd aBwCZWgfWUERAmx0 fR0NBzg0BkwCQW0y KVQNO1EDHUBZaANr aB15HAtw
X-Authentic-SMTP: 61633634383431.1038:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 213.105.212.114/25
X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system.
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id w828cbA3023655

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