From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 129567 invoked by alias); 1 Sep 2018 19:22:12 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 129558 invoked by uid 89); 1 Sep 2018 19:22:11 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-100.7 required=5.0 tests=AWL,BAYES_00,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=Allsopp, allsopp, 2.11, H*f:sk:2018090 X-HELO: mout.kundenserver.de Received: from mout.kundenserver.de (HELO mout.kundenserver.de) (212.227.126.187) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 01 Sep 2018 19:22:09 +0000 Received: from calimero.vinschen.de ([24.134.7.25]) by mrelayeu.kundenserver.de (mreue006 [212.227.15.167]) with ESMTPSA (Nemesis) id 0Ljxmg-1fK6Yn0hBq-00cBg7 for ; Sat, 01 Sep 2018 21:22:07 +0200 Received: by calimero.vinschen.de (Postfix, from userid 500) id 4BFFEA81F07; Sat, 1 Sep 2018 21:22:06 +0200 (CEST) Date: Sat, 01 Sep 2018 19:22:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Bug Report: Regression in Cygwin 2.11.0-1 Message-ID: <20180901192206.GM6350@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20180901155435.GL6350@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="oCBD0SPT9UHZkBMO" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) X-SW-Source: 2018-09/txt/msg00020.txt.bz2 --oCBD0SPT9UHZkBMO Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1111 On Sep 1 16:41, David Allsopp wrote: > Corinna Vinschen wrote: > > Some of the path handling is seriously crippled as soon as you start us= ing > > backslashes, and that's a delipberate decision and won't change, even a= fter > > fixing the aforementioned bug. >=20 > 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 --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --oCBD0SPT9UHZkBMO Content-Type: application/pgp-signature; name="signature.asc" Content-length: 833 -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAluK5t4ACgkQ9TYGna5E T6D/zA/9EKyTCbcdBpZ0Fn+ohSBOJ0PfBkhVAvKujc/CnPAMpMHTmo9kkclkG/3t 4GJmzydIxxFFGd7VZs1owAd3DvfaoCbSyLRvssUgrkcEoVc60ZFc5L+onB6BGlIS 5TEK0hvO4OQ7kcHqVsa3K1IdGNCx7RboJmG08LC41NFiUqHNec0Cn5/5FRytzqvF hSn2BvrS63ZlKFjEQCAMdn9KpZwD8FLI24ZhWlkfciRRcrPkFggBrj292s6jYDDI 6m7lYiOzlFsv7PWqZzWTmbsgnC8b0bULr/3nSy3rNdPUxlS3jE916gRxngWHGQg3 rgSxg73lomDxM6ErSATTiSXpIz3n9Ka/ThJDoHaveqJnCpWDWvbquet5gmy7H0BT Xk+Wh+7i7OglmBYChMJa8+42r1lCA7Wd5vfup4GTRThrXWa8ggr8fRLXl0VjJ3ZL 3RvQP/8YzINEZVB1d2qNXS83o9UZY1mf9/2UuCnMIe3wSc0xEsYEFskaK7T9pYyn GqejN4VbYejjXUh4uio1S7SWLagXDha5FQuz7Ruhbp570PNTMVXSn4uFjaAVF+8h Vcg1of1Rso73TN5XA+LSmx8VMPJXSFSIy7r2rw3X7Sx4g8knj0BlT/t6crzWnTlk LUVShMWUcHzMy0I3OcKWiESttVrLvXMhrdTC8pIiBKrSvPoLZEI= =NxSP -----END PGP SIGNATURE----- --oCBD0SPT9UHZkBMO--