Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <05bf01c2dc60$836ec100$c67486d9@webdev> From: "Elfyn McBratney" To: "cygwin" , "David Starks-Browning" References: <6375-Mon24Feb2003233631+0000-starksb@ebi.ac.uk> Subject: Re: gcc problem with filename case insensitivity Date: Mon, 24 Feb 2003 23:57:38 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 > 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 > #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 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? I just tried this with "check_case:strict" in my CYGWIN environment variable, and that works. It finds /usr/include/string.h and my local include/String.h . Regards, Elfyn McBratney elfyn@exposure.org.uk www.exposure.org.uk -- 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/