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:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=TvMWb0B1V8N/2Bj5oiUCxgZ/IN6Xzxg2DOHXKoEE0nsOv7TkhVFPO
	JFBwiLG0ZRq2Ymi1YMBQwMWkPwCME0F26GN0TE/tIjLPfL+tMZoEhVyV6Ro0Ls1N
	4VRvuoF5bc1uOOVjGyPDRSxoDSyOrh7m3lD1vDBeC8z1MhTWww5l2k=
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:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=Bb2VcslE0jgR44+bQ01q4yinSMg=; b=JfmbrRkXhyAi6hnTwTzlx2a9CzVz
	l35OAJZEWyiYuCF2UQ9vCBV0Y9aIrPryvNSNCrCIEWUX0VJiPEeYamsd7CVFw5d5
	GlFnfTBTQa4GWOj/lK2sEiTNTfiNED1MHsG9E87IIACrqga5v46Ye3bmT+PeMD8m
	gLTKYfqCx+wPnNc=
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-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-101.5 required=5.0 tests=AWL,BAYES_00,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=H*i:sk:489b128, H*f:sk:489b128, H*MI:sk:489b128, dear
X-HELO:	drew.franken.de
Date:	Fri, 18 Nov 2016 16:51:08 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: case sensitivity on Windows 7 Enterprise with NTFS drive
Message-ID:	<20161118155108.GA26674@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<CAMySpjTXuOSvxjE3+G7U=A9Z-4c7pKS=N3gHn-oN+in=HhHdZQ AT mail DOT gmail DOT com> <20161118151507 DOT GD22194 AT calimero DOT vinschen DOT de> <489b1282-8e0f-0de7-bdd3-168c3b7433db AT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<489b1282-8e0f-0de7-bdd3-168c3b7433db@gmail.com>
User-Agent:	Mutt/1.7.1 (2016-10-04)

--5vNYLRcllDrimb99
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Nov 18 10:32, cyg Simple wrote:
> On 11/18/2016 10:15 AM, Corinna Vinschen wrote:
> > On Nov 18 13:59, Matthias Herz wrote:
> >> Dear Cygwin Team,
> >>
> >> on my cygwin installation I have problems with case sensitivity althou=
gh I
> >> did everything described here:
> >> https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-cas=
esens=3D
> >>
> >> I really need case sentitivity since I would like to use OpenFOAM (c++=
 cfd
> >> library) inside cygwin and OpenFOAM has a bunch of files like scalar.H=
 and
> >> Scalar.H.
> >>
> >> The minimal example for my problem is:
> >>> mkdir test1
> >>> touch test1/file.txt
> >>> touch test1/File.txt
> >>
> >> This gives me
> >> test1
> >> |-- file.txt
> >> |-- File.txt
> >>
> >> This means touch is somehow case sensitive but
> >>> cp -r test1 test2
> >> fails with the message:
> >>> cp: cannot create regular file /test2/file.txt: File exists
> >=20
> > Works for me, I just tested it on a local NTFS.  Is the file tree on
> > some remote FS by any chance?  If so, what Fs is it?  Some FSes are
> > known to have (not so) funny bugs when deviating from Windows defaults.
> > Or, was the CWD set the same way when calling mkdir vs. when calling cp?
> > If you use Windows path rather than POSIX paths, case sensitivity won't
> > work since WIndows paths ar handled with Windows default assumptions.
> >=20
> > Bottom line is, I *know* it works, and it does so since Cygwin 1.7.1.
> > There must be some quirk in either your FS or in your path handling.
>=20
> As I said already, this simply isn't a portable solution.
>=20
> $ uname -a
> CYGWIN_NT-10.0 xxxxxx 2.6.0(0.304/5/3) 2016-08-31 14:32 x86_64 Cygwin
>=20
> $ mkdir A
>=20
> $ mkdir a
> mkdir: cannot create directory =E2=80=98a=E2=80=99: File exists
>=20
> $ rmdir A
>=20
> $ touch A && ls -l A
> -rw-r--r-- 1 cygSimple cygSimple 0 Nov 18 10:26 A
>=20
> $ sleep 60 && touch a && ls -l A
> -rw-r--r-- 1 cygSimple cygSimple 0 Nov 18 10:27 A
>=20
>=20
> My installation is on the native C:\ drive that is NTFS.

You didn't follow
https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesens=
itive
so it's clear that this doesn't work for you.  And it wouldn't be
accepted into the Cygwin distro because that would require that it
also works with case sensitivity off.  However, as long as it's just
the OPs build environment, it's fine.  After all, that's one scenario
case sensitivity support in Cygwin was added for.


Corinna

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

--5vNYLRcllDrimb99
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJYLyNsAAoJEPU2Bp2uRE+gEF8P/A7NBqnyQQa30L9krX4wlz53
bai34iZptyB+fgMfmBURj3zOn9goAGUTkTvYgJi9iktWHcDUIFBlwQP28ybqYIoR
Ai5uP0oE0uEWhhQyCGtPhAte3fo6Er6LdNnXNFnYpyl79g1MFxvbzNsMXOvxtP6c
29E8dG7Pokp09CCgrXMTurAoUFpb61MH9Ng2Wl9RvIsLr976YClJJkeopl+Okw7k
ZYGnHDNzlP04JPjxCGSKvDLTSVViXzedf4gy+bNxyMPRuX2QgLAHAHGAuU1lnDa5
n00QbtoDRU8WsuePzyFQXMqX9W2dDiga2Y0U3/IMa4Z/XsuhKdA7HVxcfEK32egZ
BxZ6JxHgyGtWXVS1PjQQhNynomp2gXBK74y8XMSvqaV/fCdxd+P3tWy4kAQ/+pbI
9HHnhtIhGP+tQypctIh4WcCnma+JEqv4yT7d5K/OW4UdFdXBf+D9tWNXECISdwNN
nTClmBiOfQT/cK5oLE0NIAl+n1s1Evki+xMxj3z7Xq3tKdO9JywnO9+W0FlVAhqG
bCPO1P3zM6hZq5ST700m7Dl+aTpk3QRPsRjxPSipgnDKrfKQ0/a5hQhDNcaN08mf
NxDxoztXxHdddMd5qiEq/56SvTnb8Lcn5MaxArCrfzj66R+r/VDOkK9VUdyq1YME
nP6/AGrY/VXZTx7Eef/5
=bpgz
-----END PGP SIGNATURE-----

--5vNYLRcllDrimb99--

- Raw text -