Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Fri, 11 Oct 2002 11:32:15 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: binutils 20021009 cvs trunk on cygwin: ld failuers
Message-ID: <20021011153215.GA4878@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4 DOT 3 DOT 1 DOT 2 DOT 20021011083907 DOT 031691d0 AT pop DOT rcn DOT com> <000401c2713a$50cb5560$0301a8c0 AT D90V2D0J>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <000401c2713a$50cb5560$0301a8c0@D90V2D0J>
User-Agent: Mutt/1.4i

On Fri, Oct 11, 2002 at 05:24:34PM +0200, Christian J?nsson wrote:
>Hmm, I don't quite follow you here.
>
>The PATH variable is not set by me, it's set by cygwin, right?
>
>The PATH contains the entry /cygdrive/c/WINDOWS/system32 but that makes
>no sense if "check_case:strict" is present in the CYGWIN variable
>initialising cygwin, right?

It depends on whether WINDOWS is the actual name of your directory or
not.  This isn't set by Cygwin, regardless.  It's set by the system.
If you are going to use strict case checking then it is up to you
to make sure that all filenames are properly referenced.  As you
probably noticed, there was no "Make sure all files have proper case?"
option in setup.exe.  And, having the DLL actually try to figure out
what case is correct would defeat the purpose of strict case checking.

I always suggest against using strict case checking.  It adds extra
overhead and causes other problems since Windows assumes that it
can be flexible with respect to filename cases.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/