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: Mon, 24 Feb 2003 23:36:31 +0000
Message-ID: <6375-Mon24Feb2003233631+0000-starksb@ebi.ac.uk>
From: David Starks-Browning <starksb AT ebi DOT ac DOT uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: cygwin AT cygwin DOT com
Subject: gcc problem with filename case insensitivity

Greetings,

I have a problem which I realise comes from Windows' being
case-insensitive with filenames.  Even so, maybe someone here knows
how to solve it.

Suppose I have this source file:

	#include <string.h>
	#include "String.h"

	int main() {
	  // some stuff
	}

and I compile with "gcc -Imy/include/dir sourcefile.c" where
String.h lives in my/include/dir.

GCC uses my/include/dir/String.h to satisfy the <string.h> directive.

Is there any way to get GCC to check case when locating include files?

Interestingly, this used to work in B18!  (Hahaha!)
Seriously, though, the B18 release announcement has this remark:

	   The conflict between String.h and string.h (and other such pairs of
	header files) where you include one and get the other has been fixed.

(describing gcc in the release).

A Google search on "filename case gcc site:cygwin.com" turned up only
10 hits, and the B18 release announcement was one of them. :-)

Is there any possibility to get case-sensitive behavior from GCC in
this respect?

Thanks,
David


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