Date: Sun, 21 Sep 1997 13:24:34 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "A. Sinan Unur" <sinan DOT unur AT cornell DOT edu>
cc: djgpp AT delorie DOT com
Subject: Re: *.C on Windows 95 (was: Stupid problem)
In-Reply-To: <341F0C41.8959AA98@cornell.edu>
Message-ID: <Pine.SUN.3.91.970921132328.9556N-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Tue, 16 Sep 1997, A. Sinan Unur wrote:

> under win95 with lfn
> enabled, the files with *.c extension that are created without lfn seem
> to get *.C as the extension. for win 95 this is not a problem. but gcc
> _is_ case sensitive, and you may inadvertently compile C as C++.

I don't see how this could happen.  If you say "gcc -c foo.c", GCC
will find `foo.c' (lowercase!) and happily compile it as a C program,
even if the file's long name is `FOO.C', because the OS itself is
case-insensitive and so open("foo.c") succeeds to open `FOO.C'.

> it
> happened to me a couple of times. especially if you are as braindead as
> me and use batch files rather than makefiles and for get to turn on
> lfnfor ... yuck.

Please explain more.  What exactly did you put into those batch files
and how did you try to compile the files when you got these problems?

And what is that ``lfnfor'' you are talking about?