public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: case sensitivity on Windows 7 Enterprise with NTFS drive
Date: Fri, 18 Nov 2016 16:33:00 -0000	[thread overview]
Message-ID: <20161118155108.GA26674@calimero.vinschen.de> (raw)
In-Reply-To: <489b1282-8e0f-0de7-bdd3-168c3b7433db@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2640 bytes --]

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 although I
> >> did everything described here:
> >> https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesens=
> >>
> >> 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
> > 
> > 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.
> > 
> > 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.
> 
> As I said already, this simply isn't a portable solution.
> 
> $ uname -a
> CYGWIN_NT-10.0 xxxxxx 2.6.0(0.304/5/3) 2016-08-31 14:32 x86_64 Cygwin
> 
> $ mkdir A
> 
> $ mkdir a
> mkdir: cannot create directory ‘a’: File exists
> 
> $ rmdir A
> 
> $ touch A && ls -l A
> -rw-r--r-- 1 cygSimple cygSimple 0 Nov 18 10:26 A
> 
> $ sleep 60 && touch a && ls -l A
> -rw-r--r-- 1 cygSimple cygSimple 0 Nov 18 10:27 A
> 
> 
> 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-casesensitive
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

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-11-18 15:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18 15:15 Matthias Herz
2016-11-18 15:32 ` cyg Simple
2016-11-18 15:35 ` Corinna Vinschen
2016-11-18 15:51   ` cyg Simple
2016-11-18 16:33     ` Corinna Vinschen [this message]
2016-11-18 18:45 Matthias Herz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161118155108.GA26674@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).