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:date:from:subject:to:mime-version:content-type :message-id; q=dns; s=default; b=Bb1bQo3sgtDblXA5XBQlv9n7BqyvU7F alcNthWkLSmA3/CnECsV3Hi1HgmiQlFS2+fWUKALN3RJzepIhHTT5o6m3wt5sMur QsqYDYUpThUHzLONBf0w5A0aB6QQ6+lVPxeqHEanOwSRjNAxYQG8nmATpsVt3U9k YIswbnRxbVdY= 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:date:from:subject:to:mime-version:content-type :message-id; s=default; bh=7J2yzuzWGwv6U0J7qDb4/bQwY7U=; b=B5Kwf nBsXNJI9oEHOZcoxi1/8MD8a8PTwue1+R767S2X4k18IJ1eH+5zWdVXShGP5O8hI ZfITmp8uhylvaU1tBMzii0paEmsiQKhW59aS3spfu1LgVUHo0aSkablO2IKqeA5s Fz0DmPW+OBAog9X6Q1LatluW+9uhmAKykdFvos= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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-Virus-Found: No X-Spam-SWARE-Status: No, score=1.8 required=5.0 tests=BAYES_50,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=Notice, H*MI:solutions, mkdir, H*x:Service X-HELO: smtp.tt-solutions.com Date: Sat, 26 Nov 2016 02:42:06 +0100 From: Vadim Zeitlin Subject: Bug in cygpath -a handling of leading ".//" To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: MULTIPART/SIGNED; protocol="application/pgp-signature"; micalg=pgp-sha1; BOUNDARY="27031793-41-1480124526=:7124" Message-Id: --27031793-41-1480124526=:7124 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE Hello, I seem to have a special talent for finding problems related to the handling of doubled consecutive slashes in cygpath, as 5 years after posting my previous bug report on this topic (see http://sourceware.org/ml/cygwin/2011-06/msg00212.html), I have another one which is also best shown with an example obtained with the latest Cygwin 2.6.0 version under Windows 7: [~]% cd /tmp [/tmp]% mkdir dir [/tmp]% cd $_ [/tmp/dir]% cygpath -a ../dir /tmp/dir [/tmp/dir]% cygpath -a ./../dir /tmp/dir [/tmp/dir]% cygpath -a .//../dir /tmp/dir/dir The last one is, of course, incorrect, as it should still output /tmp/dir. Notice that the problem doesn't happen if "-am" or "-aw" is used, only for "-a" on its own, so it does have a simple workaround: realpath can be used instead. But I still wanted to report it in the hope that it might at least help somebody else if they run into it (it took me quite some time to realize that the bug wasn't in my own makefile but rather in cygpath itself...). Please let me know if you'd like me to provide any further information and thanks in advance for looking at this, VZ --27031793-41-1480124526=:7124 Content-Type: APPLICATION/PGP-SIGNATURE -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) iEYEABECAAYFAlg46G4ACgkQBupB3k9sHob3WACfQqBnl3KDtr+AiZ+2EpRrwT+1 AKsAoJwFPdpsGQfiyk7g+ZFj+uWVhgDr =91/+ -----END PGP SIGNATURE----- --27031793-41-1480124526=:7124--