Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Fri, 11 Oct 2002 22:43:16 +0200
From: "U-D90V2D0J\chj" <christian AT j-son DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: binutils 20021009 cvs trunk on cygwin: ld failuers
Message-ID: <20021011204316.GA3180@D90V2D0J>
References: <4 DOT 3 DOT 1 DOT 2 DOT 20021011083907 DOT 031691d0 AT pop DOT rcn DOT com> <000401c2713a$50cb5560$0301a8c0 AT D90V2D0J> <20021011153215 DOT GA4878 AT redhat DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20021011153215.GA4878@redhat.com>
User-Agent: Mutt/1.4i

On Fri, Oct 11, 2002 at 11:32:15AM -0400, Christopher Faylor wrote:
> 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.
> 

I can in a way understand you there, too bad it's conflicting with
building gcc with gcj under cygwin. see for example

http://gcc.gnu.org/ml/java/2002-09/msg00107.html

what do you see as the "best" way ahead?

Cheers,

/ChJ



--
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/