From: Ben Peddell <killer DOT lightspeed AT bigpond DOT com>
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Re: make says no makefile found, but the file is out there
References: <200304070403 DOT h3743MW25915 AT pavo DOT ncbi DOT nlm DOT nih DOT gov> <b6rh7f$fog$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <2f64dfca DOT 0304080458 DOT 6768f9a4 AT posting DOT google DOT com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 30
Message-ID: <0_Toa.19440$1s1.291762@newsfeeds.bigpond.com>
Date: Tue, 22 Apr 2003 01:30:05 +1000
NNTP-Posting-Host: 144.134.89.111
X-Trace: newsfeeds.bigpond.com 1050938364 144.134.89.111 (Tue, 22 Apr 2003 01:19:24 EST)
NNTP-Posting-Date: Tue, 22 Apr 2003 01:19:24 EST
Organization: Telstra BigPond Internet Services (http://www.bigpond.com)
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Tony Richardson wrote:
> Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de> wrote in message news:<b6rh7f$fog$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE>...
> 
>>Anton Lavrentiev <lavr AT ncbi DOT nlm DOT nih DOT gov> wrote:
>>
>>
>>>I renamed MAKEFILE into "makefile" all lowercase,
>>>then it reads the file. But there is another problem:
>>>%.o: %.c rule is not working because there are
>>>DOS files around, all having ".C" extensions,
>>>uppercased. 
>>
>>This should *never* be a problem.  Neither DOS nor Windows really care
>>about the case of filenames.  DJGPP has a runtime library setting that
>>changes this, but I strongly disbelieve any distributed DJGPP binary has
>>that set.
> 
> 
> I've had the same "problem" with DJGPP make.  Files with a .C extension
> are assumed to be C++ files instead of C files.  Either rename the
> file or redefine the .o .C rule.
> 
> Tony Richardson

That's only when you invoke GCC with the C in uppercase on the command 
line. If the LFN API can't support case-insensitive searches, then it 
will look for foo.c when you enter "foo.c", although you've got a file 
named FOO.C